Onboarding
A short guide for reading judgment outputs.
How to read one Judgment Record
- Read the outcome type (affirm alignment / recommend adjustment / escalate).
- Confirm mandate + procedure versions (authority bindings).
- Scan constraints and confidence for the “why”.
- Treat outputs as audit artifacts: append-only and reviewable.
When escalation requires action
- Escalate means a boundary was reached; automation is suspended.
- Assign accountable ownership; record committee disposition.
- Route any portfolio change through human-controlled processes outside MandateOS.
Governance principles
What makes outputs institutionally reviewable.
Auditability
Every record binds to a mandate and procedure version and is written as an append-only artifact. The institution can reproduce the decision context by inspecting those sources.
Explicit authority boundaries
Mandates define what is allowed. Procedures define how judgment is applied. When authority is exceeded or confidence is insufficient, the system escalates rather than improvising.
No trades
MandateOS produces judgment records only. Recommendations may inform human decision-making, but portfolio changes are outside this system and outside this viewer.
Glossary
0 terms