01 · NOVA · Governed Execution System
The economic case was approved. What actually gets built and runs?
The question NOVA answersCan an approved AI-native process be built as intended, operated with its controls in place, and evaluated on evidence of what actually happened?
NOVA is PurpleAI’s Governed Execution System. NOVA Build turns an enterprise-approved change into an AI-Native Process Contract and release-ready work. NOVA Run operates what was released under its permissions, human decisions and controls, and records what happens once it actually runs. Build and Run are two planes of one product.
Before NOVA
- CortexQualified Process CaseThe process qualifies on evidence
- Enterprise DeltaCertified Economic Process CaseProduct-defined; not an accreditation and not approval to build
LeadershipApprove, change or declineRequired before NOVA Build; not a release approval
NOVA · one Governed Execution System
Build planeAI-Native Process ContractEngineering work, tests, controls and release evidence
Run plane · only once released and deployedControlled operationPermissions, human decisions and recorded observations
Enterprise Delta · only if the change runsActual operating evidence compared with the approved case
Hippokeeps the decisions, versions and evidence along the way
- What goes wrong
- The approval drifts in deliveryOperating-model changes shift as they pass into backlogs, code and configuration, and the controls the case assumed are not always the ones built.
- No single unit of controlWork runs across agents, tools, workflows and people, with nothing that matches the process the enterprise approved.
- No evidence of what ranWithout runtime evidence tied to the approved version, nobody can say whether the case held.
02 · NOVA Build
From an approved decision to engineering work your team can pick up.
NOVA Build turns the enterprise-approved change into an AI-Native Process Contract and a first draft of engineering backlog items, with controls, acceptance tests and links to the approved case.
Your engineers review, refine and implement that work in their own delivery tools; Jira and Confluence are intended handoff points, not connected workspaces. Your designated authorities, not NOVA, approve release.
How an approved decision becomes build-ready work
Loading process example…
Loading the selected NOVA example…
Loading process example…
Go deeper
On demandExplore the six-step engineering handoffEvery step, owner, task and acceptance criterion
How an approved decision becomes build-ready work
Loading process example…
On demandInspect connected delivery signalsFive signal types with source, link and status
Connected engineering and delivery signals · where configured
Each signal stays linked to the contract, story and version it belongs to.
| Signal | Source | Linked to | In this illustration |
|---|---|---|---|
| Loading process example… | |||
| Loading process example… | |||
| Loading process example… | |||
| Loading process example… | |||
| Loading process example… | |||
Illustrative signal states. Nothing here comes from a connected tool, and missing evidence is never treated as passed.
On demandSee the full AI-Native Process ContractAll eight clauses and their status
On demandExplore target engineering toolsTool categories; no connection to a specific product is claimed
Works through the tools you already use
To build the workWork management · source control · coding assistants · CI/CD · cloud · testing and evaluation · security
To perform the workBusiness systems · workflow and case management · existing automation · enterprise APIs · AI agents · human queues
Shown by category. No connection to a specific product is claimed, and NOVA is not an IDE, repository or CI/CD platform.
The contract carries the decision into the build. Nothing is released that the contract does not allow.
See the controlled run model03 · NOVA Run
Run the approved process. See what happens across systems, agents and people.
Once the enterprise authorises release and the process is deployed, NOVA Run coordinates permitted actions across agents, applications, workflows and human teams under the approved Process Contract, and relates their events, logs, traces and metrics back to that contract.
The enterprise retains service accountability, incident response and reserved decisions. Routine steps can run automatically, and nothing overrides a policy. Through authorised connectors, NOVA observes only participating systems and data within agreed permissions; a connected signal is not proof of realised savings.
NOVA BuildApproved requirement → revised engineering work → customer-authorised release
NOVA RunProcess events and scoped telemetry, tied to the released version
Governed process execution
Loading process example…Loading process example…On demandExplore connected observabilitySystem categories, signal types, provenance, guardrails and what owners can see
What the run should record
Loading process example…Recorded only if it runsGuardrails in operationPermissions limit what each agent and system may do. If AI consumption per unit of work approaches the envelope, the process is flagged for a person to review.
Connected observability
Intended · only where configured and permitted
- Business apps and workflowProcess events and decisions
- Delivery pipelines and deploymentsChanges and release versions
- Production monitoringMetrics and traces
- ITOps and ITSMIncidents and changes
- AIOps and observabilityLogs and anomalies
NOVA connector and signal accessOnly where configured and permitted, within agreed scope
- Events
- Logs
- Traces
- Metrics
- Changes
- Exceptions
Every signal carriesSource · released process version · time and correlation · permission scope · confidence and gaps
- Execution and policy visibility
- Deviation and exception review
- Release-to-runtime traceability
- Economic evidence for Enterprise Delta, when supported
- Versioned context for Hippo
Your ITSM, monitoring and AIOps platforms stay the systems of record. NOVA reads relevant signals from them; it does not replace them.
- NOVA Run coordinates
- Within-policy work across agents, systems and queues
- Enterprise operations decides and owns
- Reserved approvals, policy exceptions, incident response and service accountability
- The recorded outcome
- Decision, authorisation, action, exception and consumption, only if it actually runs
People keep the decisions the contract reserves for them. NOVA does not approve on their behalf.
See what the enterprise can verify later04 · Three kinds of evidence
Know what was released. Know what ran. Then test the economics.
What was released, what actually ran and what it means economically are different questions, answered by different evidence and different owners.
A release is not proof of results, and an economic assumption is never recorded as a runtime fact.
| Evidence | Owner | What it shows | When it exists | For the selected example |
|---|---|---|---|---|
| Release evidence | NOVA Build | Which approved contract version was built, which tests and controls passed, and who signed off | At release, by design | Loading process example… |
| Runtime observation | NOVA Run | Volumes, exceptions, human decisions, timing and AI consumption | Only when the process actually runs | Loading process example… |
| Economic assessment | Enterprise Delta | Actual operating cost compared with the approved economic case | Only with enough runtime evidence | Loading process example… |
Hippokeeps each version, decision and piece of evidence linked to the approved case it belongs to.
NOVA works fromThe approved economic case and leadership’s decision; policies, permissions and approval rules; the enterprise’s engineering tools; and the agents, systems, workflows and people that perform the work.
NOVA producesThe AI-Native Process Contract; built and released capability with its release evidence; the process in controlled operation; and, once it runs, runtime observations for Delta and Hippo.
Each layer answers a different question, and none is filled in from another.
Understand NOVA’s responsibility05 · Where NOVA fits
Build and run what was approved. Keep every control accountable.
NOVA Build and NOVA Run are one Governed Execution System. NOVA works with the enterprise’s tools and people; it does not replace them, and it decides nothing that belongs to someone else.
- Cortexqualifiesthe process, on evidence
- Enterprise Deltaevaluatesthe economics
- Leadershipauthorisesthe change
- NOVAbuilds, runs and observeswhat was approved
- Hippopreservesthe context
Within an enterprise transformation
Discuss governed execution for an approved change
NOVA is scoped with PurpleAI as part of an enterprise engagement. There is no self-service purchase, package or price on this page.
NOVA is not
- A code editor, repository or CI/CD product
- A general workflow engine or agent framework
- An ERP or CRM system
- A self-service orchestrator or an economic certifier
Delta-Lite is a paid, standalone, owner-validated workbench. It is not promoted to NOVA automatically.
Not every engagement uses every product. Explore the Product System