Architecture
The Castle Architecture.
Five named layers, each with a distinct contract. Castle Wall: operating-system egress
enforcement, proven on macOS and, on Linux, proven on Ubuntu 24.04
(x86-64) only. Sentinels: behavioral observation inside the box. Charter: the encrypted
state and policy surface for cooperative agents. Heralds: receipts and reputation that
travel across vendors. Mantle: the install-time mechanism that binds the other four to
your machine. The layers compose, and none of them substitutes for another.
Perimeter
Castle Wall
Operating-system-level egress filtering. Network Extension on macOS, where Phase 1
is proven on a signed and notarized build. On Ubuntu 24.04 (x86-64),
a fresh install of the shipped package enforces a signed operator
policy per user account through five reboots on three fresh servers; DNS, DoH, DoT,
hostname paths, and other Linux platforms remain unproven.
kernel-binding
cgroup-v2
per-account-policy
Observation
Sentinels
Internal behavioral observation. Cross-platform auditd-tail, plus an eBPF watcher
scaffold on Linux that currently falls back to stub mode because the real probe loader
is not implemented. Seven
sentinels watching for prompt-injection signatures, anomalous tool sequences, and
policy drift. The sentinels surface; the operator decides.
ebpf
auditd-tail
seven-sentinels
Cooperative surface
Charter (Cooperative MCP)
Encrypted state, hash-chained audit, mandate primitives, canonical policy slots, and
substrate selector. Production call sites sign audit checkpoints when the fortress
holds an identity; a fortress with no identity yet, and the root daemon's split audit
store, write honest unsigned checkpoints, and the audit-chain row stays partial
pending the IC-05 external-verifier drill. Compliant agents that voluntarily route
through Sanctuary get the full surface. On macOS with the wall installed and armed,
non-compliant agents still hit the wall and the Sentinels.
approval-gates
context-gate
audit-log
Accountability
Heralds (Receipts and Reputation)
Cryptographic receipts on cross-castle transactions, portable reputation that
survives vendor churn. Concordia structures negotiation and commitments; Verascore
prices the reputation. Operators carry the trust record across vendors.
concordia
verascore
portable
Substrate
Mantle (install-time binding)
Install-time substrate-binding to the operator. The Mantle gives the rest of the
castle a verifiable anchor on the operator's machine before the agent runs.
Template init rejects orphan agent identifiers that are not bound to a wrapped harness.
install-time
substrate-binding
verifiable