Proposals & Events
Consent-proposal workflow and time-aware record of assemblies and deadlines.
Consent proposals
A proposal wraps a document with a state machine: draft → proposed → consent_round → consented | rejected | withdrawn. One proposal per document. Create one from the metadata editor in Index (button Create proposal), then open it from the Proposals tab.
How a round works
- Draft — title and linked document only. Not visible as a live proposal yet.
- Proposed — any member can respond. Editors can still tune wording.
- Consent round — a time-boxed window (optional end-date). Responses are collected.
- Consented / Rejected — an editor or org-admin records the outcome + optional note.
- Withdrawn — the proposer can pull it at any stage before a terminal state.
Responses
- Consent — I agree.
- Stand aside — I won't block but have reservations. Reasoning recommended.
- Object — I block. Reasoning is required.
Who can do what
- Any member of the owning organisation: read + respond.
- Editors and org-admins: create, transition states, add decision notes.
- Contributors own their response row (update or withdraw it).
Events
The Admin → Events page lets editors and org-admins add assembly dates (AGO, AGE), CF meetings, deadlines, and external obligations. A document can be linked to an event from the metadata editor. Insights' Timeline interleaves events with documents.