Skip to content

plan(D-AW): base single-sourced + OGAR per-app mint — the shrinkable two-place awareness model#731

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/happy-hamilton-0azlw4
Jul 18, 2026
Merged

plan(D-AW): base single-sourced + OGAR per-app mint — the shrinkable two-place awareness model#731
AdaWorldAPI merged 1 commit into
mainfrom
claude/happy-hamilton-0azlw4

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

Follow-up to the merged D-AW-1 plan (#730), folding two operator directives (2026-07-18) into the M20 awareness-assembly design. Docs-only (the plan file); no code carve yet.

The correction

The auditor's LAYOUT-GATED verdict audited "add 19 named ValueTenant variants to the base + Full mask." Operator ruling supersedes that: 19 named base variants makes every M20 shrink a base-layout edit + version bump + blast radius across every consumer — the opposite of shrinkable. The correct, shrinkable shape:

Layer Holds Override point Shrink
Baselance-graph-contract (one root), consumed by lance-graph-ogar + OGAR + ogar-vocab reserves ONE generic facet region + the FacetCascade shape. Content-blind. region size / ENVELOPE_LAYOUT_VERSION region stays reserved
OGARogar-vocab per-app mint mints classid → ClassView whose value_schema projects the awareness readings onto the region the mint (versioned per app) re-mint to drop redundant readings — no base edit

Awareness facets (A1–A7 + siblings) are OGAR-minted ClassView READINGS over one reserved region, not base enum variants → activation overridable in 2 places, cheaply tested, versioned, shrunken later (the M20 endgame: after jc measures redundancy, shrink by re-mint).

Reuses shipped substrate (#729 P4, same day)

  • MailboxSoaView::style_rails_at — the 6×(8:8) ClassView-selected reading of a 12-byte content-blind register ("one register, two readings").
  • The per-class doctrine (3248bd9): "reading is ClassView-selected PER ROW/CLASS, never per lane."
  • Awareness facets = additional style_rails_at-shaped readings; style_lane_at (226-atom FROZEN palette256) is the frozen sibling.

Prerequisites / re-scoping

  • Single-import (Place 1): close ENTROPY M21 (woa-rs/q2 NodeGuid hand-copies → one canon-node-bytes). symbiont is deprecated (surrealdb → OGAR); its bridge.rs copy retires with symbiont — not a fix target (drops the W2c SurrealDB arm from the live path).
  • Auditor re-audit: the delta is now reserve ONE region + the reading contract, not 19 variants — needs re-audit before any canonical_node.rs edit.

Rebased onto origin/main (picks up #729 P4 triangle bricks + the merged D-AW-1). CausalEdge64/EW64 stay for reference.

🤖 Generated with Claude Code

https://claude.ai/code/session_016b33swuXE23hKtqxsHu9p1


Generated by Claude Code

…e two-place model

Operator directives (2026-07-18) fold into the M20 assembly plan:

- Base layout has ONE root (lance-graph-contract), consumed by the
  OGAR-aligned cluster (lance-graph-ogar + OGAR + ogar-vocab). Awareness
  facets are OGAR-minted ClassView READINGS over one reserved facet
  region, NOT 19 named base ValueTenant variants — supersedes the
  auditor's bake-19 path. Activation overridable in 2 places (base
  region + OGAR mint); shrink later = re-mint (drop redundant readings),
  no base edit, no ENVELOPE_LAYOUT_VERSION bump.
- Reuses the mechanism #729 P4 SHIPPED the same day:
  MailboxSoaView::style_rails_at (6x(8:8) ClassView-selected reading) +
  the "one register, two readings, per-class-not-per-lane" doctrine
  (3248bd9). Awareness facets = additional style_rails_at-shaped
  readings, one rung wider; style_lane_at (226-atom FROZEN palette256) is
  the frozen sibling.
- Single-import prerequisite = close ENTROPY M21 (woa-rs/q2 NodeGuid
  hand-copies). symbiont is deprecated (surrealdb -> OGAR); its
  bridge.rs NODE_ROW_STRIDE copy retires with symbiont, not a fix target
  (drops the W2c SurrealDB arm from the live path).
- Auditor LAYOUT-GATED verdict re-scoped: the delta is now reserve ONE
  facet region + the reading contract, re-audit needed before any
  canonical_node.rs edit.

Rebased onto origin/main (picks up #729 P4 triangle bricks + the merged
D-AW-1 via #730). Doc-only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016b33swuXE23hKtqxsHu9p1
@cursor

cursor Bot commented Jul 18, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot 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: serverGenReqId_d70c3b2c-5ff5-4834-8c90-eee42bcb2668)

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@AdaWorldAPI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3eb7346d-93ec-4d71-a6cc-7277cae78ff2

📥 Commits

Reviewing files that changed from the base of the PR and between aa8a3a0 and 0886b22.

📒 Files selected for processing (1)
  • .claude/plans/soa-32-tenant-awareness-redundancy-v1.md

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

Comment @coderabbitai help to get the list of available commands.

@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review July 18, 2026 21:26
@AdaWorldAPI
AdaWorldAPI merged commit dbd7fe6 into main Jul 18, 2026
2 checks passed

@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: 0886b2269a

ℹ️ 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".

Comment on lines +95 to +96
`value_schema` projection is an **OGAR mint** (classid → ClassView), not a new
hardcoded `BUILTIN_READ_MODES` preset baked in `canonical_node.rs`. The code's

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep facet projections off value_schema

This plan makes the per-app awareness projection a ClassView value_schema, but the current contract's ClassView::value_schema returns only the ValueSchema enum preset (Bootstrap/Cognitive/Compressed/Full), and ReadMode.value_schema only selects which fixed ValueTenant set materializes (crates/lance-graph-contract/src/class_view.rs:1133, crates/lance-graph-contract/src/canonical_node.rs:1198). As written, an OGAR mint cannot encode different SpoFacet/PearlRung/sibling readings without either adding a new projection axis/API or hardcoding additional presets, so following this plan would leave the intended per-app facet readings unrepresentable.

Useful? React with 👍 / 👎.

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