Attesto

Operators

Readiness, assurance, and production evidence

This page explains public, tenant-safe operator concepts. It does not publish private control-plane procedures, credentials, or internal infrastructure instructions.

Canaries

Canaries are evidence-producing checks that prove the production path still works. Attesto 2.0 uses canaries for the full lifecycle, fork defense, quorum, connectors, Local Vault, multi-tenant witness isolation, and Proof of Evolution readiness.

CanaryWhat PASS means
LifecycleEvent, receipt, window, checkpoint, witness, anchor, bundle, and offline verify all succeeded.
Fork defenseA conflicting checkpoint history created fork evidence and verifier rejection.
QuorumTenant witness policy was satisfied by the required witness statements.
ConnectorConnector auth, source observation, idempotency, and revoke behavior worked.
Local VaultRelay, encrypted spool, source attestation, and optional witness behavior worked.

Readiness

Readiness is not one green light. Production-ready evidence requires signer health, trust policy, witness quorum, verifier corpus, backup restore evidence, metrics protection, and release evidence.

Assurance reports

A good assurance report answers: “This stream is verifiable because...” and then lists receipts, window inclusion, checkpoint consistency, witness/quorum status, anchors, bundle digest, and verifier result.

Production evidence health

Tenant-facing runbooks

Public runbooks should tell tenant users what they can do safely: rotate a system key, request a new export, inspect stream health, verify a bundle, retry a connector delivery, or pause reliance on a stream range when fork evidence appears. Private operational details stay outside docs.attesto.eu.