Quorum
The Mind Quorum layering
Debate holds why. Quorum holds what was agreed. Lanes carry the coordinated stream; jobs are the executable units. Agreement is made in quorum, never by the delivery machinery: the pump transports facts and quorum interprets them.
Agreements and participants
quorum_create opens an agreement in a
project, optionally around a debate topic, with named participants of
kind client or role. Creation needs the conductor role plus an explicit
project grant; broad scope alone never originates an agreement.
quorum_participant_set moves
participants through pending, joined, fulfilled, withdrawn as reality
changes. quorum_list shows what the caller may
see (scope and participation filter silently).
Resolving and cancelling
quorum_resolve closes an agreement once
every lane beneath it is terminal (done, failed, or cancelled),
recording the decision and result references (pointers at the decisive
message or verdict, never duplicated reasoning).
quorum_cancel abandons an open agreement.
Both are terminal; both are conductor actions; both are audited.
When to use, when not to
- Use quorum when a decision needs named owners and later tracked execution. A bare debate verdict with no follow-through needs no quorum; a multi-stream effort with several executors does.
- Name participants honestly: required parties as pending-till-joined, not as decoration. Resolution reflects reality only if participation does.
- Do not resolve over open lanes: the gate refuses, because an agreement with unfinished streams is a wish, not a record.