[GH-ISSUE #73] Create an evidence-linked residual-unknowns registry #60

New issue

Closed

opened 2026-10-15 18:20:37 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:20:37 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/73

Problem

Unsupported branches, missing authority, contradictions, and recommended probes are easily lost and inference can be mistaken for verified behavior.

Outcome

Add a durable registry with create/update/query and evidence-qualified resolution.

Contract

Records contain stable ID, bounded question, open/investigating/blocked/contradicted/resolved status, severity/domain, supporting and contradicting evidence IDs, required authority/environment, recommended probes, relationships, and resolution evidence/rationale.

Provide list_unknowns, record_unknown, update_unknown, and verify_unknown_resolution. Mutations require approval and create evidence.

Correctness

Resolution requires qualifying evidence or explicit withdrawn/out-of-scope disposition. Inference cannot satisfy observed authority. Deleted evidence invalidates dependent resolution. Contradictions remain visible. Imports validate references and cycles.

Acceptance criteria

Workflows create unknowns from truncation/unavailability/contradictions; queries filter meaningfully; resolution checks authority; bundles preserve relationships; stale/missing evidence cannot remain resolved; ordering/IDs are deterministic.

Dependencies

Parent #18. Requires Evidence v2, bundles, and typed capabilities.

Verification

Lifecycle, automatic creation, authority, contradictions, evidence invalidation, cycles/broken refs, round trips, tampering, concurrent updates, and merge determinism.

Non-goals

General project management, automatic truth determination, or replacing GitHub issues.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/73 ## Problem Unsupported branches, missing authority, contradictions, and recommended probes are easily lost and inference can be mistaken for verified behavior. ## Outcome Add a durable registry with create/update/query and evidence-qualified resolution. ## Contract Records contain stable ID, bounded question, open/investigating/blocked/contradicted/resolved status, severity/domain, supporting and contradicting evidence IDs, required authority/environment, recommended probes, relationships, and resolution evidence/rationale. Provide `list_unknowns`, `record_unknown`, `update_unknown`, and `verify_unknown_resolution`. Mutations require approval and create evidence. ## Correctness Resolution requires qualifying evidence or explicit withdrawn/out-of-scope disposition. Inference cannot satisfy observed authority. Deleted evidence invalidates dependent resolution. Contradictions remain visible. Imports validate references and cycles. ## Acceptance criteria Workflows create unknowns from truncation/unavailability/contradictions; queries filter meaningfully; resolution checks authority; bundles preserve relationships; stale/missing evidence cannot remain resolved; ordering/IDs are deterministic. ## Dependencies Parent #18. Requires Evidence v2, bundles, and typed capabilities. ## Verification Lifecycle, automatic creation, authority, contradictions, evidence invalidation, cycles/broken refs, round trips, tampering, concurrent updates, and merge determinism. ## Non-goals General project management, automatic truth determination, or replacing GitHub issues.

bsakaguchi

2026-10-15 18:20:37 +00:00

closed this issue
added the
area: server

P1: high

area: domain

roadmap

enhancement
labels

bsakaguchi commented

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

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Implemented on main. The session Evidence ledger now owns deterministic residual-unknown identities and revision history; the canonical list_unknowns, record_unknown, update_unknown, and verify_unknown_resolution tools expose schema-parsed lifecycle operations with CAS revision checks. Domain and bundle validation enforce evidence references, contradictions, authority-qualified verified resolution, cycles/broken references, deterministic ordering, and atomic import. Direct, enhanced, comparison, process, managed, application, and investigation workflows can record approved residuals. Lifecycle, concurrency, authority, tampering, resource, bundle, and MCP integration tests cover the acceptance criteria.

@morluto commented on GitHub (Jul 17, 2026): Implemented on main. The session Evidence ledger now owns deterministic residual-unknown identities and revision history; the canonical `list_unknowns`, `record_unknown`, `update_unknown`, and `verify_unknown_resolution` tools expose schema-parsed lifecycle operations with CAS revision checks. Domain and bundle validation enforce evidence references, contradictions, authority-qualified verified resolution, cycles/broken references, deterministic ordering, and atomic import. Direct, enhanced, comparison, process, managed, application, and investigation workflows can record approved residuals. Lifecycle, concurrency, authority, tampering, resource, bundle, and MCP integration tests cover the acceptance criteria.

bsakaguchi referenced this issue

2026-10-15 18:22:08 +00:00

[GH-ISSUE #334] Integrate finite-state replay machine into process capture #181

bsakaguchi referenced this issue

2026-10-15 18:22:08 +00:00

[GH-ISSUE #335] Add CLI/MCP command for finite-state replay machines #182

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:28:41 +00:00