π II. PRESENCE: the daily cockpit
Summary
Presence is the supervision surface: read the situation, choose posture, certify a technical (WRITE) action, then verify the actual execution outcome. Detailed law and business-label editing happens in Emergence.
Cockpit mode: daily usage
- Cadence: about 5 minutes per day.
- Goal: consume reliable decisions, not perform engineering.
- Expected outcome: fast arbitration and operational continuity.
Presence keeps decisions on one screen:
- Situation and rules β idea, active rule, modality gauges (visible steering evidence).
- Perspective and perimeter (side panel) β the βwhyβ, then the βhow farβ, including the verb applied to the selected rule.
- Integrated validation β no standalone pending panel; validation runs in the current cockpit flow on the active rule. Approve (reinforce) dispatches execution and anchors the decision for this pass.
- WRITE feedback in Perspective β the right panel shows the current WRITE state (success, failed, pending) and reflects it in Perspective history per agent/idea context.
- Reject and correct β opens Emergence with agent, idea, rule, and action reference prefilled, plus the reason you entered, so you can adjust the law without losing context.
Supervision delegation
- Typical firm setup: D1/D2 actions can be approved by mission leads in the Presence flow.
- Leadership governance: D3/D4 approvals remain under leadership control.
- Role separation: operational validation happens here; law editing happens in Emergence .
The 5-minute ritual and D1βD4 are covered under Efficiency β performance and costs . Printable due-diligence supervision evidence is summarized in Strategic FAQ .