QM3 shared custody
Shared custody — where an action needs several owners to agree — expressed in the framework's own language. The QM3 operator is superposition:
QM3: |ψ⟩ = ∑ cᵢ |ϕᵢ⟩
A custody object holds a superposition of N owner principals until M signatures arrive, then it collapses — exactly one outcome materialises on the audit chain. Nothing needs a new metaphor: the framework already speaks superposition and collapse, so M-of-N custody is just that mechanic made concrete.
The lifecycle
Create
Open a custody object under a machine with N owners and an M-of-N threshold.
Sign
An action opens a pending transition (the superposition). Each owner adds a signature bound to their ZeqID.
Collapse
Once M valid signatures exist, the state collapses and the single outcome is written to the audit chain.
A pending action that never reaches its threshold is expired by the machine's own per-machine ticker — overdue transitions don't linger.
What protects it
Signatures and payloads are sealed with HITE encryption, so what's in flight is both confidential and tamper-detectable. And because the collapse is written through the entangled-state chain, a custody object's history carries the same ZeqProof and seal guarantees as any other machine state — every signature and every collapse is provable after the fact, by anyone, without trusting the machine that recorded it.
Read next
- HITE encryption — what seals the signatures.
- ZSC — the secure context — where owner keys are held.
- Proofs — why a collapse is verifiable.