consensus-check

To document group consensus, you can run a formal polling process that verifies quorum based on the attendee list and records each member's explicit position on the issue. This generates an auditable per-member consent record in a YAML template for traceability.

Consent mode checks for the absence of voiced objections, whereas consensus mode requires absolute agreement from participants. Both modes handle absentee members and validate quorum before producing a final group position record.

You execute a step-by-step consensus poll by specifying inputs like the question, participant list, mode, and quorum, then polling each member individually. Absentee handling and quorum validation are applied automatically during the process.

Yes, the per-member consensus record generated in the consensus-record-template.yaml file is designed for traceability and seamless integration with higher-level governance flows.

If quorum fails during a formal consent check, the polling process identifies the shortfall based on the attendee list and mode, requiring an escalation or re-polling of the group at a later time.

No, formal polling for group consent requires no external dependencies, utilizing only internal assets to generate and store the final consensus record template.