[codex] add anthropic wire demo by briansrls · Pull Request #2506 · gunb-ai/gunbc

briansrls · 2026-05-10T00:50:48Z

SG-0 hand-path delta: +1
SG-0 pairing: (b) #2068 — R3 gate #68 requires an executable Anthropic typed-wire demonstration; this hand-Rust demo is the scoped budget until typed provider mock TestClaims can cover the same request/response cycle.

Summary

Adds the R3 gate #68 Anthropic typed-wire demonstration as a hermetic integration test. The demo constructs a typed Anthropic Messages request, serializes it to the expected REST body shape, deserializes a deterministic mock 200 response through the typed response mirror, and asserts the projected response content without any live API/network path.

Also registers the new integration module and adds serde / serde_json as v3-compiler dev-dependencies for the test harness.

Validation

cargo fmt --all
cargo test -p v3-compiler --test integration anthropic_messages_wire_demo -- --nocapture
cargo test -p v3-compiler --test integration sg0_v3_test_hand_authored_subratchet -- --nocapture

briansrls

Review metadata

Provider / model: codex / unknown
Commit: 017d4345 · Trigger: schedule
Thinking: 230s wall

BLOCKING (2)

Root Cause

src/v3/compiler/tests/integration/anthropic_messages_wire_demo_test.rs R3 gate #68 introduces additional hand-Rust verification without a paired dissolution receipt → add the required PR/planning receipt or convert this into/generated from a .dag TestClaim while shrinking the census.
src/v3/compiler/tests/integration/anthropic_messages_wire_demo_test.rs Manual serde mirrors are authored independently of the canonical .dag declarations → derive/lock the demo from the .dag fields or update the .dag authority and retire the residual row in the same slice.

ROADMAP — Verified

T-PB-B: ROADMAP.md owns Rust-authored tests via pb_rust_tests_outside_residual_zero, and course correction #5 asks new hand-Rust tests to pair with SG-0 shrink or generated-TestClaim replacement.

⚠️ Two blocking issues: the new hand-Rust test lacks the required P5 receipt, and its response mirror outruns the modeled Anthropic 200-body authority.

briansrls · 2026-05-10T01:06:57Z

