feat(protection): add lifecycle foundation - #22
Merged
vishr merged 6 commits intoAug 8, 2026
Conversation
Establish shared schema, capability, fencing, journaling, active-volume, and scheduled-runner contracts before adding the first PostgreSQL backend. Unqualified drivers remain Run and mutations fail closed.
Project external credentials through least-privilege release files, bind protected service rendering to observed lifecycle state, and make recurring operations occurrence-specific. Fail closed on foreign units, unavailable images, stale timing, and credential cleanup errors.
feat(backup): add S3 target adapter
vishr
marked this pull request as ready for review
August 8, 2026 01:45
This was referenced Aug 17, 2026
vishr
added a commit
that referenced
this pull request
Aug 18, 2026
feat(protection): add lifecycle foundation
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
1 participant
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.
Stacked on #21.
Implements OpenSpec sections 1-4 as a safety-focused foundation:
All managed runtimes remain single-node. There is no replication target, operation, evidence type, schedule, or MinIO second-deployment path.
No database backend is graduated or advertised as Managed in this PR. Database backup and restore engines follow as separate slices.
Validation: