Production beta · REST + MCP

QuorumMyAction

Put separation of duty outside the acting model. Create distinct private member links, require an N-of-M threshold, then atomically consume one execution right.

Use it when one approval is not enough

Require two operators, multiple business functions, or another declared threshold before a transfer, publication, permission change, production action, or irreversible workflow step.

Decision rule

Never execute from status: approved alone. Proceed once only when owner consume returns both execution_right_acquired: true and safe_to_execute: true.

POST /v1/quorums/manage
{"operation":"create","action_fingerprint":"sha256:...","required_votes":2,"member_count":3,"expires_in_seconds":3600}
Bearer separation, not identity proof. Each link is distinct and can decide once, but your application must deliver each link to the intended independent authority and enforce its own legal and organizational rules.