RFC 0066: Server lifecycle and online deployment - #697
Draft
aaltshuler wants to merge 2 commits into
Draft
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
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.
What & why
Schema and configuration changes currently require reconstructing server state, while interrupted requests and failed writes can leave graphs unavailable. RFC 0066 proposes online activation in the running server, server-owned operation lifetimes, and explicit recovery and resource boundaries.
The proposal defines coherent schema/query activation without resetting graphs, exact publication outcomes, per-graph availability, bounded admission and change-feed progress, and an incremental rollout with evidence gates.
Backing issue / RFC
Related: #466, #694, #601, #602, #513, #494.
Checklist
docs/dev/invariants.md; graph publication, recovery ownership and authorization remain explicit requirements.Local verification
python3 scripts/check-docs.py— passed; 139 Markdown files checked.bash scripts/check-agents-md.sh— passed; 47 links and 45 docs checked.typos docs/rfcs/0066-server-lifecycle-and-online-deployment.md docs/rfcs/README.md— passed.git diff --checkandgit diff --check origin/main...HEAD— passed.Notes for reviewers
The RFC remains
draft/not-started. Review the operation-settlement boundary, deployment publication/finalization/activation ordering, and the startup reconciliation proof required before online deployment can ship.Issue #694 requires engine failure finalization in addition to surviving client disconnects. Issue #466 requires typed retry decisions for the complete command. The RFC also records its relationship to RFC 0065's separately gated isolated merge-publication design. Durable data-operation submission and result lookup have their own acceptance gate.