[GH-ISSUE #3005] MCP-reachable path to ledger 'verified' rung + update_unknown revision digest #1049

New issue

Open

opened 2026-10-15 18:30:39 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:30:39 +00:00

Owner

Originally created by @shikyo13 on GitHub (Oct 13, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3005

Context

Reforge (a reconstruction-first RE platform) drives rea-agents 6.4.0 as a pinned external MCP provider and has built an L4 behavioral-verification lane on top of capture_process_scenario -> get_evidence_bundle -> build_reconstruction_obligation_ledger -> verify_reconstruction.

What works today (all over MCP, no session API)

Obligations reach ledger status implemented with fail-closed diagnostics (weak-fixture-authority, weak-verifier-authority).
record_unknown / verify_unknown_resolution work and correctly refuse (valid:false) until resolved.

What is unreachable over MCP in 6.4.0

verified ledger rung needs a shipped-artifact-authority fixture authenticated via the in-process boundProofEvidence session helper; MCP-produced evidence tops out at controlled-replay/analyst-inference.
update_unknown accepts the full typed revision (validation passes) but then rejects with evidence_integrity_mismatch ("refresh and retry", retryable:false) regardless of ordering, including re-reading the head via list_unknowns between calls — it looks like a revision-digest/chaining parameter that record_unknown returns (revision_digest) is not present in the update schema.

Request

Expose (a) an MCP tool to register/authenticate a fixture-evidence with shipped-artifact authority (or let capture/exported-bundle re-import raise authority), and (b) document/extend update_unknown with the digest the mutation expects.

Happy to co-test against our provider integration; reproducible via plain MCP calls on 6.4.0.

Originally created by @shikyo13 on GitHub (Oct 13, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3005 ## Context Reforge (a reconstruction-first RE platform) drives `rea-agents` 6.4.0 as a pinned external MCP provider and has built an L4 behavioral-verification lane on top of `capture_process_scenario` -> `get_evidence_bundle` -> `build_reconstruction_obligation_ledger` -> `verify_reconstruction`. ## What works today (all over MCP, no session API) - Obligations reach ledger status `implemented` with fail-closed diagnostics (`weak-fixture-authority`, `weak-verifier-authority`). - `record_unknown` / `verify_unknown_resolution` work and correctly refuse (`valid:false`) until resolved. ## What is unreachable over MCP in 6.4.0 1. **`verified` ledger rung** needs a `shipped-artifact`-authority fixture authenticated via the in-process `boundProofEvidence` session helper; MCP-produced evidence tops out at `controlled-replay`/`analyst-inference`. 2. **`update_unknown`** accepts the full typed revision (validation passes) but then rejects with `evidence_integrity_mismatch` ("refresh and retry", `retryable:false`) regardless of ordering, including re-reading the head via `list_unknowns` between calls — it looks like a revision-digest/chaining parameter that `record_unknown` returns (`revision_digest`) is not present in the update schema. ## Request Expose (a) an MCP tool to register/authenticate a fixture-evidence with `shipped-artifact` authority (or let capture/exported-bundle re-import raise authority), and (b) document/extend `update_unknown` with the digest the mutation expects. Happy to co-test against our provider integration; reproducible via plain MCP calls on 6.4.0.

bsakaguchi added the

area: mcp

enhancement

labels

2026-10-15 18:30:39 +00:00

bsakaguchi referenced this issue

2026-10-17 21:08:09 +00:00

[PR #1049] [MERGED] fix(domain): preserve prototype-named JSON members through Evidence boundaries #2607

bsakaguchi added

enhancement

and removed

enhancement