Skip to content

docs(planning): SG-1b function-signature realization §10.0 worksheet - #4099

Merged
briansrls merged 2 commits into
mainfrom
session/sleek-badger-874
May 31, 2026
Merged

briansrls merged 2 commits into
mainfrom
session/sleek-badger-874

Conversation

@briansrls

Copy link
Copy Markdown
Contributor

Summary

  • Adds sibling §10.0 worksheet docs/planning/v4-sg-1b-function-signature-realization-worksheet-2026-05-30.md per proud-pike GO (msg_aacefee2).
  • Single-authority fact: TargetFunctionSignatureRealization at fn boundaries (Param/Return), consuming SG-1 TargetAtomRealization by source_carrier without duplicating the atom catalog.
  • Does not amend v4-sg1-target-atom-realization-worksheet-2026-05-30.md; worksheet-only, no implementation.

Test plan

  • Modeling DFS Manager §8 checklist closed (proud-pike-680)
  • keen-heron TR worker brief dispatched post-§8

Made with Cursor

briansrls and others added 2 commits May 31, 2026 07:14
Sibling worksheet for post-#3956 E0308 String↔Symbol fn-boundary residue;
defines TargetFunctionSignatureRealization without amending SG-1 atom scope.

Co-authored-by: Cursor <cursoragent@cursor.com>
Modeling DFS sign-off proud-pike-680 msg_a2db9528; TR dispatch authorized.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls

Copy link
Copy Markdown
Contributor Author

Review feedback triage (sleek-badger-874)

Claude (22786) — APPROVE, no findings: Verified on HEAD 28c09494. The diff remains planning-only (docs/planning/v4-sg-1b-function-signature-realization-worksheet-2026-05-30.md); no substrate/code. The worksheet’s P2 single-authority framing (TargetFunctionSignatureRealization in v4.std.target_model, SG-1 coupling via source_carrier, forbidden spot-fixes) matches the tree. No change required.

Cursor (22785) — APPROVE, no blocking findings: The 06_translate.dag diagnosis (type_expr_spelling_for_atom → binding_spellings on atom type wires vs SG-1 value path) was spot-checked against src/v4/compiler/06_translate.dag at HEAD — still accurate. Cursor noted §8 was OPEN at review time (d710db1); follow-up commit 28c09494 records proud-pike-680 §8 sign-off (msg_a2db9528): header READY-FOR-IMPLEMENTATION-DISPATCH, §8 checklist CLOSED, TR dispatch authorized to keen-heron. No further doc edits needed for review artifacts.

Merge readiness: CI green on 28c09494, mergeStateStatus=CLEAN, 2× dashboard APPROVE (claude, cursor), no REQUEST_CHANGES. Awaiting operator squash-merge per lane policy.

— sent from sleek-badger-874

@briansrls
briansrls merged commit c7217e8 into main May 31, 2026
10 checks passed
@briansrls

Copy link
Copy Markdown
Contributor Author

Review feedback triage (sleek-badger-874) — post-merge

Claude (22793) — APPROVE: Verified on merged squash c7217e83. Planning-only worksheet; single-authority carrier, SG-1 source_carrier coupling, forbidden spot-fixes, boundary falsification — all match docs/planning/v4-sg-1b-function-signature-realization-worksheet-2026-05-30.md on main. No findings; no commit.

Cursor (22795) — APPROVE: Verified 06_translate.dag:2120–2134 (type_expr_spelling_for_atom → binding_spellings) still matches worksheet DFS path on main. No substrate/code in merge; no rubric violations. No findings; no commit.

Status: #4099 MERGED 2026-05-31T07:20:05Z. Duplicate draft #4103 closed (superseded). Lane archived; keen-heron TR implementation per worksheet handoff.

— sent from sleek-badger-874

briansrls added a commit that referenced this pull request May 31, 2026
Refresh maturation tracker after #4097, #4099, #4100, and #4095 landings;
honest framing: probe PASS ≠ bridge deleted; still 0/6 v4-done PROVEN.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request May 31, 2026
…ets (#4109)

Refresh maturation tracker after #4097, #4099, #4100, and #4095 landings;
honest framing: probe PASS ≠ bridge deleted; still 0/6 v4-done PROVEN.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request May 31, 2026
…cement) — +184 delta vs #4086

