coulomb/repo-scoping
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement scope-derived candidate review infrastructure

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-16 00:26:29 +02:00
parent f4d782c997
commit ba2228e889
14 changed files with 1740 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/quality-criteria/acceptance-quality-criteria.v1.json
View File

@@ -73,8 +73,8 @@
"severity": "critical",
"applies_to": ["ability", "capability", "feature", "evidence"],
"description": "Generated SCOPE.md text cannot be primary evidence for rebuilding the same characteristic model. It may be comparison context, bootstrap context, or a generated output under review.",
"deterministic_action": "rejected",
"deterministic_action_when": "A candidate is supported only or primarily by generated SCOPE.md content from the same scoping process.",
"deterministic_action": "requires_review",
"deterministic_action_when": "A candidate is supported only or primarily by generated or derived SCOPE.md content from the same scoping process.",
"reviewer_guidance": "Use source, docs, tests, and product intent instead of accepting circular evidence.",
"agentic_guidance": "Treat circular generated-scope evidence as a blocker unless independent evidence supports the same claim.",
"examples": [
@@ -95,6 +95,36 @@
"examples": [
"Schema examples mentioning model providers should not create native model-provider capabilities."
]
},
{
"id": "RREG-QC-007",
"title": "Template Boilerplate Is Not Repository Purpose",
"category": "template-contamination",
"severity": "high",
"applies_to": ["ability", "capability"],
"description": "Repository templates, seed README text, and bootstrap boilerplate should not become the repository's native ability or capability when more specific source evidence exists.",
"deterministic_action": "downgraded",
"deterministic_action_when": "Candidate names or descriptions are dominated by template boilerplate such as repo-seed instead of repo-specific evidence.",
"reviewer_guidance": "Prefer SCOPE, INTENT, implementation, or product docs that describe this repository, not the template it was created from.",
"agentic_guidance": "Detect template text and replace it with a repo-specific abstraction before proposing approval.",
"examples": [
"A README that says 'A git repository template to bootstrap coulomb projects' should not become the ability for ops-warden."
]
},
{
"id": "RREG-QC-008",
"title": "Scope-Derived Drafts Stay Separate From Intent",
"category": "scope-intent-separation",
"severity": "medium",
"applies_to": ["scope", "intent", "ability", "capability"],
"description": "Existing SCOPE.md content can bootstrap current-state candidates and draft intent, but it must remain clearly labeled as scope-derived until reviewed.",
"deterministic_action": "requires_review",
"deterministic_action_when": "A candidate or draft is generated from SCOPE.md rather than authored INTENT.md or implementation evidence.",
"reviewer_guidance": "Check whether the claim describes current behavior, desired future utility, or both. Do not write INTENT.md without explicit review.",
"agentic_guidance": "Use SCOPE.md to propose current-state candidates and ambitious intent drafts, but keep provenance and review status explicit.",
"examples": [
"A Railiance SCOPE.md capability block can create a candidate capability, not approved registry truth."
]
}
]
}