Repository navigation
rfc: narrow graph access to client contracts - #1149
Open
aaltshuler wants to merge 1 commit into
Open
aaltshuler wants to merge 1 commit into
aaltshuler wants to merge 1 commit into
Conversation
This was referenced Oct 24, 2026
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.
Amends the accepted graph access RFC from #1017. It bundled client access and error contracts with a separate engine concurrency redesign, making client completion depend on new manifest control facts, a storage stamp and cross-process qualification.
Retitle it “Graph access and client contracts” and remove the engine design, its rollout and evidence gates, and the dependent
disposition.checkprotocol. Preserve the current writer-process restrictions and cluster admission. Update the registry, HTTP-conventions title reference and storage-outcomes dependency statements; keep the canonical filename and record the maintainer's October 24 scope decision.Documentation validation passes across all 400 Markdown files, the agent-guide consistency check passes, and spelling and whitespace checks pass. An independent scope review found no remaining normative engine-redesign promises. No runtime code or storage contract changes.
For review: the existing client scope remains accepted and in progress. Historical engine decisions remain in the decision log, explicitly superseded; a future engine redesign needs its own RFC. Storage-outcomes settlement remains owned by its unchanged §5. The open #951 branch still references the withdrawn
disposition.checkproposal and will need to reconcile that dependency before landing; it is not part of this amendment.