Use case · Authority
Secure board approvals.
A board approves a merger, an executive compensation plan, or a major expenditure. Downstream, someone needs to prove — years later, possibly in court — that each named director actually approved this specific version at this specific moment.
The change: Multi-approver signed authority chain per board decision.
How it works
Four steps · every step signs a receipt.
The board decision is drafted as a cryptographic artifact — merger terms, comp plan, expenditure amount — hashed at draft time
Each director receives a signed authorization request bound to that specific artifact hash
Directors sign with biometric-attested identity · the chain accumulates their approvals in the order they arrive
Once threshold is met, the decision executes with the full signed authority chain traveling with it
Evidence
The proof this actually works.
- Every director's signature is verifiable independently · no 'who was in the room' ambiguity
- The artifact hash means no post-hoc 'we approved a different version' argument · the version is bound to the signature
- Multi-year replay: even if directors leave the board, their signatures at time-of-approval remain valid and reconstructible
- Edge case: Split decisions: each faction's signatures are logged separately · the chain records who approved what, not just the aggregate
- Edge case: Foreign directors under different jurisdictions: cryptographic signatures work uniformly, regardless of local e-sign law nuances
Related capabilities
If you're comparing alternatives
Trust status
Runs today. Honest about what's next.
We publish what's shipped and what's coming — the same list on every page.
Runs today
- Vault workflows running in production
- Cryptographic receipts emitted per action
- Immutable audit trail · Object-Locked
- Auth1 · Wallet · Document · Audit APIs
- Post-quantum primitives (Dilithium + Kyber)
- Benchmark v12 · 2,293,766 auth/sec
Coming next
- Public /verify/
/ receipt viewer - Public /replay/
/ decision viewer - docs.h33.you developer documentation
- SOC 2 Type II Certified
- Payment Requests + Rewards adapters