Documentation
OperationsSHIPPED
Worker attestation and quarantine
Compare worker-reported ledger, build, and configuration state before assigning more work.
Manifest→
Policy→
Human approval→
Worker→
Attestation→
Ledger
Authority is resolved before execution
Attestation fields
CARNELIAN_LEDGER_HEADcarries the worker view of the latest ledger hash- The worker computes or reports a build checksum
CARNELIAN_CONFIG_VERSIONidentifies the expected configuration state
Verification path
Health checks carry optional attestation data to the orchestrator. Matching values are recorded; a ledger-head, build-checksum, or configuration-version mismatch sends the worker into quarantine.
Quarantine behavior
A quarantined worker continues running but receives no new tasks. Karnelian records `worker.quarantined` as a privileged ledger event and preserves the reason for operator diagnosis.
Trust boundary
Current attestation is self-reported and quarantine is advisory. The repository explicitly identifies hardware-backed remote attestation, such as TPM-based verification, as a stronger future option rather than a shipped guarantee.
Recovery
- Refresh a stale ledger-head value and restart the worker
- Redeploy a worker whose build checksum differs
- Propagate the current configuration version before clearing quarantine
- Trigger a fresh health check after correcting the root cause
