Skip to content

D-VAS R1: E0 on the real mailbox (publication token, mailbox lane socket, route-bound admission) - #2061

Merged
AdaWorldAPI merged 8 commits into
claude/virtual-address-algebra-cleanfrom
claude/d-vas-r1-e0
Nov 13, 2026
Merged

AdaWorldAPI merged 8 commits into
claude/virtual-address-algebra-cleanfrom
claude/d-vas-r1-e0

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Stacked on #2060 (research baseline). First implementation step of the roadmap virtual-address-superpowers-roadmap-v1.md: stage E0, D-VAS-A1, D-VAS-A2, D-VAS-C2, D-VAS-D1, direct-class D-VAS-C1. Ledger: .claude/plans/d-vas-implementation-v1.md. Draft; not for merge without a merge decision.

What E0 is

real MailboxSoA -> publication -> routed data class -> admitted MethodBinding
                -> a lane borrowed over `reads` only -> one demanded read

No guard, no effect, no selection, no NodeGuid, no separate 0xF### lens.

Changes

crate change
cognitive-shader-driver MailboxSoA::published(&self) -> Published<'_, N>: a token that holds the shared borrow. No field added, no layout change.
lance-graph-dt64 BindStore::admit_routed(RouteAt, &MethodRef) and Refusal::NotRoutedClass. admit alone accepts a method of any registered class.
lance-graph-mailbox-lanes (new) MailboxLanes<'_, N>: LaneSource. Lends meta, last_active_cycle, last_write_cycle (u32) and edges, temporal (u64) as the owner's own slices, populated prefix only. One FrameStore per publication.

Why the frame is a borrow and not a counter

The lab plan (section 18, #2060) reads every mutation path of the mailbox: ten field setters and 19 public columns move neither current_cycle nor last_write_cycle; two writes in one cycle share a stamp; the cycle wraps onto the never-written sentinel. No stamp accounts for the writes a reader can see. What the owner can guarantee is that no column changes while a shared borrow is live. Published is that borrow, issued by the owner, and the socket's frame store lives exactly as long.

Consequence: no frame, binding or lane address survives a publication. A frame that outlives the borrow needs a revision every write moves, which needs the public columns to stop being assignable. That is recorded as BLOCKED, not worked around.

Tests

crates/lance-graph-mailbox-lanes/tests/e0.rs, 7 tests on a real MailboxSoA<64> (40 rows populated, heterogeneous values), committed before the first run. Oracle: the owner's public arrays and the generator functions.

  • every admitted read equals the owner's value; the lent slice has the owner's column address; the lane ends at the populated prefix
  • refused: a binding or frame of an earlier publication (across a set_meta that moves no stamp), two sockets over one publication sharing frames, another mailbox, another row order, another reader scope, a re-route, a foreign MethodRef with the same MethodId, another store's reference, a field outside reads, a field outside the basis, a basis naming a column the socket cannot lend (f32, u16, u8, [u8; 12] are refused by name)

Disable runs, each anchor asserted once and restored, all exit 101: route comparison skipped; all N rows lent; a lane number lending another column; the socket's own row-order/scope check; its own frame check. The last two passed at first because DT64 repeats both checks above the socket; a test that asks the socket directly was added.

Local: lance-graph-mailbox-lanes 7 (debug and release), lance-graph-dt64 117, cognitive-shader-driver lib + mailbox_cutover 131. Clippy -D warnings clean on lance-graph-dt64, lance-graph-mailbox-lanes (all targets) and cognitive-shader-driver (lib). cognitive-shader-driver --all-targets has three existing manual_is_multiple_of findings in examples/meta_prefilter_mask_probe.rs, a file this PR does not touch.

Not established

  • Reader scope: DR has no Scope issuer; the socket compares what the caller asserts.
  • Column names: urn:mailbox:<column> is this crate's naming; no contract names the mailbox's columns.
  • Cost: nothing is measured.
  • Selections, NodeGuid, guards, effects: R2 to R4.

Generated by Claude Code

…mailbox lane socket; E0 tests before the run

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
…rectly (two disables were not load-bearing)

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
…ventory delta; codegraph anchors follow the DT64 insertion

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2ec58e37-9c50-4e66-9dbb-996958d5bebf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

…exes regenerated

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-13T11:22:55.593181Z c9317e1 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c9317e15ef

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…n's socket (review finding), before the fix

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
…dress of another publication is refused (review finding)

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMMWgnUU9g7Ldyn6sbk
@AdaWorldAPI
AdaWorldAPI merged commit ca0e423 into claude/virtual-address-algebra-clean Nov 13, 2026
19 checks passed
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.

2 participants