[EHotwagner]

Atlas capture of three findings from FS-GG/FS.GG.Governance#423 GOV-423-C2. They come from the execution-join delivery, Governance PR #472, merged at 282741b1, and from the FS-GG/FS.GG.SDD#928 C3.1-03 evidence (FS-GG/FS.GG.SDD#928 (comment)).

Records. All three are append-only. Every baseline record keeps its original bytes.

• governance/neutral-binding-producer-caller-frontier (boundary). This supersedes 9cf90b3a….
  • Published 1.14.0 stops after planning and always exits 1.
  • Source at 282741b1 (prepared as 1.15.0, unpublished) does three things:
    • runs admitted commands through the GateExecution held-cwd host under the Verify capture owner;
    • accepts only fsgg.governance-handoff@2.x evidence that Governance observes itself;
    • blocks required capabilities that are not accepted.
  • Profile limits are stated.
  • Still open: publication, the installed SDD re-run, the physical cases and teardown. C2 is not complete.
• governance/provider-verify-sdd-codec-skew (decision). Verify keeps the bundled SDD 2.3.0 codec while admitting SDD 2.4.0 provenance.
  • The provenance, policy and admission modules are byte-identical between c8aea928 and c1fee66a.
  • On that path Implement the #1103 body-line sentinel: human-block (Blocked on: human/decision|action) refused-by-construction, and the Paths:none epic-vs-chore split #1116 is the only 2.4.0 change, and it only changes data.
  • Strict parsers refuse any future codec change.
• governance/provider-verify-workspace-catalog (boundary).
  • Provider-mode gates come from the workspace's own .fsgg catalog, never from provider provenance.
  • Workspaces scaffolded through the catalog route get no Governance overlay; C3.1-03 had to hand-write one.
  • The supplier at creation is workspace composition (Templates#441 / C4).

Citations. All are immutable revisions with file sha256:

• Governance 282741b1 and f97de157;
• SDD c1fee66a.

Mechanics.

• The seed mirrors under .agents and .claude are byte-identical.
• registry/driver-skill-manifest.json was regenerated with scripts/generate-driver-manifest --write for the seed catalog digest.

Local checks.

• python3 tests/atlas/check.py --baseline <merge-base> passes: 371 records, 699 local citations verified.
• scripts/generate-driver-manifest --check reports current.
• scripts/skill-view-parity.sh reports AGREE.
• tests/skill-quality/run.sh passes.

Revision after review. An independent review of 0d6262bb returned REQUEST_CHANGES because the branch conflicted with main (#4813 added a record), not because of record content. This version:

• rebuilds the branch on 65a71ad2;
• recaptures the records, adding 2.3.0-side citations for the byte-identity claim and two explicitly unclaimed items to the frontier record;
• regenerates the manifest.

Merge hold. Released by the coordinator.

🤖 Generated with Claude Code

[EHotwagner]

fdev: relaying the independent fsgg-critic-best (opus) review of PR #4830.

• Head 0d6262b: REQUEST_CHANGES. The branch conflicted with main and required CI had not run. Record content was accurate: all 14 citations matched, the supersession was legitimate, and nothing was overclaimed.
• Head a8af258: ACCEPT, after rebuilding on main and applying the nonmaterial points (2.3.0-side citations, and two items now listed as unclaimed).
• Head 15bb27d: ACCEPT on mechanical re-check after main moved again (Capture Home execution route, LEARN profile, privilege policy and release/board lessons in Atlas #4829, Add read-only hosted qualification of the retained knowledge upgrade R3 (Refs #4822) #4828).
  • Records are byte-identical to the accepted ones.
  • The catalog union keeps every main digest, including the 7 from Capture Home execution route, LEARN profile, privilege policy and release/board lessons in Atlas #4829, and adds only the 3 new ones (371 records).
  • No id collisions.
  • tests/atlas/check.py --baseline 65a71ad2 passes.
  • Seed mirrors are byte-identical.
  • The manifest diff touches only the atlas entry.
  • CI: 53 pass, 2 skipping.