Development record
itd-134 renders a banner from the identity block's name, tagline and version; 19-identity's block holds a title, a tagline and an optional pitch, and no version.
itd-134 renders a banner from the identity block's name, tagline and version; 19-identity's block holds a title, a tagline and an optional pitch, and no version.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-134-every-abcd-managed-cli-greets-like-abcd.md:13— "rendered from that repo's canonical identity block — name, tagline, version" - End B:
.abcd/development/brief/04-surfaces/19-identity.md:50— "Title and tagline are required; the pitch is optional at onboarding and may wrap"
itd-134 scaffolds a banner rendered from the repo's canonical identity block, naming its fields as name, tagline and version. 19-identity defines the block's fields as Title, Tagline and Pitch, with title and tagline required and the pitch optional. The block carries no version and calls the name a title, so a banner sourced from the block as itd-134 describes cannot take its version from it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 626.
Frontmatter
| id | iss-2610262036082275 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262036082275-itd-134-renders-a-banner-from-the.md
open on GitHub ↗ · commit history ↗
References1
- itd-134Every abcd-managed CLI greets like abcd does: one command scaffolds a banner for a managed repo, rendered from that repo's canonical identity block — name, tagline, version — as a committed, language-neutral artefact (the generator emits the rendered banner, not code), so a CLI in any language opens with its own identity without hand-drawing anything. Split out of itd-112 at its 2026-08-21 grill: itd-112 keeps abcd's own banner and the colour ladder; this intent carries the managed-repo generator and the per-repo accent question.related