Skip to content

rfc: narrow graph access to client contracts - #1149

Open
aaltshuler wants to merge 1 commit into
ModernRelay:mainfrom
aaltshuler:codex/rfc-1017-client-scope
Open

aaltshuler wants to merge 1 commit into
ModernRelay:mainfrom
aaltshuler:codex/rfc-1017-client-scope

Conversation

@aaltshuler

Copy link
Copy Markdown
Contributor

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.check protocol. 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.check proposal and will need to reconcile that dependency before landing; it is not part of this amendment.

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