Per PM dispatch 2026-05-31: re-run full-tree M1 probe + per-class delta vs
PR #4086 baseline. Substrate landings since #4086: #4099 SG-1b worksheet,
#4100 SG-RC worksheet, #4102 R3-internal, #4105 + #4107 substrate
(compute_fabric + cache_interface), #4115 P5 bridge replacement.

Headline (origin/main at d015b76):
- v2 emit diagnostics: 0 (SG-7 stays closed; confirms #4115 didn't regress)
- .rs files emitted: 345 (was 335; +10 substrate growth)
- rustc errors: 7175 (was 6991; +184 / +2.6%)
- E0423 (SG-1 closure check): 0 (stays closed across all 6 substrate PRs)

Delta concentration:
- E0107 (SG-2): +125 — biggest single delta; new compute_fabric/cache_interface
  carriers need type-arg projection; SG-2 worksheet path #3962 absorbs without
  shape change.
- E0308 (mixed): +43 — SG-1-FOLLOWON +13 (1317 → 1330 'expected String, found
  Symbol') + SG-RC-LAYERING +24 on TestClaim row + minor others.
- Other codes: ±0 to +6 each; long tail completely pinned.

No new SG-class signatures emerged. P3-D elastic core count UNCHANGED from
#4086: 8 active receipt-producing classes + 2 closed. All routing from
proud-pike-680 (msg_6db2dc9e) absorbs the delta:
- SG-1b worksheet #4099 absorbs the +13 SG-1-FOLLOWON.
- SG-RC-LAYERING worksheet #4100 absorbs the +80 SG-RC.
- SG-COLLECTION-PROJECTION (~170, no Δ) stays on SG-5/SG-6 amendment plan.
- SG-2 / SG-8 / SG-3-CASCADE: existing worksheet routings.

§6 includes a spot-correction of #4086's SG-3-CASCADE arithmetic (was
1191; actual sum is 761).

§7 explicit reads: P5 bridge replacement (#4115) did NOT regress v2 emit;
this catalog's 0-diagnostic line is the implicit non-regression receipt.

§8 NOT-list: not a worker dispatch (proud-pike's routing surface); not a
SG-1/SG-7 reopening; not a P5 bridge receipt (#4097 owns that); not a P1/
MW-D8 amendment.

Two files: catalog + raw probe summary verbatim.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…4086 (no new SG classes) (#4122)

* WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos

* docs(close/receipt): fresh M1 rustc probe post-#4115 (P5 bridge replacement) — +184 delta vs #4086

Per PM dispatch 2026-05-31: re-run full-tree M1 probe + per-class delta vs
PR #4086 baseline. Substrate landings since #4086: #4099 SG-1b worksheet,
#4100 SG-RC worksheet, #4102 R3-internal, #4105 + #4107 substrate
(compute_fabric + cache_interface), #4115 P5 bridge replacement.

Headline (origin/main at d015b76):
- v2 emit diagnostics: 0 (SG-7 stays closed; confirms #4115 didn't regress)
- .rs files emitted: 345 (was 335; +10 substrate growth)
- rustc errors: 7175 (was 6991; +184 / +2.6%)
- E0423 (SG-1 closure check): 0 (stays closed across all 6 substrate PRs)

Delta concentration:
- E0107 (SG-2): +125 — biggest single delta; new compute_fabric/cache_interface
  carriers need type-arg projection; SG-2 worksheet path #3962 absorbs without
  shape change.
- E0308 (mixed): +43 — SG-1-FOLLOWON +13 (1317 → 1330 'expected String, found
  Symbol') + SG-RC-LAYERING +24 on TestClaim row + minor others.
- Other codes: ±0 to +6 each; long tail completely pinned.

No new SG-class signatures emerged. P3-D elastic core count UNCHANGED from
#4086: 8 active receipt-producing classes + 2 closed. All routing from
proud-pike-680 (msg_6db2dc9e) absorbs the delta:
- SG-1b worksheet #4099 absorbs the +13 SG-1-FOLLOWON.
- SG-RC-LAYERING worksheet #4100 absorbs the +80 SG-RC.
- SG-COLLECTION-PROJECTION (~170, no Δ) stays on SG-5/SG-6 amendment plan.
- SG-2 / SG-8 / SG-3-CASCADE: existing worksheet routings.

§6 includes a spot-correction of #4086's SG-3-CASCADE arithmetic (was
1191; actual sum is 761).

§7 explicit reads: P5 bridge replacement (#4115) did NOT regress v2 emit;
this catalog's 0-diagnostic line is the implicit non-regression receipt.

§8 NOT-list: not a worker dispatch (proud-pike's routing surface); not a
SG-1/SG-7 reopening; not a P5 bridge receipt (#4097 owns that); not a P1/
MW-D8 amendment.

Two files: catalog + raw probe summary verbatim.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs(close/receipt): #4122 — fix §6 arithmetic per openai-pro (long-tail 58 → 115; SG-3-CASCADE includes E0308 mop-up)

openai-pro found that §6 published a contradictory long-tail count:
§2 already lists E0391=29, E0599=28, other=58 separately, but §6's
'Long tail (E0391 / E0599 / + 12 other codes)' said 58 — should be
29+28+58 = 115. Separately, SG-3-CASCADE row totaled only
E0277+E0573+E0560+E0369+E0121 (765), omitting the E0308 mop-up that
the cascade definition is supposed to soak up by construction.

Fixes:
- Long tail row: 58 → 115 (E0391 + E0599 + other 12 codes, sum verified).
- SG-3-CASCADE row: 765 → ~1,390 (adds unclassified-E0308 mop-up
  ~625 = 2905 total E0308 minus SG-1-FOLLOWON 1330 minus SG-RC-LAYERING
  ~780 minus SG-COLLECTION-PROJECTION ~170).
- Added an explicit arithmetic-reconciliation sub-table showing each
  bucket × code coverage × count, summing to ~7,175 ± 1 rounding band.
- Footnote on the probe-summary top-25 histogram summing to 7,174 vs §1's
  7,175 — single error in a code beyond top-25 (probe script truncates
  display at top-25; rustc log carries full population).

Catalog now publishes a single self-consistent residual count usable as
the live ratchet meter.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…rksheet)

Author TargetFunctionSignatureRealization in v4.std.target_model: a product
carrier (M6) keyed by SG-1 source_carrier + FunctionBoundarySite, with
signature_type_form sourced BY REFERENCE from the paired TargetAtomRealization
(no second atom catalog). Rust rows for Symbol x {Param, Return}; 06_translate
Arrow domain/codomain serialization consults signature realization before
binding_spellings while non-boundary decl sites keep SG-1 type_form authority.

Addresses codex BLOCKING review: register String target spelling; positional
catalog slots (no Conj edge-name collision, P2); disposition tags on new types.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…rksheet)

Author TargetFunctionSignatureRealization in v4.std.target_model: a product
carrier (M6) keyed by SG-1 source_carrier + FunctionBoundarySite, with
signature_type_form sourced BY REFERENCE from the paired TargetAtomRealization
(no second atom catalog). Rust rows for Symbol x {Param, Return}; 06_translate
Arrow domain/codomain serialization consults signature realization before
binding_spellings while non-boundary decl sites keep SG-1 type_form authority.

Addresses codex BLOCKING review: register String target spelling; positional
catalog slots (no Conj edge-name collision, P2); disposition tags on new types.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…signature String→Symbol realization rows per worksheet §6; close the Pareto subset of post-SG-1 E0308 String↔Symbol diagnostics. M6 prohibition (no N-arm identical-payload coproducts; mirror landed TargetTypeExpression {kind, node (#4118)

* feat(target): SG-1b function-boundary signature realization (#4099 worksheet)

Author TargetFunctionSignatureRealization in v4.std.target_model: a product
carrier (M6) keyed by SG-1 source_carrier + FunctionBoundarySite, with
signature_type_form sourced BY REFERENCE from the paired TargetAtomRealization
(no second atom catalog). Rust rows for Symbol x {Param, Return}; 06_translate
Arrow domain/codomain serialization consults signature realization before
binding_spellings while non-boundary decl sites keep SG-1 type_form authority.

Addresses codex BLOCKING review: register String target spelling; positional
catalog slots (no Conj edge-name collision, P2); disposition tags on new types.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* WIP: SG-1b implementation per #4099 worksheet (28c0949) — author function-si

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…ksheet (per #4086) (#4126)

* docs(receipt): SG-3-CASCADE cascade-only determination — no §10.0 worksheet (per #4086)

SG-3-CASCADE (trait/field/binary mop-up: E0277/E0573/E0560/E0369/E0121 +
residual-E0308) carries no independent missing modeled fact. Each band is the
rustc-visible consequence of a fact already owned by a primary class
(SG-1-FOLLOWON #4099, SG-2 #3962, SG-RC-LAYERING #4100, SG-8, SG-COLLECTION-
PROJECTION). A §10.0 worksheet's DFS-path / canonical-home fields would be empty
or duplicate a primary's — so no worksheet is warranted; authoring one would
invent substrate work that does not exist.

- New: docs/audit/v4-sg3-cascade-only-receipt-2026-05-31.md
  §0 determination, §2 per-band traceability (each → owning primary/worksheet),
  §4 falsifiable monotonic-dissolution criterion for the next post-primary probe.
- Resolves predicate-dependency-graph §3.3 ambiguity: SG-3-CASCADE row was
  "extend existing worksheet" (unnamed); now "retired (no worksheet)" — bands
  fan across five primaries, no single host to extend.

Docs-only; no code/substrate/.dag touched. Grounded in the committed #4122 live
ratchet meter (SG-3 bands pinned, zero-Δ vs #4086); no re-probe (would regenerate
identical numbers).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* WIP: SG-3-CASCADE §10.0 worksheet or cascade-only receipt — trait/field/binar

* docs(receipt): fix §1 measurement-basis wording — E0560 +4 is primary-driven, not "zero Δ" (openai-pro #4126)

§1 claimed the SG-3 named bands are "pinned (zero Δ)" and "the only motion is
residual-E0308," contradicting the adjacent table's E0560 +4 / named-subtotal +4.
Corrected: 4 of 5 named bands are zero-Δ; E0560 ticked +4, and that tick is
itself primary-driven (new SG-2 field-projection sites from #4105/#4107
substrate, per §2) — not independent SG-3 growth, which strengthens the
cascade-only thesis rather than weakening it. The −46 total is net of the +4
E0560 tick. No count changed; wording made internally faithful.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…4126 (#4130)

* docs(receipt): SG-3-CASCADE cascade-only determination — no §10.0 worksheet (per #4086)

SG-3-CASCADE (trait/field/binary mop-up: E0277/E0573/E0560/E0369/E0121 +
residual-E0308) carries no independent missing modeled fact. Each band is the
rustc-visible consequence of a fact already owned by a primary class
(SG-1-FOLLOWON #4099, SG-2 #3962, SG-RC-LAYERING #4100, SG-8, SG-COLLECTION-
PROJECTION). A §10.0 worksheet's DFS-path / canonical-home fields would be empty
or duplicate a primary's — so no worksheet is warranted; authoring one would
invent substrate work that does not exist.

- New: docs/audit/v4-sg3-cascade-only-receipt-2026-05-31.md
  §0 determination, §2 per-band traceability (each → owning primary/worksheet),
  §4 falsifiable monotonic-dissolution criterion for the next post-primary probe.
- Resolves predicate-dependency-graph §3.3 ambiguity: SG-3-CASCADE row was
  "extend existing worksheet" (unnamed); now "retired (no worksheet)" — bands
  fan across five primaries, no single host to extend.

Docs-only; no code/substrate/.dag touched. Grounded in the committed #4122 live
ratchet meter (SG-3 bands pinned, zero-Δ vs #4086); no re-probe (would regenerate
identical numbers).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* WIP: SG-3-CASCADE §10.0 worksheet or cascade-only receipt — trait/field/binar

* docs(receipt): fix §1 measurement-basis wording — E0560 +4 is primary-driven, not "zero Δ" (openai-pro #4126)

§1 claimed the SG-3 named bands are "pinned (zero Δ)" and "the only motion is
residual-E0308," contradicting the adjacent table's E0560 +4 / named-subtotal +4.
Corrected: 4 of 5 named bands are zero-Δ; E0560 ticked +4, and that tick is
itself primary-driven (new SG-2 field-projection sites from #4105/#4107
substrate, per §2) — not independent SG-3 growth, which strengthens the
cascade-only thesis rather than weakening it. The −46 total is net of the +4
E0560 tick. No count changed; wording made internally faithful.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs(planning): purge SG-3 single-authority conflict — retire it across all dispatch/count surfaces (codex + inline RC on #4126)

#4126 retired SG-3-CASCADE as cascade-only but only updated the §3.3 row +
state legend, leaving SG-3 still represented as dispatchable elsewhere in the
same planning artifact — two authorities for "is SG-3 dispatchable" (INVARIANTS
P2 single-authority). Resolved across all surfaces:

- §Path C (line 98): dropped SG-3 from "Workers extend ..." dispatch list;
  added explicit "SG-3 is NOT a dispatch target — retired cascade-only" note.
- Count surfaces (§P3 row line 11, §2 #4086 entry line 21, §3.3 header line 44,
  §3.3 footnote line 60): "8 active receipt-producing classes routed" →
  "8 receipt-producing classes — 7 dispatchable + SG-3-CASCADE cascade-residual."
  Keeps the #4086-catalog reconciliation (still 8 receipt-producing) while
  removing the dispatchability contradiction.

Follow-up to merged #4126; receipt unchanged. Docs-only — no code/substrate/.dag.

Closes #4086
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs(planning): "7 dispatchable" → "7 active across routing states" — precise count (openai-pro RC on #4130)

openai-pro flagged that "7 dispatchable" introduced a new dispatch-count
contradiction: of the 7 non-SG-3 classes, several are not worker-dispatchable
under the table's own legend (SG-1b=worksheet-needed, SG-RC-LAYERING=authoring,
SG-COLLECTION-PROJECTION=route-pending). Reworded all four count surfaces
(§P3 row, §2 #4086 entry, §3.3 header, §3.3 footnote) to "7 active across
routing states + SG-3-CASCADE retired cascade-residual" — the only binary
fact the count asserts is retired-vs-active, which matches the per-row state
column exactly. No claim that all 7 are dispatchable.

Docs-only — no code/substrate/.dag.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
…ANDED) — single-authority (codex + inline RC on #4131)

#4131 rebased the SG-1b row's count to #4122's 7,175 meter but left its routing
STATE stale ("worksheet-needed / NEW sibling worksheet"), while the same #4122
catalog (§6) and merged #4099 say the SG-1b worksheet has LANDED and only TR-lane
worker dispatch remains — two authorities for SG-1b state.

Aligned all live SG-1b state surfaces to #4122 §6 ("worksheet #4099 landed; TR
worker dispatch is next-step receipt"): §3.3 row :50 (state worksheet-needed →
routed), §5 owner table :113, §6 sequence row :138. Dropped now-unoccupied
`worksheet-needed` from the §3.3 footnote's active-states enumeration (kept in
the legend definitions). Action step :97 and timestamped historical notes
:125/:185 unchanged.

Docs-only — no code/substrate/.dag.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
… single-authority fix (follow-up to #4130) (#4131)

* docs(planning): rebase P3 error-count surfaces on #4122 live ratchet (7,175), not stale #4086 6,991 (codex + inline RC on #4130)

The predicate-graph reported #4086's 6,991-error meter as current P3 state at
three surfaces (§1 P3 row :11, §3.3 SG-1b row :50, §8 watchlist :159), but
#4122's post-#4115 catalog explicitly declares itself the live ratchet at 7,175
("replaces #4086 as the live meter; #4086 kept as the post-SG-1 baseline").
That left two P3 count authorities (INVARIANTS P2).

All three surfaces now cite #4122 7,175 as the live count; the 6,991 figure is
retained only where explicitly labeled as the post-SG-1 delta baseline. Single
P3 count authority restored.

Follow-up to merged #4126/#4130. Docs-only — no code/substrate/.dag.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs(planning): align SG-1b routing state to #4122 (worksheet #4099 LANDED) — single-authority (codex + inline RC on #4131)

#4131 rebased the SG-1b row's count to #4122's 7,175 meter but left its routing
STATE stale ("worksheet-needed / NEW sibling worksheet"), while the same #4122
catalog (§6) and merged #4099 say the SG-1b worksheet has LANDED and only TR-lane
worker dispatch remains — two authorities for SG-1b state.

Aligned all live SG-1b state surfaces to #4122 §6 ("worksheet #4099 landed; TR
worker dispatch is next-step receipt"): §3.3 row :50 (state worksheet-needed →
routed), §5 owner table :113, §6 sequence row :138. Dropped now-unoccupied
`worksheet-needed` from the §3.3 footnote's active-states enumeration (kept in
the legend definitions). Action step :97 and timestamped historical notes
:125/:185 unchanged.

Docs-only — no code/substrate/.dag.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <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.

1 participant