Repository navigation
docs: update plan with Graph deployment status - #45
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
oneshot | 510421b | Sep 08 2026, 11:24 PM |
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.
Summary
Update the canonical delivery plan with the current open-PR progress and verified The Graph deployment status. Clarify that the Subgraph is published with an immutable deployment but is not yet allocated/indexed on the decentralized network. Align
plan_missing_parts.mdwith the remaining allocation, MCP/model, and live-proof gaps.Scope and acceptance criteria
plan.mdrecords open PRs docs: correct Gate P4 verification status #42, fix(settlement): close lane B review follow-ups #43, and fix: require recovery lookup config #44 as pending human integration.plan.mdrecords the published Subgraph, deployment CID, public IDs, Explorer status, and Studio-vs-decentralized query distinction.plan_missing_parts.mdseparates deployment identification from remaining allocation/indexing and live recovery evidence.Product and security invariants
Invariant notes:
Documentation-only change. One intent / at-most-one settlement and UNKNOWN safety semantics are preserved. The Graph remains observational and non-authoritative; production recovery remains
FALLBACK_DIRECT_RECOVERYuntil allocation and live MCP/model/Arc evidence are complete.Validation
Commands and results:
Independent review evidence
Gate A — exact candidate tree before push
Base commit SHA:
48391e4968675764632627716e580988a271c13dCandidate tree SHA:
7cca5327ec867a85f373d353d71e44a0fc3de9deCandidate commit SHA:
510421b20e9d8f971b95065ee25fcc86d46ccf25Reviewer tool:
free-pi-cliReviewer model:
glm-5.3-flashVerdict:
VERDICT: PASSFindings or residual risks: no blocking findings; Explorer and PR status claims are external-state snapshots.
The reviewed tree equals the committed tree.
Gate B — exact remote PR head
Pull request URL/number: to be filled after creation
Remote head commit SHA: to be filled after creation
Remote head tree SHA: to be filled after creation
Reviewer tool:
free-pi-cliReviewer model: pending
Verdict: pending
Findings or residual risks: pending exact-head review and required CI.
Gate B reviewed the current remote head and matches Gate A's approved tree, or a fresh Gate A was run for the changed tree.
Agent policy / repository-policyand all applicable CI checks pass.Risk and rollback
510421b20e9d8f971b95065ee25fcc86d46ccf25; no runtime rollback is required.Human merge