DECISIONS AND GOVERNANCE
Decisions from documents
Keep a document whole and store its decision passages as proposals you confirm later.
Ask your assistant: “Save this document and keep possible decisions as unconfirmed proposals. I will review them later.” The document is saved whole. Exact decision passages become proposals: searchable, clearly unconfirmed, and linked to the passage they quote.
| Status | Means |
|---|---|
| Pending | A possible decision with an exact quote. Leave it until you need it. |
| Confirmed | A person confirmed it; it becomes a decision in the log. Who decided is recorded separately from who reviewed. |
| Rejected | Dismissed. The same passage will not be proposed again. |
flow decisions pending|confirmed|rejected|all [query] [--offset N]- Find possible decisions by status or text. Pending items are unconfirmed; review them whenever needed.
flow decisions get <id>- Show a possible decision, its status and the exact passage in the source document.
flow decisions propose <source-id> {"quote":"exact words"}- Save an exact passage from a document as an unconfirmed possible decision in a company workspace.
flow decisions confirm <id> [{"decidedBy":"name","decidedAt":"YYYY-MM-DD"}]- Confirm a possible decision, specifying or correcting who decided and when. The reviewer is recorded separately.
flow decisions reject <id>- Dismiss a possible decision. The same passage will not be proposed again.
The decider and date must appear in the document, or stay unknown. The assistant never guesses them, and the reviewer is never assumed to be the decider.
For meetings with named reviewers and a sign-off, use Meeting minutes instead.