01
Confirmation by default
Ordo proposes. A person approves, edits, or dismisses before follow-through.
Trust
Ordo needs a person before it does real work. Every proposal keeps its source, and every yes or no is on the record.
Audit event
Priya approved “Close security review before signature.”
01
Ordo proposes. A person approves, edits, or dismisses before follow-through.
02
The sentence it came from stays attached, so you can see why Ordo suggested it.
03
Capture, proposal, approval, and dismissal are written down.
04
Confirmed internal work can be undone. External action is not the live promise.
An example of the trail: who acted, what changed, and which source it came from.
| When | Who | Action | What | Source |
|---|---|---|---|---|
| 09:14 | Priya | Approved | Close security review before signature | Gmail |
| 09:16 | You | Edited | Send revised SOW - due Thursday | Gmail |
| 09:22 | Alex | Dismissed | Chase Jordan on the vendor intro | Slack |
| 09:40 | Priya | Created | Reminder: status before Friday | Pasted notes |
Members review their own work. Admins invite people and route queues. Owners hold retention and any higher autonomy setting.
| Member | Admin | Owner | |
|---|---|---|---|
| Review and confirm proposals | |||
| Invite people and assign roles | - | ||
| Change retention and export | - | - | |
| Enable a higher autonomy tier | - | - |
We will walk the confirmation model, the audit log, and what is still roadmap.