[GH-ISSUE #560] Thread platform and environment through process host and evidence stamping #288

New issue

Closed

opened 2026-10-15 18:23:29 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

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

Owner

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

Remaining scope

ProviderProcess and the default ProcessOwnership host still read ambient platform/environment inside their implementation. Several evidence builders also stamp process.platform rather than an observed producer or configured host. Thread local host identity through existing composition seams; represent a remote producer platform as unknown when unobserved. Removed replay evidence is no longer in scope. Setup/doctor evidence should reflect the host actually selected.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/560 ## Remaining scope ProviderProcess and the default ProcessOwnership host still read ambient platform/environment inside their implementation. Several evidence builders also stamp process.platform rather than an observed producer or configured host. Thread local host identity through existing composition seams; represent a remote producer platform as unknown when unobserved. Removed replay evidence is no longer in scope. Setup/doctor evidence should reflect the host actually selected. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

bsakaguchi

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