The first pilot binds one real decision to real trust material.
The platform is described as planned, not deployed. Vendor choices are made from the deployment's requirements, not pre-integrated here.
The first deployment pilot will bind one defined evidence-submission or decision record to an atomic replay claim, persistent encrypted-envelope storage, trusted key resolution and an explicit verification profile. Vendor choices will be made from the deployment's data classification, residency, availability and key-custody requirements.
Supplied by the deployment, not the SDK.
Atomic replay
Persistent, atomic replay claiming so a valid record cannot be reused. The SDK defines the boundary; the store is deployment-supplied.
Key custody
Managed key generation, storage, rotation and revocation through a KMS or HSM. The default Node provider is not production custody.
Trusted time
An independent time source where chronology must be defensible. Declared time alone is a signer assertion.
No Cloudflare D1, KV, R2, Durable Objects, specific KMS or trusted-time authority is integrated at this stage.