Go worksheets post-#4149 reconciliation (R2b int64 anchor, SG-1 §3.1 dual-name, Go RCA lane)

[briansrls]

Auto-opened by session-dashboard for session zesty-otter-480.
Pushing to session/zesty-otter-480 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: d8abdb8b · Trigger: schedule
• Thinking: 236s wall

---

Non-blocking — Strengths

• docs/planning/v4-go-leaf-model-verification-worksheet-2026-06-01.md R2b now consistently anchors on go_facts_int64, matching the int64 fixtures and Go integer-overflow semantics at https://go.dev/ref/spec#Integer_overflow.
• docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md The SG-1 dual-name text keeps TargetAtomRealization as the single row authority while making the leaf-model fact_id projection explicit.

✅ Docs-only reconciliation is consistent with the thesis, P2/P5, and the inspected v4 Go/Rust authority patterns; no blocking concerns found.

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: d8abdb8b · Trigger: manual
• Comparison: main @ 9e33792c ... session/zesty-otter-480 @ d8abdb8b
• Conversation: View conversation

---

1. Story of the diff

This PR is a post-#4149 planning reconciliation for the Go worksheet lane. It fixes the Go R2b leaf-model path so the claim no longer says “platform int overflow” while the fixture is actually an int64 overflow exercise: the CI runner worksheet, verification worksheet, and authority map now all route R2b through leaf_model_claim_go_r2b_int64_silent_overflow_truncates and the go_facts_int64 bundle, while leaving R2a on platform go_facts_int as before.

The second thread is SG-1 naming/dispatch cleanup for Go TargetAtomRealization: the worksheet now makes the Rust-style dual-name pattern explicit, with go_target_atom_realization_symbol as the actual TargetAtomRealization row and go_atom_realization_symbol as the fact-id symbol consumed by leaf-model R3. That is paired with a lane ownership clarification: Arbiter owns the shared carrier shape, while Go RCA owns the Go rows, fact ids, and emit-consumption dispatch.

2. Invariant categories

1. LAYER MODEL (substrate vs implementation).

Compliant — the diff is documentation/planning only, but it is substrate-adjacent because it directs future go.dag facts. The important modeling decision is correct: R2b is anchored to the width-specific go_facts_int64 bundle rather than the platform-int go_facts_int bundle at docs/planning/v4-go-leaf-model-verification-worksheet-2026-06-01.md:139 and reinforced at :143/:175. The SG-1 side also preserves the shared substrate carrier by saying src/v4/std/target_model.dag remains canonical and by reusing TargetAtomRealization rather than creating a Go-local carrier at docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md:5, :70-73, and :92.

1. INVARIANTS.md + modeling-discipline.md.

Compliant — P1/P2 are handled directly. P1 modeling faithfulness is improved because the claim now matches the fixture width: go_facts_int64 + int64 source, with R2a explicitly remaining on platform go_facts_int at docs/planning/v4-go-leaf-model-verification-worksheet-2026-06-01.md:139 and :143. P2 single-authority is also handled: the SG-1 worksheet says go_atom_realization_symbol is a fact id naming the go_target_atom_realization_symbol row, i.e. one row with two named projections, at docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md:48-49 and :70-73. This is shared reads of one resolved fact, not parallel representations. The diff introduces no coproducts, predicate helpers, walkers, hand-rolled validators, or undeclared sums.

1. CODING.md.

Compliant — no Rust implementation code is changed. For the Markdown planning surface, the new prose is load-bearing and compact: docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md:66-73 adds a role/consumer table instead of a long explanatory block, and :86 replaces a potentially ambiguous “Coordination” handoff with a concrete dispatch boundary. I do not see comment/prose bloat that would obscure the decision being made.

1. TESTING.md.

N/A — this is a worksheet/authority-map reconciliation, not executable code or a landed .dag claim implementation. The diff does update the downstream test/CI contract by changing the R2b runner row to the new claim id at docs/planning/v4-go-leaf-model-ci-runner-worksheet-2026-06-01.md:59 and by keeping R2b on go run/go test only at docs/planning/v4-go-leaf-model-verification-worksheet-2026-06-01.md:139-143; no same-PR test is required for a planning-only rename/anchor correction.

1. LOCKED DESIGN DECISIONS.

N/A — the PR does not edit a locked design document or alter a locked carrier shape. It preserves the high-level target-model direction: target facts remain modeled in go.dag, and the shared TargetAtomRealization carrier remains in src/v4/std/target_model.dag.

1. TRACKED vs UNTRACKED DEBT.

Compliant — I do not see new unbounded TODOs, temporary scaffolds, or “later” shapes. The only staged dependency is explicit and bounded: the R3-external dependency requires both go_target_atom_realization_symbol and go_atom_realization_symbol to land together or in the same implementation wave at docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md:16-18, with the checklist repeating the dual-name receipt and Go RCA dispatch ownership at :95-96.

2.5. Top-down PM intent review

Compliant — this PR strengthens the PM-level intent rather than diluting it. The thesis requires target primitives and target realization to be structurally modeled, with target grounding failing closed rather than falling back to name-keyed shortcuts; the R2b change makes the Go worksheet’s proof surface match the actual int64 fixture instead of claiming a platform-int fact. chatgpt-review-aa834e4c-12d3-43…

The SG-1 clarification also fits the “model local, derive global” intent: Go authors its target row and fact id once, while consumers read the appropriate projection instead of inventing a second carrier. The diff’s lane change does not postpone the work or create permanent scaffolding; it assigns Go-specific rows and emit consumption to Go RCA while keeping the shared carrier under Arbiter ownership at docs/planning/v4-go-target-atom-realization-worksheet-2026-06-01.md:86.

3. Verdict

APPROVE. The diff consistently reconciles the Go R2b width anchor and the SG-1 dual-name contract across the affected planning surfaces, without introducing new substrate shapes, parallel carriers, untracked debt, or implementation/test drift.

[briansrls]

Closing as SUPERSEDED. These were Jun-1 planning worksheets (Go leaf-model/target-atom-realization/CI-runner). The emit-ladder authority is now ctrl#1489 (the 8-tier ladder); per the doc-authority ledger principle these worksheet docs are not a parallel ledger to maintain. Go target work routes through the T1+ ladder under Mgr-SPINE. Operator-authorized close (via still-raven-546).