Repository navigation
D-SPOG-W-0: the Witness slot as a SPOG sub-context under classid-G - #1371
Conversation
A SPOG coordinate read from (classid, CausalEdge64) with no stored column: S/P/O are the resident bytes, G is graph_of(classid) (the existing "g via classid" rule), and the Witness slot is a sub-context inside G for classes that declare that reading. Slot 0 reads as no anchor. Undeclared classes, another reading of the slot, and v1/unknown provenance refuse. Compared with the real MailboxSoA::apply_edges routing: within one graph it accepts exactly the edges in the same SPOG context on all 64 x 64 slot pairs; across graphs it diverges, because routing reads no classid. Recorded as ISS-MAILBOX-ROUTES-WITNESS-WITHOUT-GRAPH; not fixed here. 7 tests, 6 disable runs red, 0 allocations. Board: D-SPOG-W-0 row and entry, ISSUES row; D-GSO-AFF-0 marked Shipped (#1370). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T8w7Ucm7NhitfTduFKmhYx
|
Warning Review limit reachedYour organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Next included review available in 21 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 69 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (8)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: d526f83e-9fa0-4c5a-ae75-a0a0f48ea56c) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: b1aa0b2f-5fab-4c1b-89b6-2bc64fce7b60) |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Re-running the failed job once to confirm. If it fails again on the same error, the fix is a dependency pin, which would need its own PR. Generated by Claude Code |
The heap meter kept MEASURING per thread but BYTES global. The test harness runs tests on parallel threads, so loco_execution_needs_a_gathered_copy (which measures its own 364-byte allocation) could land in readings_allocate_nothing's window and fail it with left: 364. BYTES is now thread-local like MEASURING. Measured locally: the old version fails 20/300 runs of the test binary, this one 0/300. The can-fire half (materialize_indices allocates) still passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T8w7Ucm7NhitfTduFKmhYx
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 7eccc70b-e733-46f5-a464-a167bb8cbbf8) |
… a declared local source D-ALPHA-G-0 (alpha_world_provenance_probe): an epistemic event is (Alpha-attended address, CausalEdge64). WorldG = graph_of(addr), the order of worlds is the SpogTenants route. Same edge bits in two worlds are two events; replaying the same claims recovers the world sequence with all-zero edges; changing edge fields never moves the world; partitioned by recovered world each MailboxSoA holds only its own deliveries through the unchanged apply_edges; an undeclared world is refused at the tunnel (NoTenant). 5 tests, 5 disable runs red. D-WA-0 (witness_angle_probe): (class, generation, w_slot, bits 43..45) -> SourceCoord under a probe-local sparse law. Same bits mean different sources in another class and another generation; classes reading the bits as the pathology triad or a cohort WitnessTable refuse, as do undeclared classes and generations, Witness 0 and v1/unknown provenance. World from the attended key, never the edge. 0 allocations; 7 tests, 7 disable runs red. Reframe: ISS-MAILBOX-ROUTES-WITNESS-WITHOUT-GRAPH resolved as a false positive. The #1371 cross-graph case bypasses the split tunnel; apply_edges has no production caller; MailboxSoA stays graph-blind and gains no G check. spog_witness_probe docs corrected in place. Board: STATUS_BOARD (D-SPOG-W-0 Shipped #1371; D-ALPHA-G-0, D-WA-0 rows), ISSUES status, entry with the 10-point inventory, entries index. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T8w7Ucm7NhitfTduFKmhYx
Probe only. It adds no library code, persists nothing, and moves no CE64 bits.
Claim
A SPOG coordinate is a view over resident coordinates, not a storage layout.
graph_of(classid), the existing "g via classid" rule inspog_tenants.rsw_slot(), only for a class that declares this reading; slot 0 = no anchorWitness refines G and never replaces it. Undeclared classes, classes that declare another reading of the slot, and v1/unknown provenance all refuse.
Routing check against the real
MailboxSoA::apply_edgesISS-MAILBOX-ROUTES-WITNESS-WITHOUT-GRAPH. Fixing it is a production change and is not made here.Tests
Board: D-SPOG-W-0 status row and entry,
ISSUES.mdrow; D-GSO-AFF-0 marked Shipped (#1370).Also in this PR: one unrelated flaky-test fix
r2il-mask-abi-probe/tests/v3_v4_dual_reading.rskept its heap counter global while the measuring flag was per thread. A parallel test's 364-byte allocation could therefore failreadings_allocate_nothing. The counter is now thread-local. Measured: 20/300 failures before, 0/300 after. This fixes the redtestjob on this PR; the change is test-only.🤖 Generated with Claude Code
https://claude.ai/code/session_01T8w7Ucm7NhitfTduFKmhYx
Generated by Claude Code
Generated by Claude Code