[GH-ISSUE #37] Add differential analysis and reconstruction verification workflows

bsakaguchi commented

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

Owner

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

Goal

Turn low-level evidence into repeatable cross-version and reconstruction comparisons.

Workflows

compare_artifacts
compare_bundles
compare_functions
find_changed_behavior
build_call_path
correlate_static_and_runtime
verify_reconstruction
create_residual_unknowns_ledger

Requirements

Normalize provider-specific identities without hiding raw evidence.
Separate observed changes, derived relationships, hypotheses, contradictions, and unresolved branches.
Compare symbols, imports, exports, strings, metadata, CFG shape, call relationships, resources, protocols, and runtime observations where available.
Support multiple versions and multiple providers in one investigation.
Cite stable evidence IDs for every conclusion.
Bound expensive comparisons and expose progress, pagination, and exported artifacts.

Acceptance criteria

Two fixture versions yield a deterministic classified change report.
A reconstruction can be checked against a behavioral and structural specification.
Missing evidence is reported as unknown, never as equivalence.
The residual-unknowns ledger recommends concrete next probes.

Roadmap expansion

Child work

Comparisons normalize only declared volatile fields and classify unchanged, added, removed, changed, truncated, and unknown. Every conclusion cites both evidence sets. Missing, unauthorized, stale, or truncated evidence never implies equivalence.

Reconstruction workspace and coverage-closure workstream

Differential tools need a durable graph that proves which authoritative surfaces and finite claims are actually owned and verified by a reconstruction. Add a reconstruction workspace rather than relying on aggregate test counts or narrative completion claims.

Workspace responsibilities

Import deterministic surface inventories from artifact, semantic, protocol, process, browser, Electron, and native evidence.
Map each required surface to one primary reconstructed owner or an explicit allowed disposition.
Register finite claims, replacement boundaries, verifier contracts, required dimensions, freshness, repetitions, and normalization.
Ingest canonical Evidence v2 and verifier results.
Detect missing/duplicate/stale owners, authority routing, undistributed code, missing verifiers, weak authority, skips, truncation, contradictions, and unresolved unknowns.
Compute fail-closed replacement readiness and recommend the highest-impact next probe.

Correctness

Ownership does not prove parity. Component tests cannot cover unnamed process/package/UI/native claims. Changed artifacts, schemas, owner paths, normalization, verifier contracts, or evidence invalidate dependent closure. Missing and stale facts remain unknown. Concurrent agents update through monotonic CAS revisions.

Completion fixture

Use an intentionally incomplete reconstructed CLI whose component suite is green but one command process, persistence effect, and packaged entrypoint remain unowned. The workspace must report partial. Add each missing proof independently and advance only the claims it covers. A candidate that imports the authority must never become replacement-ready.

Track the full schema and workflow in #268.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/37 ## Goal Turn low-level evidence into repeatable cross-version and reconstruction comparisons. ## Workflows - compare_artifacts - compare_bundles - compare_functions - find_changed_behavior - build_call_path - correlate_static_and_runtime - verify_reconstruction - create_residual_unknowns_ledger ## Requirements - Normalize provider-specific identities without hiding raw evidence. - Separate observed changes, derived relationships, hypotheses, contradictions, and unresolved branches. - Compare symbols, imports, exports, strings, metadata, CFG shape, call relationships, resources, protocols, and runtime observations where available. - Support multiple versions and multiple providers in one investigation. - Cite stable evidence IDs for every conclusion. - Bound expensive comparisons and expose progress, pagination, and exported artifacts. ## Acceptance criteria - Two fixture versions yield a deterministic classified change report. - A reconstruction can be checked against a behavioral and structural specification. - Missing evidence is reported as unknown, never as equivalence. - The residual-unknowns ledger recommends concrete next probes. ## Roadmap expansion ### Child work - [x] #61 - [x] #65 - [x] #67 - [x] #73 Comparisons normalize only declared volatile fields and classify unchanged, added, removed, changed, truncated, and unknown. Every conclusion cites both evidence sets. Missing, unauthorized, stale, or truncated evidence never implies equivalence. ## Reconstruction workspace and coverage-closure workstream Differential tools need a durable graph that proves which authoritative surfaces and finite claims are actually owned and verified by a reconstruction. Add a reconstruction workspace rather than relying on aggregate test counts or narrative completion claims. ### Workspace responsibilities - Import deterministic surface inventories from artifact, semantic, protocol, process, browser, Electron, and native evidence. - Map each required surface to one primary reconstructed owner or an explicit allowed disposition. - Register finite claims, replacement boundaries, verifier contracts, required dimensions, freshness, repetitions, and normalization. - Ingest canonical Evidence v2 and verifier results. - Detect missing/duplicate/stale owners, authority routing, undistributed code, missing verifiers, weak authority, skips, truncation, contradictions, and unresolved unknowns. - Compute fail-closed replacement readiness and recommend the highest-impact next probe. ### Correctness Ownership does not prove parity. Component tests cannot cover unnamed process/package/UI/native claims. Changed artifacts, schemas, owner paths, normalization, verifier contracts, or evidence invalidate dependent closure. Missing and stale facts remain unknown. Concurrent agents update through monotonic CAS revisions. ### Completion fixture Use an intentionally incomplete reconstructed CLI whose component suite is green but one command process, persistence effect, and packaged entrypoint remain unowned. The workspace must report partial. Add each missing proof independently and advance only the claims it covers. A candidate that imports the authority must never become replacement-ready. Track the full schema and workflow in #268.

bsakaguchi

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

closed this issue
added the
area: server

P1: high

roadmap

enhancement

area: tests
labels

bsakaguchi commented

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

Author

Owner

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

Current main delivers artifact, function, bundle, process, and web comparison; changed-behavior and call-path workflows; static/runtime correlation; residual unknowns; and reconstruction verification/coverage workspaces. Remaining scope is authoritative multi-provider/version fixture closure and the focused gaps in #61, #65, and #67.

@morluto commented on GitHub (Jul 17, 2026): Current main delivers artifact, function, bundle, process, and web comparison; changed-behavior and call-path workflows; static/runtime correlation; residual unknowns; and reconstruction verification/coverage workspaces. Remaining scope is authoritative multi-provider/version fixture closure and the focused gaps in #61, #65, and #67.

bsakaguchi commented

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

Author

Owner

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

Split into focused child issues:

#360
#361

These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

@morluto commented on GitHub (Jul 20, 2026): Split into focused child issues: - [ ] #360 - [ ] #361 These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

bsakaguchi referenced this issue

2026-10-15 18:23:04 +00:00

[GH-ISSUE #481] [Feature] Add a read-only Ghidra provider for macOS #257

bsakaguchi referenced this issue

2026-10-15 18:23:04 +00:00

[GH-ISSUE #482] [Feature] Trace native state and value dependencies across functions #258

bsakaguchi referenced this issue

2026-10-15 18:24:00 +00:00

[GH-ISSUE #747] [Feature] Integrate IDA Pro MCP as an attached and headless analysis provider #332

bsakaguchi referenced this issue

2026-10-15 18:28:06 +00:00

[GH-ISSUE #2300] [Feature] Show one function's pseudocode from several decompiler providers in one call #764