Capability Discovery Acceptance Criteria
acceptance criterion · created
Evidence record
- What is verified
- Uses in published workflows: 0
- Revision
- Version 0.1.3
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
The gate no implementation lane may start before: acceptance criteria for the capability map. The map must cover all required specification sections, every row must resolve either to an existing verified path or to a named creating lane, inventory numbers must be measured rather than copied from the reference, gaps must be listed explicitly with owners, and the map check itself must be mutation-tested: one deliberately broken row produced a red run before the fix restored green.
Where it was applied and what it helped deliver
No published workflow records this capability yet — the count includes only ledger mentions that resolve.
Metadata and provenance
- id
- tal-sc-stage-0b-capability-discovery
- type
- acceptance criterion
- version
- 0.1.3
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- stage-0b, gate
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-sc-stage-0b-capability-discovery · v0.1.3