[AdaWorldAPI]

What

hubspo-store::table::Table holds one dataset (tenant × object type, plan §5.5) in memory.

• Layout: resident U32 / I32 lanes, a live plane (plane 0), and one validity plane per nullable lane. planes() lends them to mask-risc; no read copies a lane.
• Writes: a Batch (inserts, updates, deletes) is validated as a whole and lands as exactly one new version, or not at all.
• Ownership: a table accepts only batches written for its own owner (the contract's MailboxId; write on behalf, one writer per mailbox).
• Refusals: wrong owner, wrong arity, wrong kind, a missing required value, an unknown lane, a deleted or absent row, and a row written twice in one batch (two updates of the same lane, update + delete, delete + delete). Order inside a batch carries no meaning, so a double write is ambiguous.
• Result: apply() returns Applied { version, first_insert, changed }. changed is the plane that list::refresh (D-QRY-2: active / static lists and membership history as mask programs #20) takes.
• Ordinals are never reused: inserts append, and deletes clear the live bit and leave the row inert. Static lists rely on this.

Persistence, one Lance version per published batch using P-SPARSE-1's base + sparse delta, is the other half of D-STO-1 and comes next. It will sit behind a feature so this crate's default CI stays fast.

Evidence

• hubspo-store/tests/table.rs:
  • 60 random batches match a plain model on every lane and plane, with more than 200 updates and 30 deletes over the run.
  • All 12 refusal kinds leave the version, lanes and planes untouched. Each refused batch also carries a valid insert, so a partial apply would show.
• hubspo-query/tests/store_list.rs runs end to end: catalog → filter compiler → list::refresh, fed by the store's own changed plane. Over 50 batches it equals a full recomputation.

Disable runs; every one went red:

• owner not checked;
• deletes missing from changed (red in the store test and in the list test);
• a delete that keeps the row live;
• a cleared value that keeps its validity bit;
• the version not incremented;
• the conflict check turned off;
• updates to deleted rows allowed;
• lane kind not checked.

Workspace fmt, clippy (--all-targets --no-deps -D warnings), tests and hubspo-guards are green locally. No serde in zone 2. Rebased on main after #21; no other HubSPO-rs PR is open.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PPcakjk7ioQsnasmNDtc5z

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.