Alan Woodyard

Architecture

Tool boundaries

Outrigger Protocol is the public Python package. Harbormaster is the reference runtime for the same kind of path gate. Both checks run in the application. They do not replace operating-system accounts, containers, or hardware virtualization.

The changelog records v0.2.0 for the CLI and the GitHub Action. pyproject.toml in the public tree is version 0.3.0, and that tree already contains outrigger proxy. The README still describes a standalone v0.3.0 extraction as planned.

Public index

What the code checks

Outrigger check, Outrigger proxy, and the Harbormaster MCP server.
Component Status What it does
outrigger check Public, changelog v0.2.0 command_check loads an OPS-1 manifest and calls check_git_diff_scope. That function runs git diff --name-only and compares each changed path with the writable scope. When the manifest lists writable paths, a path outside that list makes the command return BLOCKED. A path that matches a forbidden pattern returns BLOCKED as well. The composite GitHub Action runs outrigger check. The package declares no runtime dependencies and requires Python 3.10 or newer.
outrigger proxy In tree, README still says planned outrigger proxy calls run_stdio_proxy. On a tools/call frame, ensure_within_scope checks path arguments. A path outside the allowed roots is returned as JSON-RPC error -32602, and that frame is not written to the child process. The module is src/outrigger_protocol/proxy.py.
Harbormaster Reference runtime The MCP server in mcp_server.py speaks JSON-RPC 2.0 over stdio. ensure_within_scope returns false for empty input, for a .. path segment, and for a path that does not resolve inside an allowed root. The server reports that rejection with JSONRPC_INVALID_PARAMS, which is -32602, and does not dispatch the call. Harbormaster is not one of the six pinned public repositories.

Path decision sketch

This panel runs in the browser only. It sketches an allow or reject decision for a workspace root of /workspace/repo. It is not the Python ensure_within_scope function, and it does not contact a live process.

Request JSON-RPC 2.0
 
Scope check ALLOW
 
Decision Not forwarded on reject