WaveRegister
Delivery evidence that remains verifiable.
Anchor proof bundles with organisation-scoped signing identities, controlled key rotation, governed quorum and historical verification.
f3735cc5b784237b999857be3d73346d4957538ed220cec57d6301cd1e68aca4
- Organisation identity
- org:73d...:wave-register:v3
- Algorithm
- ECDSA P-256 / SHA-256
- Quorum
- 2 of 3 approvals
- Verified at
- 17 Jul 2026 · 14:31 UTC
Proof continuity
From delivery event to verifiable anchor.
01Evidence bundleDecisions, proofs, artifacts
→02Canonical hashDeterministic SHA-256
→03Governed signatureOrganisation identity
→04Anchor recordHistorically verifiable
Organisation isolation
One root of trust. A distinct signing key per organisation.
For public beta, an envelope-encryption model can keep a single managed root while encrypting a unique private signing key for every organisation.
Managed root KMSKey-encryption key
encryptsOrganisation ASigning key A
Organisation BSigning key B
Organisation CSigning key C
Governed quorum2 of 3
✓✓○
Two authorised approvals are required before the signature can be issued.
Controlled signing
High-value anchors can require multiple approvers.
Quorum separates evidence preparation from signature authorisation and keeps every approval in the audit trail.
Historical verification
Key rotation never invalidates old anchors.
Every anchor records the key version, public identity, algorithm and signature metadata required to verify it after future rotations.
v1Historical86 anchors
→ rotate →v2Historical143 anchors
→ rotate →v3ActiveKey healthy
Private beta available
Bring governance into the flow of delivery.
Show us the portfolio, Workhub, AI or evidence challenge you want to solve.