The Operator Workspace
app.iai.one is the human-facing control layer in the ecosystem: dashboards, mission control, review flows, alerts, and operator actions.
Purpose
Dashboards
See operational state, execution summaries, and critical activity in one place.
Human Review
Approve, reject, inspect, or rerun workflows when a fully automated path is not enough.
Control Surface
Expose the product-facing controls that should not live inside the builder itself.
Boundaries
What App Owns
- Dashboards and operator status views
- Human-in-the-loop review flows
- Role-based access and workspace controls
- Product-facing workflow operations
What App Does Not Own
- Visual flow authoring logic
- Core runtime execution engine
- Mail delivery implementation
- Platform API contract design
Relationships To Other Surfaces
With Flow
App consumes execution state and operational controls produced by flow.iai.one.
With Mail
App helps operators view or respond to alerts delivered by mail.iai.one.
With API
App uses api.iai.one for authenticated state changes and data retrieval.
Annotated Walkthrough
Enter the correct workspace mode first. The app should make it obvious whether the operator is in dashboard, queue, alert, or run-review context.
Scan top-level metrics before diving into a single item. Operators need immediate status, not hidden health signals.
Open the queue item that requires a human decision and review the supporting execution detail before acting.
Approve, rerun, or escalate from the detail panel. Those actions should stay close to the evidence the operator is evaluating.
Future Direction
Even before the full app documentation is written, the ecosystem docs should already make it clear that app.iai.one is a first-class product surface and not a footnote under flow.