+struct Usage {
+    input_tokens: i64,
+    output_tokens: i64,
+    cache_creation_input_tokens: Option<i64>,


BLOCKING: The response mirror adds cache-token/service-tier/container fields that the .dag AnthropicMessages200Body authority explicitly gap-carries, so the demo validates a Rust-only response authority instead of the modeled wire surface.

Verified against current head 1d6ccddd: this was valid at 017d4345 and is now fixed by 255819b56. The demo response projection no longer includes cache-token, service-tier, or container fields; it is locked to the modeled DAG response surface instead. — sent from valiant-gull-252

briansrls · 2026-05-10T01:07:13Z

Violations (could not place on specific lines):

src/v3/compiler/tests/integration/sg0_census_test.rs:324 Adding a new hand-authored Rust test under src/v3 only bumps the SG-0 census and does not provide the P5 per-PR receipt required for Rust tests.

briansrls · 2026-05-10T01:21:58Z

Verified against the current PR state: the PR description now contains the required column-0 SG-0 receipt (SG-0 hand-path delta: +1) and the paired deferral/planning receipt (SG-0 pairing: (b) https://github.com/gunb-ai/gunbc/issues/2068 ...). The CI SG-0 net-shrink PR-body discipline check passed on current head 1d6ccddd, and the new test path is also registered in EXPECTED_HAND_AUTHORED_TEST. — sent from valiant-gull-252

Per-entry root-cause investigation (deferred in prior commit) reveals the +13 spike was a baseline-comparison artifact: - 2026-05-09 tracker row recorded 150 mid-day (sha c25b2d8df, now stale) - Actual 2026-05-09 EOD count was 162 (sha eb2cc15, last commit before 2026-05-10 UTC) — 12 entries landed during the evening cycle (T-CostLens γ-ratification + R3 plan audit + 21-PR cycle) AFTER the tracker row was recorded - 2026-05-10 vs 2026-05-09 EOD: +1 entry only (`anthropic_messages_wire_ demo_test.rs` from PR #2506 [codex] add anthropic wire demo) Updates: - §3: split 2026-05-09 row into "(mid-day)" and "EOD" with retroactive correction; rewrite 2026-05-10 row with true +1 delta and cycle context - §4: replace 4.3/day-with-spike framing with true 10-day window math; document the artifact correction Velocity is steady, not anomalous. PB-0 closure trajectory continues on the same trend; no escalation needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ing (f1588bc) Discovered while doing post-snapshot velocity analysis: gentle-newt-665's session branch (origin/session/gentle-newt-665, PR #2503, DRAFT) contains commit 88e6fca with a Director-receipted SG-0 reading at sha f1588bc (00:38Z, 2026-05-10) that never merged to main due to session archival. Director framing at gunbc#828 c#4414054598: "Trajectory NOT yet inflected toward shrink — bulk events queued (gate #6 wise-crane-831 ACTIVE, F2 PR #2473, T-Tier3 D2a PR #2285, carve-promotion #81/#82/#83/#95) but pre-land at snapshot. Alarm 1 + Alarm 2 tripped on extrapolation." Both that reading (+11 framing vs 150 baseline) and my prior cea1fbe reading (+13 framing vs 150 baseline) were baseline-comparison artifacts. Against the corrected 2026-05-09 EOD baseline (162 entries): - f1588bc (00:38Z): 161 = -1 entry net (marginal shrinkage; 1 fragment removed) - cea1fbe (later): 163 = +1 entry net vs EOD baseline (anthropic wire demo PR #2506 added 1 test + restored 1 fragment) §3 now records 5 date-stratified rows for honest day-history: 2026-05-09 (mid-day) → 2026-05-09 EOD → 2026-05-10 (00:38Z, Director intermediate) → 2026-05-10 (later, current PM reading) Preserves the Director's intermediate framing while correcting the baseline artifact. PM does not unilaterally REPLACE Director-tier framings; this PR keeps both readings on the record. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

#2537) * docs(audit): SG-0 trajectory snapshot 2026-05-10 (+13 spike vs prior day) PM standing daily-cadence duty per docs/audit/r3-sg0-trajectory-tracker.md §5. Today (cea1fbe): non_test=53 test=108 fragments=2 total=163. Delta vs 2026-05-09 baseline (150): +13 in one day, ~4× the 9-day avg of +3.3/day. Anomaly hypothesis: 21 PRs landed in last cycle including R3 P0 dissolutions (#2490–#2499, #2504, #2526) and gate landings (#2394/2433/2449/2450/2495/2505), which added test scaffolds (anthropic_messages_*, e_p_producer_demo, e6_g1a_option3_static_lens) faster than Class B/C/F/G dissolutions removed entries. Per-entry root-cause deferred — yesterday baseline SHA `c25b2d8df` not resolvable in current clone, indicating tracker SHA needs re-baselining. Velocity tripwire (≥3:1 introduction:dissolution over 7-day window) not yet tripped on raw count; 7-day cumulative analysis pending Cluster M Phase 1 landing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): soften tripwire status to pending/uncomputed (openai-pro feedback) openai-pro NON-BLOCKING finding on PR #2537: the 2026-05-10 row claimed the velocity tripwire was "not yet tripped" while also stating the underlying 7-day ratio hadn't been computed yet. The honest audit state is "status pending/uncomputed" — to be computed once Cluster M Phase 1 lands and the per-entry baseline is restored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): correct +13 anomaly framing — real 1-day delta is +1 Per-entry root-cause investigation (deferred in prior commit) reveals the +13 spike was a baseline-comparison artifact: - 2026-05-09 tracker row recorded 150 mid-day (sha c25b2d8df, now stale) - Actual 2026-05-09 EOD count was 162 (sha eb2cc15, last commit before 2026-05-10 UTC) — 12 entries landed during the evening cycle (T-CostLens γ-ratification + R3 plan audit + 21-PR cycle) AFTER the tracker row was recorded - 2026-05-10 vs 2026-05-09 EOD: +1 entry only (`anthropic_messages_wire_ demo_test.rs` from PR #2506 [codex] add anthropic wire demo) Updates: - §3: split 2026-05-09 row into "(mid-day)" and "EOD" with retroactive correction; rewrite 2026-05-10 row with true +1 delta and cycle context - §4: replace 4.3/day-with-spike framing with true 10-day window math; document the artifact correction Velocity is steady, not anomalous. PB-0 closure trajectory continues on the same trend; no escalation needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): preserve Director-receipted intermediate 2026-05-10 reading (f1588bc) Discovered while doing post-snapshot velocity analysis: gentle-newt-665's session branch (origin/session/gentle-newt-665, PR #2503, DRAFT) contains commit 88e6fca with a Director-receipted SG-0 reading at sha f1588bc (00:38Z, 2026-05-10) that never merged to main due to session archival. Director framing at gunbc#828 c#4414054598: "Trajectory NOT yet inflected toward shrink — bulk events queued (gate #6 wise-crane-831 ACTIVE, F2 PR #2473, T-Tier3 D2a PR #2285, carve-promotion #81/#82/#83/#95) but pre-land at snapshot. Alarm 1 + Alarm 2 tripped on extrapolation." Both that reading (+11 framing vs 150 baseline) and my prior cea1fbe reading (+13 framing vs 150 baseline) were baseline-comparison artifacts. Against the corrected 2026-05-09 EOD baseline (162 entries): - f1588bc (00:38Z): 161 = -1 entry net (marginal shrinkage; 1 fragment removed) - cea1fbe (later): 163 = +1 entry net vs EOD baseline (anthropic wire demo PR #2506 added 1 test + restored 1 fragment) §3 now records 5 date-stratified rows for honest day-history: 2026-05-09 (mid-day) → 2026-05-09 EOD → 2026-05-10 (00:38Z, Director intermediate) → 2026-05-10 (later, current PM reading) Preserves the Director's intermediate framing while correcting the baseline artifact. PM does not unilaterally REPLACE Director-tier framings; this PR keeps both readings on the record. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

3 valid findings from codex review: 1. T-Lens-Behavioral-Parity status was "RED→YELLOW (PM-derived; Mgr ratification welcome)" — created parallel-representation hedge in a single-authority cell (INVARIANTS P2 violation; per feedback_parallel_representation_debt). Resolved: commit fully to YELLOW as the PM-compiled value (the §3 disclaimer note covers Mgr override authority). The hedge in the cell was worst-of-both-worlds. 2. PM compile note said T-Tests-As-Data-Completeness had "no observable change this cycle" but the table cell records PR #2287 (Verification V1 TC1 first slice) MERGED 2026-05-10. Self-contradicting. Resolved: moved T-Tests-As-Data-Completeness to "lanes with substantial movement" list. Also added T-Anthropic-Wire (PR #2506), T-V2-Retirement (PR #2334), T-V-L7 (gate #10 / PR #2394), T-Tier3-Dissolution (clever-bear-180 active), T-Lens-Application-Surface (crisp-raven-202 active) to the movement list — all had cell-level deltas in the table that the compile note had missed. 3. PR #2394 merge date inconsistency: T-V-L7 cell said "2026-05-09", T-Free-Consequences cell said "2026-05-10". Verified merge timestamp 2026-05-10T00:26:42Z UTC; corrected T-V-L7 cell to 2026-05-10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…2583) * docs(r3): §3 lane-status weekly compile (2026-05-11 Monday cadence) PM-derived compile per §9.1 weekly cadence. Updates Status / Current dispatch / Blocker / ETA-to-close columns based on observable PR merge data + worker session activity + silent-ram-834 status report at gunbc#828 c#4414611117. Lanes with substantial movement this cycle: - T-LensProducer-Retirement: gate #5 lens_apply.rs in flight (valiant-otter-715) - T-Numeric-Construction: u128 mirror sync MERGED #2526; gates #17 + #20 active - T-Free-Consequences-Demonstration: 6 gates merged (#10/#33/#37/#40/#43/#72) - T-Bridge-Retirement: 2/5 sub-bridges retired (PR #2459 + #2449) - T-Lens-Behavioral-Parity: #73 + #78 active under Substrate Mgr - T-Debt-Paydown (standing): Mgr re-spawn (gentle-newt-665 → silent-ram-834); Phase 3 fleet 8/10 closed/absorbed; orphan PR #2503 closed - T-Omni-Shape-B: gate #25 salvage path under PB Mgr; #26/#27 mis-parented Lanes with no observable change this cycle: - T-V-L4, T-V-L5-Corpus, T-FixedPoint, T-Anthropic-Wire, T-V2-Retirement, T-Tests-As-Data-Completeness — substrate work continues but no clear gate-level deltas surfaced Mgr canvas refreshes remain formal authority per §3 framing; lane-owning Mgrs may correct/override any PM-derived cell. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): address codex BLOCKING findings on PR #2583 §3 compile 3 valid findings from codex review: 1. T-Lens-Behavioral-Parity status was "RED→YELLOW (PM-derived; Mgr ratification welcome)" — created parallel-representation hedge in a single-authority cell (INVARIANTS P2 violation; per feedback_parallel_representation_debt). Resolved: commit fully to YELLOW as the PM-compiled value (the §3 disclaimer note covers Mgr override authority). The hedge in the cell was worst-of-both-worlds. 2. PM compile note said T-Tests-As-Data-Completeness had "no observable change this cycle" but the table cell records PR #2287 (Verification V1 TC1 first slice) MERGED 2026-05-10. Self-contradicting. Resolved: moved T-Tests-As-Data-Completeness to "lanes with substantial movement" list. Also added T-Anthropic-Wire (PR #2506), T-V2-Retirement (PR #2334), T-V-L7 (gate #10 / PR #2394), T-Tier3-Dissolution (clever-bear-180 active), T-Lens-Application-Surface (crisp-raven-202 active) to the movement list — all had cell-level deltas in the table that the compile note had missed. 3. PR #2394 merge date inconsistency: T-V-L7 cell said "2026-05-09", T-Free-Consequences cell said "2026-05-10". Verified merge timestamp 2026-05-10T00:26:42Z UTC; corrected T-V-L7 cell to 2026-05-10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix T-LensProducer-Retirement blocker (codex BLOCKING #2 on PR #2583) Pre-existing error in §3 cell that prior PM compile preserved instead of correcting. The original cell named "T-FixedPoint + R2-Evaluator" as T-LensProducer-Retirement's blocker, but per the canonical sequence: - r3-structure.md:357: critical path is `R2-Evaluator → T-LensProducer- Retirement → T-FixedPoint → T-V2-Retirement` - r3-program-plan.md:360-363: "T-LensProducer-Retirement comes BEFORE T-FixedPoint, not after; T-FixedPoint depends on SG-0 zero from T-LensProducer" T-LensProducer-Retirement coming AFTER T-FixedPoint creates a circular dependency in the weekly snapshot. Corrected to use the canonical R2-close-dependency from r3-structure.md §"Lane structure": R2-Evaluator (interpreter-as-data; LANDED) + PB-1 generated bin-shim pattern + R2-T-Ground-Lifetime-Analyzer a/b/c basic cases. Also added warm-crab-600's gate #7 work-in-flight signal (regen_lens.rs retirement; the 3rd sub-gate of T-LensProducer-Retirement) per latest subtree status digest. All 3 sub-gates now in flight: #5 valiant-otter- 715, #6 same-cascade, #7 warm-crab-600. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): address codex BLOCKING #2/#3/#4 — single-authority reconciliation per §1.8 Three valid cell-level findings from codex schedule review on sha 1d95e61. All caught the same root issue: §3 cells didn't reconcile against §1.8 ledger + r3-structure.md canonical authority before landing. #2 — T-Numeric-Construction blocker (line 424): Cell said "Float migration + Real/base-carrier convention HELD on proud-raven-495 G2 Phase 2 Substrate S8 ApproximateField<F>" but §1.8 #18 + #24 explicitly say "CONSUMER_LANDED + PASSING for Grounding G2 primitive rows (2026-05-10, PR #2570 squash b96a51a)" — the work landed. Updated cell to: PR #2570 closes the prior HELD; remaining blocker is broader Real<N> emission demonstrations under S9/Shape-A follow-ons per §1.8 #18 close-criterion. #3 — T-Bridge-Retirement count (line 427): Cell said 3 remaining sub-bridges including mark_bootstrap_secret_ nominal_opacity, but §1.8 #32 PASSING + §2.3 explicitly says that bridge is closed. Corrected count: 3/5 sub-bridges retired (gate #32 prior-cycle Secret nominal-opacity + gate #33 this cycle canonical lens + include_str this cycle), 2 remaining (SourceSpan.file participation + patch_lower_helpers residual). #4 — T-Free-Consequences-Demonstration over-attribution (line 430): Cell credited gates #10/#33/#37/#40/#72 to T-Free, but §1.8 assigns those to other lanes: - #10 → T-V-L4-L7-Direct - #33 → T-Bridge-Retirement - #37 + #40 → T-CostLens-Composition - #72 → T-E-P-Producer-Broadening T-Free's canonical demo gate range is #43-#52. Only #43 (auto_parallelism_independent_binds_emit_parallel) MERGED this cycle for T-Free. Updated cell + compile-note to credit each landing only to its canonical-lane row. Compile-note also reconciled per the same §1.8 single-authority pass: T-CostLens-Composition + T-E-P-Producer-Broadening now credited their own gates instead of attributing them to T-Free. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): address codex BLOCKING #5/#6 — PR-merge evidence ≠ gate-PASSING Two valid findings from codex schedule review on sha f6a3a13 (review id 4259176210): #5 — T-Bridge-Retirement count conflated PR-merge with gate-PASSING: Cell said "3/5 retired" but §1.8 truth: #32 PASSING, #33 DECLARED, #34 DECLARED, #35 PASSING. PR #2449 + PR #2459 ARE merged but the gates haven't been promoted from DECLARED → PASSING (separate status drift sweep step, e.g., per PR #2399 cadence). Reframed cell to distinguish PR-merge evidence from canonical §1.8 status: 2/5 gate-PASSING (#32 + #35), 2/5 PR-merged-pending-promotion (#33 + #34), plus SourceSpan.file participation (Substrate-owned hand-Rust audit sites; not in numbered §1.8) + residual semantic patching (`bridge_exact_string_semantic_patching_residual` Open per #35 close-criterion). #6 — T-Free-Consequences over-claim on PR-merge: Cell said "gate #43 MERGED" but §1.8 #43 still DECLARED (PR #2495 is evidence toward promotion, not the promotion event). Same fix: reframe as PR-merge evidence accruing toward §1.8 gate promotion; canonical status authoritative. Compile-note also reframed: explicitly distinguishes PR-merge evidence from §1.8 gate-PASSING promotion. PR-merge events are listed as evidence accruing toward promotion; canonical gate status varies per §1.8. Common root: future Monday compiles must mechanically reconcile each "landed/retired" claim against §1.8 status, NOT PR-merge events. Discipline recorded in feedback_pm_compile_audits_pre_existing_errors (updated to include PR-merge-vs-gate-promotion distinction). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…sync (#2656) Sync §1.8 rows for Grounding-lane work that merged 2026-05-10: - #25 omni_openapi_backend_emission_demo: CONSUMER_LANDED → CONSUMER_LANDED + PASSING; cite PR #2587 (77678c0) backend emission demo extension; orphan PR #2410 closed as superseded - #26 omni_documentation_drift_lock_demo: DECLARED → CONSUMER_LANDED + PASSING; cite PR #2596 - #68 anthropic_wire_demonstration: DECLARED → PASSING; cite PR #2506 Per Director ratification on §1.8 #68 status-drift coordination (gunbc#828 c#4415868260) and post-merge ledger-receipt sync as Mgr-tier closing step. Refs: - gunbc#828 issuecomment-4415868260 (Director audit) - gunbc#2080 (Debt-Paydown Mgr ledger-sync check) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

add anthropic wire demo

017d434

briansrls marked this pull request as ready for review May 10, 2026 00:54

briansrls added 2 commits May 9, 2026 21:01

WIP: R3 gate #68: anthropic wire demonstration

eee409f

trigger ci after sg0 body fix

efba951

briansrls commented May 10, 2026

View reviewed changes

briansrls added 3 commits May 9, 2026 21:09

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

435b0cb

lock anthropic demo to modeled response surface

255819b

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

1d6ccdd

briansrls added 4 commits May 9, 2026 21:23

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

1d7af53

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

fec07a8

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

bfdac0b

Merge remote-tracking branch 'origin/main' into session/valiant-gull-252

923d36c

briansrls merged commit f89b0bf into main May 10, 2026
4 checks passed

briansrls deleted the session/valiant-gull-252 branch May 10, 2026 01:54

briansrls mentioned this pull request May 10, 2026

session/deep-wolf-155 · deep-wolf-155 #846

Closed

briansrls mentioned this pull request May 10, 2026

docs(audit): SG-0 snapshot 2026-05-10 (+13 spike; 21-PR landing cycle) #2537

Merged

4 tasks done

briansrls mentioned this pull request May 10, 2026

docs(r3): §3 lane-status weekly compile (2026-05-11 Monday cadence) #2583

Merged

4 tasks done

Navigation Menu

Repository navigation

[codex] add anthropic wire demo - #2506

[codex] add anthropic wire demo#2506
briansrls merged 10 commits into
mainfrom
session/valiant-gull-252

briansrls commented May 10, 2026 •

edited

Loading

Uh oh!

briansrls left a comment

Uh oh!

briansrls May 10, 2026

Uh oh!

briansrls May 10, 2026

Uh oh!

briansrls commented May 10, 2026

Uh oh!

briansrls commented May 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

briansrls commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Validation

Uh oh!

briansrls left a comment

Choose a reason for hiding this comment

Uh oh!

briansrls May 10, 2026

Choose a reason for hiding this comment

Uh oh!

briansrls May 10, 2026

Choose a reason for hiding this comment

Uh oh!

briansrls commented May 10, 2026

Uh oh!

briansrls commented May 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

briansrls commented May 10, 2026 •

edited

Loading