docs(security): define controlled replay authority

This commit is contained in:
N0zoM1z0
2026-07-16 11:54:05 +09:00
committed by N0zoM1z0
parent 4a30820a93
commit 461990da3f
4 changed files with 569 additions and 6 deletions
+15
View File
@@ -72,3 +72,18 @@ specific route, string, API, channel, module, native export, or node ID.
Because source Evidence and derived Evidence are retained by the normal session
ledger, evidence bundles, analysis snapshots, and investigation workspaces can
carry these records without another persistence format.
## Controlled replay boundary
These shipped workflows never execute a graph node or recovered module. A
future extracted-module replay may consume an exact trace handoff only through
the separate `javascript_replay` authority, two-phase content-bound approval,
and mandatory Linux OS sandbox fixed by
[ADR-0002](adr/0002-controlled-replay-authority-and-sandbox.md). Browser,
Electron, Process Capture, artifact-read, and static-analysis approvals do not
authorize that execution.
Replay observations will retain `controlled-replay` authority. They cannot
promote static inference into passive runtime observation or prove that the
original application, renderer, preload, main process, or remote service
behaved identically.