Skip to content

feat(native): stage persistent data adapter behind continuity gate - #239

Closed
roodboi wants to merge 3 commits into
nextfrom
feat/native-persistent-data-activation
Closed

roodboi wants to merge 3 commits into
nextfrom
feat/native-persistent-data-activation

Conversation

@roodboi

@roodboi roodboi commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Ordinary native persistent startup now refuses before provider connection or data effects until a root continuity witness is qualified. This stages the real retained-guest adapter and graph receipt v4 without enabling it: stable data ownership stays independent of compute generations, enrollment preserves pending before the original create, and compute cleanup never deletes persistent data.

The adapter holds the common guest mutation lease across absence, one create request, captured identity and owner publication. Docker's idempotent create endpoint alone supplies no exclusive ownership. Receipt v2 continues to reject even empty storage keys; receipt v3 remains a separate source-bearing family. Dead-publication recovery refuses receipt v4. Request budgets take the minimum of admission and explicit deadlines.

This draft is stacked on the inactive codec/enrollment foundations in #233 and #235, preserved at their original heads. The added metadata-aliasing counterexample shows why name, labels, birth and directory metadata cannot prove physical continuity after replacement. The root witness, provider integration and live SQL retention remain required; the source-pinned Bun/SQLite fixture currently qualifies lowering and fresh initializer scheduling only. It does not qualify PostgreSQL parity or full NC05 support.

Validation at ed249d0: independent source review; 17 persistence controls, 26 runtime controls (25 unchanged passes plus the corrected no-publication control), one request-deadline control and 25 lowerer/scheduler controls; default and all-feature all-target Clippy, Rust formatting; 124 protocol/model-registry tests qualified through the original round and affected reruns; strict CLI typecheck, changed-file lint, privacy, diff and owning commitlint. The separate TLC metadata-aliasing negative matched its exact witness. The historical 38-state enrollment result remains separate. Initial test/compile/lint failures are preserved. No provider, engine, SQL, helper execution or package build was performed. Exact-head hosted CI and current-base integration remain required.

Release intent: inactive native persistence groundwork; existing image-only defaults remain supported and persistent startup stays refused.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@blacksmith-sh

blacksmith-sh Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Found 1 test failure on Blacksmith runners:

Failure

Test View Logs
native-compose-adoption-job-worktrees (77.1s) — Completed-job worktree acceptance refus
ed; values omitted./
native-compose-adoption-job-worktrees (77.1s) — Completed-job worktree acceptance refus
ed; values omitted.
View Logs

Fix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@roodboi

roodboi commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #245, merged into next as d19cdd3. This exact branch head is an ancestor of the independently reviewed #245 head e1e6da9; its inactive persistent-storage groundwork is included in that cumulative change. Live guest delivery, retirement and ordinary persistent SQL remain open under NC05.

@roodboi roodboi closed this Oct 9, 2026
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.

1 participant