[PR #257] [MERGED] docs(security): define controlled replay authority #1906

Closed
opened 2026-10-16 21:12:23 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/257
Author: @N0zoM1z0
Created: 7/16/2026
Status: ✅ Merged
Merged: 7/16/2026
Merged by: @N0zoM1z0

Base: main ← Head: agent/controlled-replay-authority-policy


📝 Commits (1)

  • c22a55d docs(security): define controlled replay authority

📊 Changes

4 files changed (+569 additions, -6 deletions)

View changed files

📝 README.md (+3 -3)
➕ docs/adr/0002-controlled-replay-authority-and-sandbox.md (+547 -0)
📝 docs/adr/README.md (+4 -3)
📝 docs/javascript-application-workflows.md (+15 -0)

📄 Description

Summary

  • accept ADR-0002 as the mandatory design gate for controlled JavaScript replay without claiming that replay is already shipped
  • separate the future javascript_replay permission capability from passive browser/Electron observation, unsandboxed Process Capture, and artifact-read authority
  • require content-bound plan/execute approval, a Linux OS sandbox, architecture-checked seccomp, cgroup v2 resource controls, no host/external network, no writable host paths, and fail-closed unavailability
  • define module/input/stub/runtime provenance, deterministic execution commitments, bounded serialization, Evidence v2 authority, post-admission failure semantics, cleanup, and reproducer export policy
  • add an explicit ten-point implementation/conformance gate for the isolated worker PR and link the accepted-but-unimplemented boundary from the README and JavaScript application workflow docs

Contract and behavior

  • No public tool, CLI command, configuration field, permission grant, provider route, or execution path is added by this PR.
  • The current 82-tool inventory is unchanged.
  • Shipped static application workflows remain non-executing.
  • Future replay observations use controlled-replay Evidence authority, while the permission capability is separately named javascript_replay.
  • Unsupported platforms or incomplete sandbox backends must report unavailable; vm-only and process-only fallbacks are rejected.

Verification

  • npm run check
  • npm test -- --reporter=dot — 130 files / 906 tests passed
  • npm run docs:check
  • npm run format:check
  • npm run knip
  • npm run jscpd
  • npm run scan:todos
  • changed-Markdown internal link resolution check
  • git diff --check

Real Hopper, Ghidra, and browser verification were not run because this PR changes documentation only and does not alter provider, package, browser, or execution behavior.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/257 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 7/16/2026 **Status:** ✅ Merged **Merged:** 7/16/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `agent/controlled-replay-authority-policy` --- ### 📝 Commits (1) - [`c22a55d`](https://github.com/morluto/rea/commit/c22a55de07f2cc500c5bd21b54c971c4d7bda9d5) docs(security): define controlled replay authority ### 📊 Changes **4 files changed** (+569 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+3 -3) ➕ `docs/adr/0002-controlled-replay-authority-and-sandbox.md` (+547 -0) 📝 `docs/adr/README.md` (+4 -3) 📝 `docs/javascript-application-workflows.md` (+15 -0) </details> ### 📄 Description ## Summary - accept ADR-0002 as the mandatory design gate for controlled JavaScript replay without claiming that replay is already shipped - separate the future `javascript_replay` permission capability from passive browser/Electron observation, unsandboxed Process Capture, and artifact-read authority - require content-bound plan/execute approval, a Linux OS sandbox, architecture-checked seccomp, cgroup v2 resource controls, no host/external network, no writable host paths, and fail-closed unavailability - define module/input/stub/runtime provenance, deterministic execution commitments, bounded serialization, Evidence v2 authority, post-admission failure semantics, cleanup, and reproducer export policy - add an explicit ten-point implementation/conformance gate for the isolated worker PR and link the accepted-but-unimplemented boundary from the README and JavaScript application workflow docs ## Contract and behavior - No public tool, CLI command, configuration field, permission grant, provider route, or execution path is added by this PR. - The current 82-tool inventory is unchanged. - Shipped static application workflows remain non-executing. - Future replay observations use `controlled-replay` Evidence authority, while the permission capability is separately named `javascript_replay`. - Unsupported platforms or incomplete sandbox backends must report unavailable; `vm`-only and process-only fallbacks are rejected. ## Verification - `npm run check` - `npm test -- --reporter=dot` — 130 files / 906 tests passed - `npm run docs:check` - `npm run format:check` - `npm run knip` - `npm run jscpd` - `npm run scan:todos` - changed-Markdown internal link resolution check - `git diff --check` Real Hopper, Ghidra, and browser verification were not run because this PR changes documentation only and does not alter provider, package, browser, or execution behavior. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-16 21:12:23 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#1906
No description provided.