Isolation / provisioning / recovery
Badland Agent Runtime
The runtime beneath the personal-agent product: tenant provisioning, tool boundaries, routing, observability, and recovery.
OUTCOME / 01
Treats personal agents as long-lived services with explicit ownership and recovery—not disposable chat sessions.
Lifecycle
Provisioning creates an isolated tenant, applies a bounded tool and model policy, establishes delivery routes, and records enough state for the service to be inspected and repaired later.
Safety model
The runtime combines container and process isolation with explicit filesystem and credential scopes. Transport ownership fails closed, and health checks exercise the user-facing path rather than reporting a green process alone.
Operations
Deployment, logs, traces, usage controls, backups, and repair workflows are part of the product. This is where most of the hard-won agent expertise lives: making stateful, tool-using software recoverable after the demo ends.