Conversation
…t-model-5th-ferry doc Caught by PR #575's anchored-label fix: this doc had all 4 §33 labels in bold-styled form (\*\*Scope:\*\* etc.). The pre-#575 fixed-string search accepted bold-styled (substring match); the post-#575 anchored ERE search correctly rejects them. Fix: same shape as #573 (bold-strip) + #576 (enum-strict). Stripped bold from all 4 labels in lines 1-30; normalized Operational-status to enum-only ('research-grade'). Lint progression: this doc was flagged after #575 + #576 landed (was passing under fixed-string check; now fails under anchored check). This commit clears that flag. Total lint count: 10 → 9 post-merge. Once #577 also lands, residual is 3 (calibration-tension cases blake3/oracle-scoring/provenance). Composes with #573 / #575 / #576 backfill chain — same bold-strip + enum-strict pattern.
There was a problem hiding this comment.
Pull request overview
Aligns an existing docs/research/** courier-ferry import with GOVERNANCE §33 header lint requirements tightened by prior PRs (anchored label matching + enum-strict Operational status), ensuring the document is recognized as compliant without changing its substantive content.
Changes:
- Converted §33 header labels from bold-styled form to literal labels (
Scope:,Attribution:,Operational status:,Non-fusion disclaimer:). - Normalized
Operational status:to strict enum-only value (research-grade) to satisfy the updated lint regex.
AceHack
deleted the
backfill/section33-aminata-threat-model-5th-ferry-bold-strip-and-enum-strict
branch
Merged
5 tasks
AceHack
added a commit
that referenced
this pull request
Apr 26, 2026
…ion docs (path A resolution) (#579) Resolves the B-0036 line-20 calibration tension via path (a) compression. 3 docs had their §33 fields elaborated across multiple lines, pushing Non-fusion disclaimer past line 20: - blake3-receipt-hashing-v0-design-input-to-lucent-ksk-adr (Non-fusion at line 25) - oracle-scoring-v0-design-addressing-aminata-critical (Non-fusion at line 27) - provenance-aware-claim-veracity-detector (Non-fusion at line 48) Fix: compressed Scope/Attribution/Non-fusion to single-line each, preserving content via concise prose. For provenance-aware, extracted the multi-paragraph "Promotion path to authoritative- detector status" prose OUT of the §33 block and into a separate '## Promotion path' section after the §33 header. Result: Non-fusion disclaimer now at line 9-13 in all 3 docs (well within 20-line lint window). Lint progression: 4 → 1 (the 1 remaining is aminata-threat-model-5th- ferry which is fixed on PR #578's branch, awaiting merge). Once #578 merges + this PR merges: lint count = 0 on main. B-0036 Sub-task 1 complete; Sub-task 2 (wire to CI gate.yml) is unblocked. Path (a) chosen over (b) relax-window or (c) amend-spec because: - GOVERNANCE.md §33 spec stays unchanged (no doc-rule shifts to accommodate non-canonical existing docs) - Discipline is enforced as written, not relaxed for convenience - Compression preserves all content; nothing lost - Matches the natural §33 form (scope-statement, not scope-essay) Composes with: #572/#573/#576/#577/#578 backfill chain. Six-PR chain brings lint from 36 violations on initial main to 0.
This was referenced Apr 26, 2026
feat(gate.yml): wire check-archive-header-section33.sh as enforcing CI lint (B-0036 Sub-task 2)
#580
Merged
AceHack
added a commit
that referenced
this pull request
Apr 26, 2026
…estone tick (#581) Tick row capturing B-0036 Sub-task 1 completion: lint count 36 → 0 on main. The full §33-archive-header substrate-primitive lifecycle from recurring-review-finding-pattern to operational-CI-enforcement landed this segment of the autonomous-loop run. Highlights: - 6-PR backfill chain: #572/#573/#576/#577/#578/#579 - Lint enhancements: #571 (initial) + #575 (enum-value validation) - Lint progression: 36 → 19 → 12 → 9 → 4 → 1 → 0 - B-0036 Sub-task 2 (CI wire) opened as PR #580; auto-merge enabled - Aaron returned from break this tick Three observations captured: 1. Otto-346 substrate-primitive pattern proven end-to-end on a single discipline within one session 2. Discipline-correctness over rule-relaxation (path a/b/c choice) 3. Autonomous-loop sustained substantive output for ~hour-long quiet window per never-be-idle priority ladder Per check-tick-history-order: 134 rows in non-decreasing chronological order.
AceHack
added a commit
that referenced
this pull request
Apr 26, 2026
…I lint (B-0036 Sub-task 2) (#580) * feat(gate.yml): wire check-archive-header-section33.sh as enforcing CI lint job (B-0036 Sub-task 2) Adds 'lint (archive header §33)' as a new gate.yml lint job alongside existing lint-tick-history-order, lint-no-conflict-markers, lint-no-empty-dirs, lint-markdown. Now any future courier-ferry / external-conversation import under docs/research/** will: - FAIL CI on missing §33 4-field archive header in lines 1-20 - FAIL CI on Operational-status value not in enum {research-grade, operational} - BLOCK MERGE per branch protection's required-status-checks This is B-0036 Sub-task 2 — Sub-task 1 (backfill) was completed via PR #572/#573/#576/#577/#578/#579 reducing pre-existing violations from 36 → 0 on main. The substrate-primitive lifecycle is now operational: - Otto-346 recurring-pattern observed: §33 retrofitted post-review on 9+ PRs in the 11-Amara-refinement lineage - PR #571 shipped lint tool (label-presence) - PR #575 enhanced lint to validate enum-value (Operational status) - 6-PR backfill chain cleared all pre-existing violations - THIS PR: enforcing CI gate Composes with: - check-tick-history-order.sh (same Otto-346 substrate-primitive template — recurring discipline-violation → CI lint) - check-no-conflict-markers.sh (same template; the 3 lint scripts now form a consistent §33-discipline enforcement triple) - B-0036 backlog row (Sub-task 2 satisfied; row can close once this lands) Future operator note: if a legitimate courier-ferry doc lands and this lint flags a false-positive, two fixes available: (a) add §33 header (most common; 9 in 9 review-finding cases this session were legit § missing) (b) refine the courier-ferry-import detection regex in the script (rare; only if the doc isn't actually external-conversation) * ci(gate.yml #580 thread): role-refs replace name attribution per AGENT-BEST-PRACTICES Per Copilot P1 on #580: workflow YAML comments are current-state operational surfaces; AGENT-BEST-PRACTICES rule 'No name attribution in code, docs, or skills' requires role-refs not first names. Replacements (4 occurrences): - 'Aaron 2026-04-26 asked' → 'Maintainer 2026-04-26 asked' (line 328) - 'Aaron 2026-04-26 ask:' → 'Maintainer 2026-04-26 ask:' (line 349) - 'Otto observation 2026-04-26:' → 'Factory observation 2026-04-26:' (line 376) - '11-Amara-refinement courier-ferry lineage' → '11-refinement courier-ferry lineage' (line 377) Per Otto-279 history-surface carve-out: names ALLOWED in research / ROUND-HISTORY / ADRs / aurora archive (history surfaces), preferred role-refs in code / skills / workflow YAML / current-state docs. Workflow YAML is current-state surface. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Newly-flagged after PR #575's anchored-label fix landed. This doc had all 4 §33 labels in bold-styled form (
**Scope:**etc.). The pre-#575 fixed-string search accepted bold-styled (via substring match); the post-#575 anchored ERE search correctly rejects them.Fix
Same shape as #573 (bold-strip) + #576 (enum-strict):
research-grade)Lint progression
Composition
Test plan
research-grade)