StreamVista / AI Command Center

Architecture

productionNever syncedUpdated never

Architecture

One request path, no shortcuts: every agent action flows through the platform API, the orchestrator and the tool gateway.

Request flow

Read left to right. Nothing is allowed to bypass a stage.

Stage 1

Apps

Studio, Creator, Buyer, Admin portals and Crayons surfaces raise a request.

Stage 2

Agent Platform API

Single entry point. Authenticates the caller, resolves the canonical agent.

Stage 3

Orchestrator

Plans steps, enforces budgets and timeouts, retries and routes work.

Stage 4

Agent

Canonical agent definition executes with its own prompt, policy and version.

Stage 5

Tool Gateway

The only path to tools. Applies allow-lists, rate limits and schema validation.

Stage 6

External Services

GitHub, rights registry, warehouse, media pipeline and third-party APIs.

Stage 7

Audit & Approval

Every run is logged; high-risk actions pause for human approval.

Stage 8

Result

A verified, attributable outcome is returned to the calling app.

Guarantees

What the architecture is designed to make impossible.

  • No app calls a model or tool directly — everything goes through the platform API.
  • No agent reaches an external service except via the tool gateway.
  • No high-risk action completes without an approval record.
  • Every run is reconstructable from the audit trail.

Current gap

What the diagram describes versus what is running.

The flow above is the target architecture. Today the agent platform API and orchestrator are target repositories rather than production services, agent definitions are still spread across product repositories, and no app is connected. Treat this page as the contract to build against, not a description of live traffic.