aidd-lint: tier2-charter.md change-control banner cites a gate that does not exist #142

Open
opened 2026-07-26 21:34:42 +00:00 by jared · 2 comments
Owner

CONTEXT: plugins/os-aidd-lint/references/tier2-charter.md's change-control banner reads: "Closed catalog: exactly the three ##-level smell entries below. Do not add a fourth without a human decision (see ticket #107 open question #4 / step-bulk anti-gaming backstop)."

FINDING: Forgejo issue #107 contains no numbered open-questions list at all. Verified twice on 2026-07-26 — once by a recon agent reading the full issue and its comments via tea issue 107 --repo jared/cc-os --comments, and once independently by grep over the issue text. The only step-bulk content in #107 is a sentence in its Context section: "Also serves as the anti-gaming backstop for step-bulk (fat step split into thin steps that are still gate logic)." That is not an enumerated open question #4.

IMPACT: low severity but exact. The gate itself is real and enforceable — it lives in ADR-0060, which explicitly rejected auto-adding catalog entries and recorded two novel smells as human-review candidates instead. Only the pointer is wrong. Note the irony worth recording: the file that defines the duplicated-authority smell, and whose plugin ships a dead-reference-pointer cop, carries a dead authority reference.

FIX: reword the banner to cite ADR-0060 as the gate rather than a nonexistent question in #107. NOTE THIS IS GATED: tier2-charter.md is a change-controlled frozen prompt asset. Any edit requires updating RECORDED_SHA256 and RECORDED_LINE_COUNT in plugins/os-aidd-lint/tests/tier2/charter_test.rb and re-running plugins/os-aidd-lint/eval/bin/run --tier haiku (roughly 10 minutes, three fixtures). Bundle this with the next charter edit rather than paying that cost for a one-line pointer fix.

CONTEXT: `plugins/os-aidd-lint/references/tier2-charter.md`'s change-control banner reads: "Closed catalog: exactly the three `##`-level smell entries below. Do not add a fourth without a human decision (see ticket #107 open question #4 / step-bulk anti-gaming backstop)." FINDING: Forgejo issue #107 contains no numbered open-questions list at all. Verified twice on 2026-07-26 — once by a recon agent reading the full issue and its comments via `tea issue 107 --repo jared/cc-os --comments`, and once independently by grep over the issue text. The only step-bulk content in #107 is a sentence in its Context section: "Also serves as the anti-gaming backstop for step-bulk (fat step split into thin steps that are still gate logic)." That is not an enumerated open question #4. IMPACT: low severity but exact. The gate itself is real and enforceable — it lives in ADR-0060, which explicitly rejected auto-adding catalog entries and recorded two novel smells as human-review candidates instead. Only the pointer is wrong. Note the irony worth recording: the file that defines the `duplicated-authority` smell, and whose plugin ships a `dead-reference-pointer` cop, carries a dead authority reference. FIX: reword the banner to cite ADR-0060 as the gate rather than a nonexistent question in #107. NOTE THIS IS GATED: `tier2-charter.md` is a change-controlled frozen prompt asset. Any edit requires updating RECORDED_SHA256 and RECORDED_LINE_COUNT in `plugins/os-aidd-lint/tests/tier2/charter_test.rb` and re-running `plugins/os-aidd-lint/eval/bin/run --tier haiku` (roughly 10 minutes, three fixtures). Bundle this with the next charter edit rather than paying that cost for a one-line pointer fix.
Author
Owner

Verified: the mispointed banner now lives in tier2-charter-notes.md (charter split into charter.md + charter-notes.md, catalog grew 3->5 via ADR-0068/0071). Same wrong pointer to '#107 open question #4' persists there. Fix direction unchanged; update file path when implementing.

Verified: the mispointed banner now lives in tier2-charter-notes.md (charter split into charter.md + charter-notes.md, catalog grew 3->5 via ADR-0068/0071). Same wrong pointer to '#107 open question #4' persists there. Fix direction unchanged; update file path when implementing.
Author
Owner

Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.

Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#142
No description provided.