Skip to content

backfill(B-0036 partial-6): resolve line-20 calibration via §33 block compression on 3 docs#579

Merged
AceHack merged 1 commit intomainfrom
backfill/section33-compress-3-calibration-tension-docs
Apr 26, 2026
Merged

backfill(B-0036 partial-6): resolve line-20 calibration via §33 block compression on 3 docs#579
AceHack merged 1 commit intomainfrom
backfill/section33-compress-3-calibration-tension-docs

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 26, 2026

Summary

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:

Doc Before After
blake3-receipt-hashing Non-fusion line 25 line 9 ✓
oracle-scoring-v0-design Non-fusion line 27 line 9 ✓
provenance-aware-claim-veracity Non-fusion line 48 line 13 ✓

Path (a) chosen over (b) or (c)

From B-0036's three resolution paths:

  • (a) Compress §33 blocks ← THIS PR
  • (b) Relax lint window from 20 to ~40 lines
  • (c) Amend GOVERNANCE.md §33 spec

Reasoning:

  • GOVERNANCE.md §33 spec stays unchanged (no rule-shifts to accommodate non-canonical docs)
  • Discipline enforced as written, not relaxed for convenience
  • Compression preserves content; nothing lost (for provenance-aware, the multi-paragraph "Promotion path to authoritative-detector status" prose was MOVED to a separate ## Promotion path section AFTER the §33 header, not deleted)
  • Matches the natural §33 form (scope-statement, not scope-essay)

Lint progression

B-0036 Sub-task 2 unblocked

Once lint count hits 0, B-0036 Sub-task 2 (wire check-archive-header-section33.sh to gate.yml as enforcing CI lint) is unblocked. The §33 substrate-primitive lifecycle reaches operational enforcement.

Test plan

…ion docs (path A resolution)

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.
@AceHack AceHack enabled auto-merge (squash) April 26, 2026 08:59
Copilot AI review requested due to automatic review settings April 26, 2026 08:59
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR resolves remaining §33 archive-header lint violations in three docs/research/** external-conversation imports by compressing the four required header fields so all labels land within the first 20 lines, per GOVERNANCE.md §33 and the check-archive-header-section33.sh lint behavior.

Changes:

  • Compressed multi-line Scope: / Attribution: / Non-fusion disclaimer: fields into single-line (or fewer-line) forms so all four §33 labels appear within the first 20 lines.
  • Preserved longer-form content by relocating it below the §33 header region (notably the provenance-aware doc’s promotion-path prose).
  • Kept Operational status: research-grade enum-strict to satisfy the lint’s anchored-value check.

Reviewed changes

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

File Description
docs/research/provenance-aware-claim-veracity-detector-2026-04-23.md Compresses §33 header; moves promotion-path prose below header so Non-fusion disclaimer: is within the first 20 lines.
docs/research/oracle-scoring-v0-design-addressing-aminata-critical-2026-04-23.md Compresses §33 header so Non-fusion disclaimer: is within the first 20 lines while keeping enum-strict operational status.
docs/research/blake3-receipt-hashing-v0-design-input-to-lucent-ksk-adr-2026-04-23.md Compresses §33 header so Non-fusion disclaimer: is within the first 20 lines while preserving the document’s scope/attribution intent.

@AceHack AceHack merged commit ed463b1 into main Apr 26, 2026
19 checks passed
@AceHack AceHack deleted the backfill/section33-compress-3-calibration-tension-docs branch April 26, 2026 09:01
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants