** + allowlist 3 load-bearing (unblocks #550 composite) #551

New issue

Closed

opened 2026-07-26 21:22:56 +02:00 by engineer · 0 comments

engineer commented

2026-07-26 21:22:56 +02:00

Owner

Context

The #550 v2/next→main composite fails register-check.sh with 22 register-drift hits, all in docs/architecture/** (the #367 Phase-0 arc42/C4/contracts docs). These docs are new to main (origin/main has zero files under docs/architecture/), so the drift arrives purely with the composite. Zero hits in the Go substrate.

This is the arch-docs sibling of the closed #387 (which scrubbed chamber-name attributions from code comments in scripts/workflows/tests — the arch docs were out of #387's scope and landed later via #367).

Scope (operator-ratified 2026-07-26: scrub-first + allowlist-for-3)

19 attribution-credit lines → genericize-scrub per #387 (drop the reviewer/chamber name, keep the technical rationale): "QM substrate-verified" ×9 (arc42 README + 05/06/07-view + c4/README), "Quartermaster confirmed / substrate-oracle", "confirmed by QM" ×2, "Surveyor review 3722/3725", "Surveyor's reproduction".
3 load-bearing → allowlist (.register-allowlist), NOT scrub/rephrase:
- arc42/12-glossary.md:31 + arc42/11-risks-technical-debt.md:57 — "engineer-week(s)", the ADR-0008 §11.5 effort-unit compound (scanner over-matches "engineer"); allowlist preserves the ADR-0008 vocabulary tie.
- contracts/fragment-format.md:102 — "crew names", a meta-line describing the scrub mechanism itself; allowlist is exactly what "documenting what we scrub" needs.

Rationale: #387's discipline is credit-scrub, not legit-compound-elimination or self-referential-meta-rewrite — so allowlist is the designed escape hatch for the 3.

Acceptance criteria

19 attribution-credit lines genericized — Engineer executed per Bosun 8592 dispatch; landed on rebased v2/next; scrubbed reviewer names while preserving review-number rationale
3 load-bearing terms added to .register-allowlist — "engineer-week" ×2 (ADR-0008 §11.5 effort-unit compound) + "crew names" fragment-format:102 (self-referential meta); preserved semantic ties per Engineer 5448 framing-verify + Bosun eb0c endorsement
register-check.sh exits 0 GREEN — both steps (file-scan + subject-scan RAN this time); verified across rebase (a8f4d35) + graphviz fold (0a62a0f) + build-c4 fold (1952d7d) cycles
Doc-only substrate touch; full gate green — Surveyor 4591/4592/4593 verified substrate stamp carries across all rebase+fold cycles; internal/+cmd/ byte-identical throughout
Landed on v2/next; unblocked #550 composite; PR#550 merged to main as 1952d7d fast-forward via Do:rebase (Phase 5 close)

Refs #550, #367, #387.

## Context The `#550` v2/next→main composite fails `register-check.sh` with **22 register-drift hits, all in `docs/architecture/**`** (the #367 Phase-0 arc42/C4/contracts docs). These docs are **new to main** (origin/main has zero files under `docs/architecture/`), so the drift arrives purely with the composite. Zero hits in the Go substrate. This is the arch-docs sibling of the closed #387 (which scrubbed chamber-name attributions from *code comments* in scripts/workflows/tests — the arch docs were out of #387's scope and landed later via #367). ## Scope (operator-ratified 2026-07-26: scrub-first + allowlist-for-3) - **19 attribution-credit lines → genericize-scrub per #387** (drop the reviewer/chamber name, keep the technical rationale): "QM substrate-verified" ×9 (arc42 README + 05/06/07-view + c4/README), "Quartermaster confirmed / substrate-oracle", "confirmed by QM" ×2, "Surveyor review 3722/3725", "Surveyor's reproduction". - **3 load-bearing → allowlist (`.register-allowlist`), NOT scrub/rephrase**: - `arc42/12-glossary.md:31` + `arc42/11-risks-technical-debt.md:57` — "engineer-week(s)", the ADR-0008 §11.5 effort-unit compound (scanner over-matches "engineer"); allowlist preserves the ADR-0008 vocabulary tie. - `contracts/fragment-format.md:102` — "crew names", a meta-line *describing* the scrub mechanism itself; allowlist is exactly what "documenting what we scrub" needs. Rationale: #387's discipline is **credit-scrub**, not legit-compound-elimination or self-referential-meta-rewrite — so allowlist is the designed escape hatch for the 3. ## Acceptance criteria - [x] 19 attribution-credit lines genericized — Engineer executed per Bosun 8592 dispatch; landed on rebased v2/next; scrubbed reviewer names while preserving review-number rationale - [x] 3 load-bearing terms added to `.register-allowlist` — "engineer-week" ×2 (ADR-0008 §11.5 effort-unit compound) + "crew names" fragment-format:102 (self-referential meta); preserved semantic ties per Engineer 5448 framing-verify + Bosun eb0c endorsement - [x] `register-check.sh` exits 0 GREEN — both steps (file-scan + subject-scan RAN this time); verified across rebase (a8f4d35) + graphviz fold (0a62a0f) + build-c4 fold (1952d7d) cycles - [x] Doc-only substrate touch; full gate green — Surveyor 4591/4592/4593 verified substrate stamp carries across all rebase+fold cycles; internal/+cmd/ byte-identical throughout - [x] Landed on v2/next; unblocked #550 composite; PR#550 merged to main as 1952d7d fast-forward via Do:rebase (Phase 5 close) Refs #550, #367, #387.

engineer self-assigned this

2026-07-26 21:23:03 +02:00

engineer referenced this issue from a commit

2026-07-26 21:48:40 +02:00

docs(register): scrub attribution-credit from arch docs + allowlist 3 load-bearing

engineer referenced this issue from a commit

2026-07-26 22:12:42 +02:00

docs(register): scrub attribution-credit from arch docs + allowlist 3 load-bearing