Skip to content

feat(v0.13): State Engine V2 durability and migration - #92

Draft
eybersjp wants to merge 32 commits into
mainfrom
feature/v0.13-state-engine-v2
Draft

eybersjp wants to merge 32 commits into
mainfrom
feature/v0.13-state-engine-v2

Conversation

@eybersjp

Copy link
Copy Markdown
Owner

DKF130-T04 — State Engine V2

First v0.13 priority, rebased from the released v0.12.1 line.

Scope

  • canonical append-only State Engine V2 ledger
  • rebuildable snapshot and acceleration index
  • legacy state migration/cutover
  • Autopilot and orchestration persistence adapters
  • journal-less torn-tail recovery
  • persistent hash-chained legacy-restore transaction log
  • full Windows restore path on positively identified supported storage
  • Windows native durability helper with literal process arguments
  • v0.13 high-assurance Development Contract
  • dedicated v0.13 regression lane

Preserved

All released v0.12.1 T01–T03/T05–T10 semantics remain in place. Historical v0.12 State Engine branches are source material only.

Explicitly not claimed yet

This PR is not accepted merely because CI passes. T04 remains risk level 3 and requires independent code, architecture, and security review plus security-control evidence bound to the exact reviewed source.

Deferred/out of scope

  • application-specific state semantics
  • distributed locking
  • same-account hostile writer hardening tracked separately
  • v0.13 release publication

This branch has not been deployed

No deployments
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