Skip to content

Verified boundaries

Current checks prove repository governance and deterministic documentation behavior. The sandbox control fixture additionally proves unit-level request freezing, principal non-enumeration, finite admission, typed termination, and redacted bounded replay. A real PostgreSQL adapter integration now proves serializable immutable acceptance, pool/process-component restart reconnect, concurrent conflict handling, lease fencing, cleanup-confirmed tombstones, and ordered transactional outbox replay. It does not yet prove the complete control service across separate process failure, durable output-store replay, host-agent enrollment, hostile-tenant isolation, Linux/KVM behavior, Firecracker enforcement, production network policy, or command-scoped secret delivery.

Future documentation will label proof as unit, workflow, integration, local Tilt E2E, or Linux/KVM E2E. A local macOS process adapter can demonstrate developer workflow only; it can never serve as Firecracker security evidence. Operators remain responsible for declared infrastructure, credentials, retention, backup, and environment-specific controls.

The temporary Docusaurus dependency-audit exception is retired. Astro Starlight’s locked production dependency graph is checked directly by npm audit --omit=dev --audit-level=high in just docs-check; it must remain clean for documentation publication. The retired route remains only as a compatibility redirect to this section.