Tool Boundaries & Containment Architecture
Separation between shipped application-level CI/CLI policy gates, private-core JSON-RPC
stdio proxy enforcement, and the standalone Outrigger v0.3.0 extraction.
Scope & Non-Claims: These controls are application-level policy gates (path canonicalization, diff verification, and task-manifest checks), not an OS or kernel sandbox. They do not replace OS user isolation, containerization, or hardware virtualization.
Shipped vs. Planned Boundary
Boundary Matrix| Layer / Component | Status | Enforcement Mechanism | Verification & Scope |
|---|---|---|---|
| Outrigger v0.2.0 (CLI & GitHub Action) | Shipped · Public | Zero-dependency Python 3.10+ stdlib CLI & GitHub Action enforcing fail-closed Git diff and OPS-1 scope gates at commit/PR time. | 46 passing tests, 6 subtests. Application-level policy boundary
(woodyardae/outrigger-protocol).
|
| Harbormaster MCP Control Plane | Private Core |
Line-delimited JSON-RPC 2.0 (stdio NDJSON) proxy intercepting tool calls via
ensure_within_scope, returning fail-closed error -32602 before upstream execution.
| 719+ automated tests. Private Core; powers runtime MCP path containment.
|
| Outrigger v0.3.0 Extraction | Planned · v0.3.0-dev |
Standalone extraction of Harbormaster's stdio NDJSON containment proxy into the public
outrigger-protocol package for any MCP host/client.
|
Bridges CI/CLI static diff gates with runtime -32602 path-containment enforcement under
one public specification.
|
Interactive JSON-RPC 2.0 stdio Containment Trace
Illustrative Trace ILLUSTRATIVE TRACE: Pure client-side vanilla JavaScript simulation demonstrating how the
Harbormaster / Outrigger v0.3.0-dev stdio NDJSON proxy evaluates
ensure_within_scope and fails closed with JSON-RPC error -32602. Zero external
network calls are made.
1. stdin: Client → Proxy (NDJSON) JSON-RPC 2.0
2. ensure_within_scope(): Boundary Evaluation ALLOWED
3. stdout: Proxy Decision / Upstream Gate Fail-Closed