Boundaries and responsibility

The system supports and controls a decision. It does not replace the mandate.

Every product has a deliberate boundary, and every material decision retains a named human owner.

The system does
  • Normalises feeds and creates a versioned, inspectable signal.
  • Builds a cited brief against positions and limits.
  • Checks an order and blocks it when a rule or state fails.
  • Answers from an approved document corpus.
  • Prepares and executes an action after named approval.
  • Compares system versions before release.
The system does not
  • Promise profit or replace an investment mandate.
  • Place an order from Nova or Atlas.
  • Change a risk limit outside the authorised process.
  • Invent an answer when evidence is insufficient.
  • Perform a state change without named approval.
  • Release a model change around the Iris gate.
Shared responsibility

Who owns each part of Run

AreaOKAIClient
Package contour availabilityOperates to the agreed SLAProvides access and stable client-side feeds
Mandate and limit qualityImplements policy in Atlas and AegisApproves policy and names its owner
Trade decisionDoes not make itDesk or PM decides
Order admissionAegis applies configured rulesPolicy owner and OMS remain accountable
Approved documentsAva enforces the listClient owns corpus and access
Model releaseIris calculates the gateRelease owner approves go
Procurement language

The purchase covers licensed access to Nova Pulse, Desk Trio, Control Plane or Full Stack. Scope, Prove and Run describe the connection schedule. Studio work is a separate purchase only when an additional line is agreed.