What goodLAC is
goodLAC separates an agent's proposal from the authority to create a real effect.
The authority split
The model or agent can express intent. The controller owns capability validation, identity binding, deterministic standing policy, exact approvals, emergency state, execution leases, dispatch, receipts, and other authority-relevant state.
What goodLAC is not
goodLAC is not an AI model, general-purpose agent, memory system, workflow engine, AI operating system, or general-purpose secret manager. A process is not goodLAC-governed merely because it can call the controller. The qualified governed path also constrains alternate effect routes, ambient filesystem/process/network authority, credentials, and administrator access.
Core invariants
- Controller mandatory for governed consequential effects.
- Least privilege and deterministic authority decisions.
- Exact approval binding and current-policy re-evaluation before dispatch.
- Deny precedence and fail-closed handling of unknown or inconsistent state.
- Durable effect truth, idempotency, and receipts.
- Credential separation and no model-side administrator authority.
- Emergency pause and restart/continuation safety.
- Audit records describe events; they do not grant authority.
Two different surfaces
The runtime surface accepts governed requests. The owner administration surface changes registry, policy, approvals, and emergency state. The Linux rc.12 administration path uses an owner-only Unix-domain socket that is not mounted into governed agent sandboxes.