Eventium.aiDocumentation

RESPONSIBILITY BOUNDARIES

Every capability has an owner.

The public architecture explains stable responsibilities without exposing credentials, private topology, or operational recovery detail.

Request path

  1. The Eventium API authenticates the actor and resolves active scope and entitlement.
  2. Nexus classifies intent and routes to an allowed capability.
  3. Constellation coordinates planning or review when multiple agents are required.
  4. Apex applies governance and approval boundaries.
  5. MCP recalls allowed Atlas evidence for AI work.
  6. Gaia attaches tools or an isolated runtime only for approved execution.
  7. Verified outcomes return to Atlas as durable, scoped context.

Product handoff

Forge produces the artifact. Pilot opens its preview or supervised computer-use experience only when a preview exists and the capability is available. Apex opens the corresponding code and Gaia workspace only when the user is authenticated and entitled.

Restricted architecture remains restricted. This page intentionally documents public boundaries only. Private deployment topology, secrets, and support-only diagnostics are not published here.