generated from coulomb/repo-seed
Route auto review requests to agentic review
This commit is contained in:
@@ -67,12 +67,12 @@ that show the repository provides the utility directly or intentionally exposes
|
||||
it as a facade/adapter. Mentions, dependencies, configuration, and tooling are
|
||||
context until a curator promotes them or stronger owned evidence appears.
|
||||
|
||||
Trusted auto-approval applies the same rule. A candidate capability must have
|
||||
source references and an eligible utility relationship (`owned`, `facade`, or
|
||||
`adapter`) before it can be approved automatically. Dependency, tooling,
|
||||
configuration, and mention-only candidates remain review material. The review
|
||||
decision should explain both sides: why approved candidates were considered safe
|
||||
and why skipped candidates need curator review.
|
||||
Deterministic quality gates apply the same source and utility relationship
|
||||
signals, but they do not approve automatically. Gates may reject, downgrade,
|
||||
invalidate, flag, merge, or require review. Approval requires human judgement or
|
||||
a configured agentic reviewer that records evidence, criteria version, and
|
||||
rationale. Dependency, tooling, configuration, and mention-only candidates remain
|
||||
review material.
|
||||
|
||||
`INTENT.md` may also seed intended capabilities when it contains an explicit
|
||||
capability section. These intent-derived candidates are marked as review
|
||||
|
||||
Reference in New Issue
Block a user