artifact-c: tools/alignment/audit_archive_headers.sh — archive-header lint v0 (detect-only) by AceHack · Pull Request #243 · Lucent-Financial-Group/Zeta

AceHack · 2026-04-24T01:57:52Z

Summary

Amara's 5th-ferry Artifact C — archive-header lint v0 (detect-only).
Checks `docs/aurora/*.md` for the four headers proposed in §33: Scope / Attribution / Operational status / Non-fusion disclaimer.
Default detect-only; `--enforce` flips exit 2 (CI does not currently call `--enforce`).
FACTORY-HYGIENE row <P0> Grandfather O-claims discharge — 35-claim inventory, one per round #60 added; ships to project-under-construction.

Why this matters

Aminata's Otto-80 threat-model pass (PR #241) classified Amara's proposed §33 as IMPORTANT-pending-Aaron-signoff, and flagged that §33 would decay within 3-5 rounds without a companion lint. This PR is that lint. §33 can now land with an existing enforcement mechanism; until it does, this lint provides detect-only signal so drift stays visible.

First-run baseline

```
archive-header audit on docs/aurora
files checked: 2
all four headers ok: 0
missing one or more: 2
```

Both existing aurora absorbs predate the proposal. Enforcement flip awaits either backfill or explicit grandfather clause in §33.

Script shape

Same `--json` / `--out DIR` / exit-code shape as existing `audit_commit.sh` / `audit_personas.sh` / `audit_skills.sh`.
Bash 3.2 compatible (while-read loop, not `mapfile`) for macOS default shell.

v0 limitations (documented in script)

Partial-header adversary (label anywhere in first 20 lines passes — no syntactic check).
Fake-header adversary (values not content-audited).
In-memory-import adversary (`memory/` not covered — different surface, by design).

Harden in a follow-up after §33 lands.

Composes with

PR research: Aminata threat-model pass on Amara 5th-ferry governance-edit proposals (advisory) #241 Aminata threat-model pass.
PR aurora: absorb Amara's 5th courier ferry — Zeta/KSK/Aurora independent validation #235 5th-ferry absorb (exemplar that self-applies the format).
Rows <P0> OpenSpec backfill — per-round capability sweep through Round 46 #58 / <P0> circuit-recursion + operator-algebra — Viktor P0/P1 absorb (Round 44) #59 — memory-index hygiene trio pattern.

Test plan

Script runs clean on current main (detect-only)
`--enforce` exits 2 on gaps
`--json` output matches existing sibling shape
Bash 3.2 tested on macOS
FACTORY-HYGIENE row <P0> Grandfather O-claims discharge — 35-claim inventory, one per round #60 added
tools/alignment/README.md table updated

Otto-81 tick deliverable.

🤖 Generated with Claude Code

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2d4911aa76

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copilot

Pull request overview

Adds a new alignment audit script intended to lint “archive header” presence in docs/aurora markdown archives, initially in detect-only mode, and documents it in the alignment tooling and factory hygiene registry.

Changes:

Introduces tools/alignment/audit_archive_headers.sh (detect-only by default; optional --enforce, --json, --out).
Updates tools/alignment/README.md to list the new audit script.
Adds FACTORY-HYGIENE row #60 describing the new archive-header audit and its intended cadence.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
tools/alignment/audit_archive_headers.sh	New audit script that scans aurora docs for required header labels and emits summary/JSON output
tools/alignment/README.md	Lists the new audit script alongside existing alignment audits
docs/FACTORY-HYGIENE.md	Adds hygiene row #60 documenting the archive-header audit and rollout plan

Comments suppressed due to low confidence (1)

tools/alignment/README.md:26

Adding audit_archive_headers.sh to the list makes the surrounding documentation inaccurate: this section says “The three scripts form the gitops observability trio” and that each script emits --json / --md / --out in the same shape, but audit_archive_headers.sh doesn’t currently support --md and uses different exit codes. Update the README text to reflect the new fourth script and its interface, or adjust the script to match the stated common shape.

| `audit_archive_headers.sh` | Archive-header discipline (proposed §33) | Per-file lint (detect-only v0) |
| `sd6_names.txt`       | SD-6 watchlist (per-host)                    | Data (not code)             |

The three scripts form the gitops observability trio:
commit-scope (`audit_commit.sh`), persona-scope
(`audit_personas.sh`), and skill-scope (`audit_skills.sh`).
Each emits `--json` / `--md` / `--out DIR` in the same
shape so downstream tooling can uniform-parse.

