Implement RFC-026 private MemWAL B1 core#371
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
StreamFoldAckUnknown__manifestCASWhy
Phase A established bounded MemWAL enrollment and lifecycle authority but intentionally shipped no row path. This slice implements and proves the smallest data-bearing B1 profile without waiting for a broader upstream receipt/seal API and without exposing a product contract.
Acknowledged rows remain invisible until the exact fold publishes through the graph manifest. Lance continues to own the WAL, shard fencing, replay, generation storage, and scan primitives; OmniGraph adds only the graph authority, recovery envelope, and visibility boundary around them.
Support boundary
This remains private and deliberately narrow:
mainonlyPublic activation remains RFC-026 B2 and is still gated on attribution, reclamation, correction, retry sequencing, and persistent operator controls.
Validation
cargo test --workspace --lockedcargo test -p omnigraph-engine --features failpoints --test memwal_stream --locked— 24 passedcargo test -p omnigraph-engine --features failpoints --test failpoints --locked— 141 passed, 1 helper ignoredcargo test -p omnigraph-engine --features failpoints --test forbidden_apis --locked— 16 passedcargo test -p omnigraph-engine --features failpoints --test memwal_stream_cost --locked— 7 passed, 1 helper ignoredcargo test -p omnigraph-server --features awsscripts/check-agents-md.shrustfmt --checkandgit diff --checkGreptile Summary
This PR adds the private RFC-026 B1 MemWAL core. The main changes are:
Confidence Score: 5/5
This looks safe to merge.
AckUnknownwhile ownership remains detached.Important Files Changed
Sequence Diagram
%%{init: {'theme': 'neutral'}}%% sequenceDiagram participant Caller participant Registry as Worker Registry participant Writer as Lance MemWAL participant Recovery as Recovery v11 participant Table as Lance Table participant Manifest as __manifest Caller->>Registry: Reserve charge and queue input Registry->>Writer: Claim or reuse writer Registry->>Writer: Put one bounded batch Writer-->>Registry: Durability watcher result Registry-->>Caller: Durable ack or AckUnknown Caller->>Registry: Request fold Registry->>Registry: Acquire exclusive admission Registry->>Writer: Seal and prove generation cut Registry->>Writer: Abort and retire writer Registry->>Recovery: Arm exact StreamFold sidecar Recovery->>Table: Commit exact-ID update Recovery->>Manifest: Publish table, lifecycle, epoch, and lineage Manifest-->>Caller: Fold visible%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% sequenceDiagram participant Caller participant Registry as Worker Registry participant Writer as Lance MemWAL participant Recovery as Recovery v11 participant Table as Lance Table participant Manifest as __manifest Caller->>Registry: Reserve charge and queue input Registry->>Writer: Claim or reuse writer Registry->>Writer: Put one bounded batch Writer-->>Registry: Durability watcher result Registry-->>Caller: Durable ack or AckUnknown Caller->>Registry: Request fold Registry->>Registry: Acquire exclusive admission Registry->>Writer: Seal and prove generation cut Registry->>Writer: Abort and retire writer Registry->>Recovery: Arm exact StreamFold sidecar Recovery->>Table: Commit exact-ID update Recovery->>Manifest: Publish table, lifecycle, epoch, and lineage Manifest-->>Caller: Fold visibleReviews (1): Last reviewed commit: "Implement RFC-026 private MemWAL B1 core" | Re-trigger Greptile
Context used: