three-tier-layout verifies tier presence and the .work.local gitignore but never that local-tier artefacts are absent from committed tiers — a NEXT.md, scratch/, or logs/ under .abcd/work/ or .abcd/development/ passes clean. Field incident: NEXT.md (handover file, local-tier by convention) lived at .abcd/work/NEXT.md in a public repo and carried host infra details; no rule flagged the misplacement.

Frontmatter

.abcd/work/issues/resolved/iss-155-three-tier-rule-ignores-local-artefacts.md
open on GitHub ↗ · commit history ↗

mentions2

• dcn-26072900000000022026-07-29 — v0.5.0 scoped as "security & consistency" (plan: plans/2026-07-29-v0.5.0-security-and-consistency.md): the security half closes the NEXT.md leak class end-to-end (itd-74/spc-20; the atomic iss-154+157+125+153 detector item; iss-155/156; guard batch iss-159+144+148; boundary fixes iss-30/34), the consistency half retires the record-currency majors (iss-37..44, iss-80) — maintainer added the latter rather than deferring them. Version is derived by launch ship, not declared; 0.5.0 is the prediction given itd-74 additive. Deferred majors listed explicitly in the plan (largest: iss-124); the 2026-07-24 queue's pick-up role is superseded.
• dcn-26072900000000052026-07-29 — iss-155: `three-tier-layout` gains the placement half of the tier convention — local-tier artefacts (`NEXT.md`, `scratch/`, `logs/`) found directly in a committed tier are now errors, each finding carrying a move-to-`.abcd/.work.local/` fix. The rule verified tier presence and the `.work.local` gitignore but never that local ephemera were ABSENT from `.abcd/work/` and `.abcd/development/`, which is exactly how a handover file carrying host infrastructure detail reached a public repo unflagged. Presence is checked on the filesystem, matching the tier checks themselves: an untracked NEXT.md in a committed tier is one `git add -A` from history. The existing rule extends rather than minting a sibling ID — one convention, one rule.