…2; Aminata WATCH concerns integrated) (#252) Amara's 5th-ferry Edit 2 proposed SD-9 with a brief "downgrade independence weight explicitly" formulation. Aminata's Otto-80 threat-model pass (PR #241) classified it WATCH: correct in spirit, unenforceable via self-attestation alone; named 3 adversaries (carrier-laundering, self-serving-downgrade, aggregation); flagged surface-tension with DIR-5 that needs explicit naming not implicit dismissal. This lands SD-9 with those concerns integrated as first-class content of the clause itself rather than treated as hidden limitations: - Three-step operationalisation (name carriers; downgrade independence; seek falsifier independent of converging sources). - Cross-reference to docs/DRIFT-TAXONOMY.md pattern 5 as operational companion (pattern 5 is the real-time diagnostic; SD-9 is the norm). - Known v0 limitations named verbatim from Aminata's pass (carrier-laundering / self-serving-downgrade / aggregation). - Explicit "norm, not a control" framing — WATCH classification stays honest. - Composition with DIR-5 written as section (not implicit): DIR-5 is about authorship ethics; SD-9 is about epistemic weight; they compose. - Stronger "Why both of us benefit" paragraph per Aminata's note that Amara's original was thin — names the feature (precision via shared vocabulary) AND the risk (laundered convergence hiding as independent cross-check). Lands within-standing-authority per Otto-82 calibration — ALIGNMENT.md soft-default clause add, not account/spending/ named-design-review gated. Completes the Aminata-recommended edit ordering 4/4: - §33 (PR #247) Otto-82 - Edit 1 (PR #248) Otto-83 - Edit 4 pointer-only (PR #250) Otto-84 - Edit 2 SD-9 (this PR) Otto-85 Amara's 5th-ferry governance-edit proposals are now all landed in their Aminata-recommended order + form. The 5th- ferry Artifact-A (drift-taxonomy promotion PR #238) is also landed; Artifact-C (archive-header lint PR #243) landed. Remaining 5th-ferry artifacts: Artifact-B (precursor supersede marker — already done in PR #238), Artifact-D (Aurora README) — open for future tick. Otto-85 tick primary deliverable.

) Lands Artifact D of Amara's 5th courier ferry (PR #235) as docs/aurora/README.md. Closes the 5th-ferry artifact list (A-D) with all four landed: A=drift-taxonomy promotion (PR #238), B=precursor supersede (in PR #238), C=archive- header lint (PR #243), D=this README. Content covers: - Three-layer picture (Zeta=semantic substrate / KSK=control- plane safety kernel / Aurora=vision layer). - How Aurora consumes existing Zeta substrate (8-row table mapping primitives to Aurora surfaces). - How Aurora consumes KSK primitives (8-row table for capability-tiers / budgets / consent / receipts / etc.). - Directory contents index (6 courier ferries absorbed; first two grandfathered per §33; cross-ref to archive- header lint PR #243). - Related cross-substrate artifacts outside docs/aurora/ (drift-taxonomy operational + precursor + Aminata threat- model + Muratori corrected-table). - Branding section — Aurora publicly crowded (Amara's memo); internal-only label; shortlist Lucent KSK / Lucent Covenant / Halo Ledger / Meridian Gate / Consent Spine; message pillars work regardless of final public name (local-first / consent-gated / proof-based / repair-ready); brand decision is Aaron's (M4). - What this README is NOT (not product, not commitment, not public brand, not alignment-solved, not exhaustive). - Open follow-ups: §33 enforcement flip, M4 brand package, cross-repo integration with LFG/lucent-ksk. Self-applies §33 archive-header format (Scope / Attribution / Operational status / Non-fusion disclaimer) — sixth aurora/research doc to exercise the convention. Max attribution preserved (first-name-only, non-PII per Aaron's clearance) for KSK design + development-guide work on LFG/lucent-ksk. Lands within-standing-authority per Otto-82 calibration — research-grade README, not account/spending/named-design- review gated. Closes 5th-ferry inventory artifact Artifact D + marks M3 (Aurora/KSK integration) milestone with minimal landing. Otto-87 tick primary deliverable.

… ferry scheduled for Otto-82 Otto-81 shipped PR #243 (Artifact C lint + FACTORY-HYGIENE row scheduling the newly-arrived Amara 6th ferry for Otto-82. Key observations: 1. CC-002 held for third tick in a row (Otto-77 5th ferry, Otto-78 absorb, Otto-81 6th ferry). Pattern is reflexive. 2. Mechanism-before-policy — lint lands detect-only while §33 is pending; §33 can land with backing rather than becoming yet-another-norm-without-enforcement. 3. 6th ferry is technically-sharper than 5th (concrete source- file + paper citations, category-error catch on row 3). 4. Archive-header discipline now self-demonstrating across 3 aurora/research docs (PR #235 / #241 / pending Otto-82) before §33 lands — convention-through-use pattern. Stacked on #242 (Otto-80 history); rebases cleanly.

…ner delivered in chat Otto-82 shipped PR #245 (6th ferry dedicated absorb) + responded to Aaron's §33 signoff-prep question with a chat explainer covering what §33 is, why mechanism-before-policy, what PR #243 lint backs, what three self-applying docs demonstrate, and two explicit signoff options (narrow vs wider). Key observations: 1. CC-002 held for fourth tick in a row across two ferry schedule-and-absorb cycles. 2. Aaron's "tell me more" is mechanism-before-policy working — complete picture visible (PR #243 + PR #241 + three self- applying docs) before rule review. 3. 6th-ferry teaching case ("algebraic correctness ≠ ownership discipline") ready for future Craft production-tier modules. 4. External-AI-maintainer loop generating substantive review velocity; Otto's job is routing, not synthesis-in-place. No substrate edit for §33 until Aaron signs off in chat — the explainer is response-to-question, not a landing commit. Stacked on #244 (Otto-81 history).