omni.x1
Purpose
omni.x1 is the advisory intelligence namespace. Omni observes the system state — tasks, jobs, service events, records, signals, access states — and produces recommendations for human decision-makers. It does not execute, approve, or mutate anything.
Architectural role
Omni sits alongside the execution system. It reads from the same data the system generates and uses that information to help administrators and operators make better decisions. It cannot advance, reverse, or bypass any execution spine transition.
Position in the system
Omni is not part of the execution spine. It is an observer layer that surfaces intelligence from it.
[Execution Spine] → Record, Signal, Task, Job, Access State
↑
omni.x1 (reads, summarizes, recommends)
↓
Admin Desk /admin/desk/omni (human review)What it governs
- Observation of tasks, jobs, service events, records, trust signals, and access states
- Interpretation of system state into human-readable summaries
- Recommendations and anomaly detection (aging queues, stuck work, exceptions)
- Trust advisory generation — operator signal summaries attached to routing context (read-only)
- Multi-operator isolation — each operator’s data stays within its own account boundary
What it does not govern
- It does not create execution authority.
- It does not approve tasks, create jobs, or complete service events.
- It does not change access state.
- It does not settle payments.
- It does not mutate records.
- It does not bypass policy.
Constraint table
| Action | Omni’s status |
|---|---|
| Approve a task | Cannot |
| Create a job | Cannot |
| Reassign an operator | Cannot without approval |
| Complete a service event | Cannot |
| Change access state | Cannot |
| Settle a payment | Cannot |
| Mutate records | Cannot |
Trust advisory
When Omni processes a request for an operator, it can include a read-only trust summary:
{
"operator_slug": "qtm-detailing",
"active_signal_count": 7,
"has_trust_signal": true,
"trust_state": "present",
"latest_signal_emitted_at": "2026-04-21T..."
}This is labeled trust_advisory_effect: "none". Omni can see this information but the system does not act on it in v0.01.
Current status
Namespace assigned. Partially implemented in the Planck pilot runtime via the Admin Desk at /admin/desk/omni.
Future direction
Full agent coordination (CEO agent, COO agent, synthesized Decision Packet for admin review). Routing eligibility wired into surface assignment. Anomaly detection surface.
Guardrails
- Preserve the distinction between planned, partial, and live.
- Omni observes and recommends only. It has no execution authority.
- Multi-operator isolation must be preserved.
- Trust advisory data is read-only and does not drive routing.