Clawdlinux Operator Evidence Boundaries
The repository provides HMAC hash-chain primitives and an offline JSONL verifier. Automatic complete per-run signed evidence is not connected.
Available Primitives
- Audit hashing, signing, and JSONL chain verification.
- Workload status, routing metrics, and optional traces.
- Cost-reporting interfaces and a volatile in-memory reporter for local evaluation.
audit-verify supports JSONL input. Its ClickHouse source adapter is a stub. The controller does not automatically append every run event to the audit chain. Optional MinIO storage and audit table creation do not establish same-run capture or bundling. Durable storage, production signing keys, and independently verified checkpoints remain integration work.
Interpret Evidence Narrowly
| Observation | What it does not establish |
|---|---|
| A workload completes | Complete signed capture of that workload's actions |
| A NetworkPolicy exists | Packet enforcement by the cluster CNI |
| A pod selects gVisor | A working runsc installation on its node |
| Cost metrics exist | Durable billing records or complete budget enforcement |
| A prior-run JSONL fixture verifies | Evidence capture from the current workload |
| Offline JWT validation works | A complete air-gap installation test |
Keep current-run observations separate from configuration checks and prior-run fixtures. Verify namespace and label selection when testing network controls. The cluster CNI must enforce NetworkPolicy. Nodes need runsc for gVisor isolation.
Operational Audit
Configure Kubernetes API auditing through your cluster provider when required. Kubernetes Events are not a Secret-access audit log. External actor identity propagation and universal tool-call mediation are not complete current product capabilities.
Clawdlinux Operator does not claim compliance certification. Map configured controls and collected evidence to your own requirements and independent assessment.
See architecture, security, and monitoring.