[GH-ISSUE #170] Reconstruction workflows ignore process interaction and shim dimensions #115

New issue

Closed

opened 2026-10-15 18:21:16 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:21:16 +00:00

Owner

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

Problem

The process comparison schema now includes interaction and shim dimensions, but reconstruction tooling still validates and exposes only the legacy five dimensions (terminal, exit, filesystem, protocol, process).

Evidence

src/domain/reconstructionVerification.ts:322-327 defines validateProcessStatus over:
terminal, exit, filesystem, protocol, process only.
src/domain/reconstructionVerification.ts:271-316 calls that validator before computing behavioral claim outcomes.
src/domain/staticRuntimeCorrelation.ts:26-32 restricts runtime correlation dimensions to the same five dimensions.
src/domain/reconstructionVerificationSchemas.ts:20-27 restricts behavioral reconstruction claims to the same five dimensions.

Impact

A process comparison with only interaction (or shim) changed can make verifyReconstruction reject the comparison as internally inconsistent (Process comparison status contradicts its dimensions), even when status is correctly computed from all dimensions.
Consumers cannot create reconstruction claims or static/runtime correlations that target interaction or shim process-comparison dimensions, so these new behaviors cannot be reasoned about downstream.

Repro

Construct a process-comparison result where interaction is "changed" and all other dimensions (terminal, exit, filesystem, protocol, process, status) are "unchanged".
Pass it into verifyReconstruction via rea-process comparison Evidence.
Observe TypeError: Process comparison status contradicts its dimensions from validateProcessStatus.

Also, a reconstruction spec with behavioral dimension "interaction" is rejected by schema validation, as is a static/runtime correlation runtime dimension "interaction".

Proposed fix

Update reconstruction validation and correlation schemas to include "interaction" and "shim" as valid process dimensions.
Ensure validateProcessStatus uses the same seven dimensions used by processCaptureComparisonSchema and compareProcessCaptures status semantics.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/170 ## Problem The process comparison schema now includes `interaction` and `shim` dimensions, but reconstruction tooling still validates and exposes only the legacy five dimensions (`terminal`, `exit`, `filesystem`, `protocol`, `process`). ## Evidence - `src/domain/reconstructionVerification.ts:322-327` defines `validateProcessStatus` over: `terminal`, `exit`, `filesystem`, `protocol`, `process` only. - `src/domain/reconstructionVerification.ts:271-316` calls that validator before computing behavioral claim outcomes. - `src/domain/staticRuntimeCorrelation.ts:26-32` restricts runtime correlation dimensions to the same five dimensions. - `src/domain/reconstructionVerificationSchemas.ts:20-27` restricts behavioral reconstruction claims to the same five dimensions. ## Impact - A process comparison with only `interaction` (or `shim`) changed can make `verifyReconstruction` reject the comparison as internally inconsistent (`Process comparison status contradicts its dimensions`), even when `status` is correctly computed from all dimensions. - Consumers cannot create reconstruction claims or static/runtime correlations that target `interaction` or `shim` process-comparison dimensions, so these new behaviors cannot be reasoned about downstream. ## Repro 1. Construct a process-comparison result where `interaction` is `"changed"` and all other dimensions (`terminal`, `exit`, `filesystem`, `protocol`, `process`, `status`) are `"unchanged"`. 2. Pass it into `verifyReconstruction` via `rea-process` comparison Evidence. 3. Observe `TypeError: Process comparison status contradicts its dimensions` from `validateProcessStatus`. Also, a reconstruction spec with behavioral dimension `"interaction"` is rejected by schema validation, as is a static/runtime correlation runtime dimension `"interaction"`. ## Proposed fix - Update reconstruction validation and correlation schemas to include `"interaction"` and `"shim"` as valid process dimensions. - Ensure `validateProcessStatus` uses the same seven dimensions used by `processCaptureComparisonSchema` and `compareProcessCaptures` status semantics.

bsakaguchi

2026-10-15 18:21:16 +00:00