Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Architecture

portcullis process model: agent client to edge to upstream, with an isolated broker and runner
The process model. The edge decides and routes; execution and secrets are separated into the runner and the broker.

The edge holds no upstream credentials and cannot spawn a process (enforced by the deny-imports check). The runner cannot read the secret store. Compromise of either alone is contained.

Crates

pc-core (pure domain types) · pc-proto-mcp (codec + version negotiation) · pc-edge (transports, auth, policy wiring, limits, breakers, metrics) · pc-broker (secrets, tokens, egress) · pc-runner (sandbox) · pc-policy (RBAC/ABAC + cache) · pc-audit (hash-chained log) · pc-catalog (manifests, rug-pull, poisoning) · pc-proto-openapi (translation) · pc-facade (find/invoke + tokens) · pc-state (versioned persistence) · pc-conformance (spec suite) · pc-cli (the binary).

pc-core depends on nothing in-repo; the dependency graph is acyclic and checked in CI. The protocol is a plugin, not the architecture: pc-core names no wire format.