Development record
itd-36 calls bare-command-as-render a universal discipline; the intent surface page says it is a common convention, not a universal one.
itd-36 calls bare-command-as-render a universal discipline; the intent surface page says it is a common convention, not a universal one.
A premise contradiction (severity nitpick) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-36-memory-unification.md:41— "Bare invocation renders state per the universal bare-command-as-render discipline." - End B:
.abcd/development/brief/04-surfaces/05-intent.md:344— "Bare-command-as-help is a common abcd convention, not a universal one"
itd-36 justifies the memory command's bare render as following the universal bare-command-as-render discipline. 05-intent.md states outright that bare-command-as-help is a common abcd convention and not a universal one, naming commands whose bare form prints help or a version block instead of a board. Both cannot hold: either every bare command renders state or some do not.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 531.
Frontmatter
| id | iss-2610262034535349 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610262034535349-itd-36-calls-bare-command-as-render-a.md
open on GitHub ↗ · commit history ↗
References1
- itd-36Knowledge That Compounds, Not Knowledge That Re-Derivesrelated