Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
69 changes: 69 additions & 0 deletions .agent/context/20260908T201500Z-plan-missing-parts.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
# Session Context: plan-missing-parts

## Date/time

- UTC: 2026-09-08T20:15:00Z

## User goal

Audit the approved plan and publish a concise report of unimplemented work,
dependencies, blockers, and immediate priorities.

## Original prompt/request

Switch to `docs/missing-plan-implementation`, audit `plan.md`, and create
`plan_missing_parts.md` with missing work grouped by Not Started and In
Progress, dependencies/blockers, and immediate priorities.

## Assumptions

- A packet with offline implementation and tests is not called missing solely
because a later live project gate remains open.
- Checked-in evidence and explicit fail-closed status documents are the source
of truth for delivery state.

## Plan

1. Compare plan gates and deliverables to current code, tests, and evidence.
2. Create the report without modifying `plan.md` or product behavior.
3. Run Markdown lint and commit the focused documentation change.

## Key decisions

- Classify live The Graph recovery, P4/P5/P6 completion as In Progress because
their offline foundations exist but their required integrated evidence does not.
- Classify Arc Mainnet activation and submission media/text as Not Started.

## Files/components touched

- `plan_missing_parts.md`: delivery-gap audit.

## Commands/checks

- Repository and plan/evidence audit in progress.

## External-doc findings

- None; the report relies on repository-owned plan and evidence.

## Unresolved questions

- Exact owner and timeline for Graph deployment, MCP/Gateway access, and model
configuration require human coordination.

## Git and PR state

- Branch: `docs/missing-plan-implementation`
- Base: `develop` at `0291b684e187557e13c47869359cbab445ee4148`
- Commit: uncommitted
- PR: not created
- CI: not run

## Review gates

- Gate A: NOT RUN
- Gate B: NOT RUN

## Handoff/next steps

1. Markdown-lint and review the report, then commit the documentation-only audit.
106 changes: 106 additions & 0 deletions plan_missing_parts.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,106 @@
# Missing Plan Implementation

Audit basis: `plan.md`, current source, tests, and checked-in evidence on the
`docs/missing-plan-implementation` branch. This is a delivery-gap report, not
a change to the approved product plan. Completed offline milestones are not
listed as missing merely because their final project gate is still open.

## Not Started

### Arc Mainnet activation

- Pin official Arc Mainnet chain, RPC, explorer, and USDC identities when Arc
publishes them.
- Enable and probe the Mainnet profile only after explicit human authorization.
- Run the required review and deployment procedure; no real-value transaction
is authorized by this report.

This is deliberately absent today: `docs/MAINNET_READINESS.md` reports
`DEPLOYMENT-READY`, and the code is designed to fail closed until those inputs
exist.

### Sponsor-submission deliverables

- Record the required two-to-four-minute demo video/presentation.
- Prepare submission text that explicitly names the claimed Arc tracks and
links the public repository and evidence.
- Do not include a The Graph qualification claim unless its live MCP and model
evidence is complete.

The repository contains demo runbooks and evidence templates, but not a
recorded submission artifact.

## In Progress

### Live The Graph hashless recovery

The boundary, schemas, simulator, deterministic safety core, and fail-closed
fallback exist. The live production path is intentionally unavailable.

Remaining work:

- Publish or identify a canonical immutable OneShot/Arc Subgraph deployment
with an active Indexer allocation.
- Configure a live Subgraph MCP transport and query the pinned deployment for
a lost-hash recovery case.
- Configure the structured-output recovery-model adapter and capture its
recommendation, evidence references, and deterministic-core disposition.
- Verify every returned candidate with Arc receipt and exact Transfer evidence,
while proving zero new settlement submissions.
- Capture the sanitized trace, including `_meta` freshness/health, MCP tool and
query identity, candidate count, model action, and core decision.

Until then, automatic hashless recovery remains unavailable and The Graph is
`NOT VERIFIED`; this blocks the live lost-hash requirement in Gate P4 and the
Graph portion of C06/P6.

### Gate P4 integrated proof

Most composition pieces and the live Privy/Arc allowed, denied, and
lost-response drills are present. Gate P4 remains incomplete because its live
lost-hash The Graph MCP/model flow has not been proven. The final integrated
matrix should also record every applicable `.agent/TEST_MATRIX.md` scenario
with durable state and external-settlement count.

### Gate P5 frontend acceptance

The intent/status UI and a synthetic recovery viewer are implemented, but the
repository status still marks live API wiring as pending. Complete the frozen
API composition and browser-level acceptance coverage for:

- create, replay, and conflicting intent payloads;
- policy denial, committed settlement, and `UNKNOWN` recovery states;
- Graph discovery, lag/error, and multiple-candidate states; and
- accessibility, responsive layout, no-secret, and no-force-pay checks.

The plan calls for Playwright browser flows; the current workspace evidence is
primarily Vitest component/client tests and fixture-backed recovery UI tests.

### Gate P6 release candidate

Release runbooks, safe-disable behavior, a disabled Mainnet profile, and
Privy/Arc testnet evidence exist. P6 remains open until P4/P5 complete, the
repeatable end-to-end demo is captured, selected sponsor claims are supported,
and the exact release candidate completes CI plus Gate A and Gate B review.

## Potential Dependencies and Blockers

| Item | Dependency or blocker | Safe response while blocked |
| --- | --- | --- |
| Live Graph recovery | Immutable deployment, Indexer allocation, Gateway/MCP access, and model credentials supplied by a human | Keep `FALLBACK_DIRECT_RECOVERY`; retain `UNKNOWN`; do not retry payment. |
| P4 live lost-hash proof | The live Graph recovery trace and Arc verification evidence | Do not claim Gate P4 or Graph qualification. |
| P5 live UI acceptance | Reachable configured API, safe test data, and browser-test environment | Continue fixture/mock coverage; do not add a payment bypass. |
| P6 release | P4/P5 completion, CI, exact-tree reviews, and human demo/submission decisions | Keep release candidate and sponsor claims incomplete. |
| Arc Mainnet | Official published network values and explicit human authorization | Preserve the disabled, fail-closed profile. |

## Immediate Priorities

1. Close the live The Graph MCP/model recovery evidence gap. It is the only
sponsor-critical product dependency still intentionally disabled and blocks
final P4/P6 qualification.
2. Run the complete integrated P4 matrix against the real composed services,
recording durable outcomes and settlement counts for every required case.
3. Wire the operator UI to the configured API and add the P5 browser acceptance
suite, especially `UNKNOWN` and Graph-degraded recovery views.
4. After P4/P5 pass, capture the demo/submission artifacts and perform the P6
release-candidate CI and review sequence.
Loading