Development record
The press release's acceptance has capture write an issue file, but universal patterns calls capture (and intent and spec) a read-only render
The press release's acceptance has capture write an issue file, but universal patterns calls capture (and intent and spec) a read-only render
A premise contradiction (severity nitpick) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/01-product/01-press-release.md:43— "a structured issue at.abcd/work/issues/open/iss-N-<slug>.mdexists with frontmatter populated and source provenance recorded" - End B:
.abcd/development/brief/05-internals/04-universal-patterns.md:90— "capture,intent,guard,--version,rules,spec,identityandbanlistare read-only renders"
The press release's acceptance criterion says /abcd:capture "<text>" leaves a structured issue file under .abcd/work/issues/open/. Universal patterns lists capture, intent and spec with lint, guard and banlist as read-only renders. A verb that writes a record into the ledger is not a read-only render.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 87.
Frontmatter
| id | iss-2610262031062811 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610262031062811-the-press-release-s-acceptance-has.md
open on GitHub ↗ · commit history ↗