[GH-ISSUE #158] Process comparison marks interaction as unknown via terminal residual scope #105

New issue

Closed

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

bsakaguchi commented

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

Owner

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

Problem

In src/domain/processComparison.ts, compareDimensions classifies the interaction dimension using the residual scope "terminal":

interaction: classify(
  "terminal",
  left.interaction_events,
  right.interaction_events,
),

ProcessCapture.residual_unknowns uses a scope enum with values terminal, exit, process, filesystem, protocol, cleanup, and network, with no explicit interaction scope. As written, any terminal residual is treated as affecting interaction comparison, while interaction-related unknowns cannot be represented explicitly in residual metadata.

Impact

Interaction evidence changes can be hidden behind terminal unknowns when only the interaction dimension is expected to be unknown.
Unknown provenance for dimensions is coupled to an unrelated scope, which makes behavior harder to reason about and audit.

Expected

Classify interaction residual uncertainty with an explicit interaction scope, or add a dedicated mechanism that maps unknown provenance to interaction events.
Preserve existing behavior for other dimensions while making interaction uncertainty semantics explicit.

Notes

Observed-dimension reporting should remain deterministic and avoid scope leakage across unrelated dimensions.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/158 ## Problem In `src/domain/processComparison.ts`, `compareDimensions` classifies the `interaction` dimension using the residual scope `"terminal"`: ```ts interaction: classify( "terminal", left.interaction_events, right.interaction_events, ), ``` `ProcessCapture.residual_unknowns` uses a scope enum with values `terminal`, `exit`, `process`, `filesystem`, `protocol`, `cleanup`, and `network`, with no explicit `interaction` scope. As written, any terminal residual is treated as affecting interaction comparison, while interaction-related unknowns cannot be represented explicitly in residual metadata. ### Impact - Interaction evidence changes can be hidden behind terminal unknowns when only the interaction dimension is expected to be unknown. - Unknown provenance for dimensions is coupled to an unrelated scope, which makes behavior harder to reason about and audit. ### Expected - Classify interaction residual uncertainty with an explicit interaction scope, or add a dedicated mechanism that maps unknown provenance to interaction events. - Preserve existing behavior for other dimensions while making interaction uncertainty semantics explicit. ### Notes Observed-dimension reporting should remain deterministic and avoid scope leakage across unrelated dimensions.

bsakaguchi

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