01 · Hippo · Context Fabric
Can you still explain why the enterprise made that decision?
The question Hippo answersWhen someone challenges an assumption or a decision months later, can the enterprise still explain what it relied on, who decided, what changed and what evidence exists?
Hippo is the Context Fabric of the PurpleAI product system. It keeps the reasoning of a transformation attached to it: the evidence and where it came from, the assumptions, the decisions and who made them, and every version since. It explains decisions; it does not make them.
- What gets lost
- The reasons leave with the peopleAssumptions behind a business case live in spreadsheets and slide notes, and go when people move on.
- A challenged number has no trailMonths later, nobody can say where a figure came from, what depended on it or what was built because of it.
- Every programme starts againThe next programme rediscovers what the last one already knew.
02 · What Hippo retains
Keep the reason with the decision, not in someone’s memory.
Every item Hippo keeps carries its origin, its status, the decision that relies on it, an owner and a version.
An industry pattern stays a prior, a stated belief stays an assertion and an assumption stays an assumption. A recorded gap is still a gap: Hippo keeps it visible, it does not fill it.
Loading the selected Hippo example…
Records behind one decision Hypothetical
Loading process example…Inspecting one record Where did this come from?
Loading process example…Loading process example…Kept apart, never merged
- Industry prior
- Organisational assertion
- Human evidence
- System record
- Economic assumption
- Finance-reviewed input
- Leadership decision
- Runtime fact · if a change runs
- Gap · kept open
A recorded gap is still a gap. Hippo keeps the record; it does not repair the evidence.
Follow a decision through change03 · Lineage over time
Follow what was decided, what changed and what followed.
Each product owns its own decision. Hippo keeps the thread between them, so a question asked today can be traced back to its source.
Later steps exist only when the earlier decision allowed them. Not every engagement uses every product, and nothing moves on automatically.
Hippo · Context FabricKeeps the thread, the reasons and every version between them
The record follows the decision, including the decisions that stop.
See what the enterprise can retrieve04 · Knowledge when you need it
The answer should not depend on who is still in the room.
When an authorised colleague asks about a process, programme or transformation decision, Hippo is designed to bring back the reasoning: what was agreed, who decided, what evidence it relied on and what changed.
Keep the answer connected to its sources, version and permissions, so teams spend less time tracking down who remembers the decision.
Other questions people with access could ask
Loading process example…Examples only. Each person sees answers drawn from the records they are permitted to see. Access could be offered through authorised enterprise workspaces or approved collaboration channels, subject to integration and access controls.
Hippo keepsFrom Cortex, the mandate, the industry prior used, the evidence and gaps, and the Qualified Process Case. From Delta, each version of the economic case and its assumptions. From leadership, the decision and its reasons. From NOVA, where a change is approved, the AI-Native Process Contract, release decisions and runtime evidence.
Hippo gives backThe source and status of each figure and finding; decision history with what it relied on; what changed, when and why; and the context the next decision starts from.
Customer safeguards Hippo is designed for
Your tenant, your contextDesigned for each customer’s transformation records to stay within its own tenant boundary, separate from other customers’ context.
Only authorised answersGoverned access is intended to respect each person’s permitted processes, records and responsibilities, with answers tied to sources, status and version.
Portable by designCustomer-authorised export is part of Hippo’s product direction. When leaving PurpleAI, the customer may choose an agreed deletion or restricted archive path, subject to applicable retention obligations.
If a customer leaves
- Authorise the request
- Export and verify portable context
- Choose secure purge or an agreed restricted archive
An export is not itself an instruction to delete. The customer chooses what happens next, and lawful retention obligations still apply.
Illustrative product experience. Live conversational access, tenant-security controls and migration/exit functions require Engineering and Security verification before launch.
The knowledge stays with the decision. Access stays with the right people. The context can travel with the customer.
Understand where Hippo fits05 · Where Hippo fits
Keep the context. Let each product own its decision.
Hippo sits beside the decisions, not above them. It keeps what each one relied on, and changes none of them.
Who owns each decision, and what Hippo keeps from it
| Owner | Owns the decision | Hippo keeps |
|---|---|---|
| CortexEnterprise Intelligence | Whether a process qualifies, on evidence | The mandate, the industry prior used, the evidence, the gaps and the Qualified Process Case |
| Enterprise DeltaEconomic Intelligence | The economic case for a qualified process | Each version of the case, its assumptions and their sources |
| LeadershipDecision authority | Approve, change or decline | The decision, its reasons and what it relied on |
| NOVAGoverned Execution | Building and running an approved change | The contract, release decisions and runtime evidence, only where a change runs |
Hippo · Context FabricKeeps the thread across all four. It does not discover or verify evidence, calculate economics, approve, build or run, or fill a gap.
Within an enterprise transformation
Discuss where Hippo fits in your transformation
Hippo is scoped with PurpleAI as part of an enterprise engagement. There is no self-service purchase, package or price on this page.
Hippo is not
- A company-wide ontology or general knowledge graph
- A document vault or a data lake
- Master data management or FinOps
Delta-Lite is a paid, standalone, owner-validated workbench. Its results do not transfer automatically into Hippo.
Not every engagement uses every product. Explore the Product System