Enterprise context and ontology

Context Studio

Fast context operating view for bp source systems, finance objects, event catalogs, evidence contracts, policy bindings, and agent-ready business meaning. Formerly CREST Context Studio.

ObjectsSupplier, contract, PO, invoice, payment, journal, asset, project, cost center, policy, control, person

RelationshipsSupplier to contract, contract to PO, PO to invoice, invoice to payment, policy to control

EventsInvoice blocked, journal posted, order created, payment received, exposure changed, forecast moved

GovernanceOwner, steward, source system, quality score, freshness, lineage, and replay contract

CoverageObject, relationship, event, policy, evidence, and decision coverage measured by domain

ConfidenceFreshness, completeness, source agreement, lineage, and evidence quality combined into one operating score

Context Operating System Experience

Coverage dimension	Measured scope	Score	Owner
Object coverage	Supplier, invoice, PO, payment, journal, policy, control, asset	92%	Business steward
Relationship coverage	Supplier -> contract -> PO -> invoice -> payment links	87%	Ontology steward
Event coverage	Invoice blocked, journal posted, payment released, forecast moved	84%	Event steward
Policy coverage	Authority, SoD, tolerance, evidence, and write-back rules	91%	Control owner
Evidence coverage	Source records, documents, lineage, hashes, and replay pointers	89%	Evidence steward
Decision coverage	Named decision types with owner, alternatives, outcome, and replay	78%	Decision owner

Confidence component	Rule	Weight
Freshness	Critical sources refreshed inside SLA	22%
Completeness	Required fields and relationships present	24%
Source agreement	SAP, Ariba, Databricks, and document evidence do not conflict	20%
Lineage	Source system, timestamp, owner, hash, and replay path attached	18%
Evidence quality	Evidence pack is complete, readable, and policy-aligned	16%

Finding	ContextOps issue	Action	Owner	Status
CTX-FIN-041	Duplicate supplier relationship detected	Assign steward	Procurement data steward	Open
CTX-FIN-052	Invoice-to-PO relationship confidence improved to 94%	Approve finding	P2P control owner	Ready
CTX-FIN-063	Conflicting payment term from SAP and contract extract	Reject finding	ContextOps analyst	Blocked
CTX-FIN-074	Finance Core Pack v1.4 passed coverage gate	Promote context pack	Context council	Ready
CTX-FIN-085	Supplier risk node breached freshness SLA	Mark stale	Supplier master owner	Aging

Decision mining signal	Pattern	Operational use
Most common approval path	Analyst -> Supervisor -> Controller	37% of high-value P2P holds
Most common hold reason	Missing receipt or duplicate candidate	42% of open exceptions
Override hotspot	Payment timing overrides	9 overrides in last 30 days
Reusable pattern	Supplier resubmission after delayed acknowledgement	Promote after 3 more replay-confirmed outcomes
Policy friction	FIN-P2P-DUP-04 causes repeat supervisor review	Candidate for threshold simulation

Runtime Loaded Context Packs

Status	Objects	Relationships	Events	Actions
live	580	272	393	241

Loaded objects

asset_lifecycle.asset, Asset, asset_lifecycle.equipment, Equipment, Failuremode, asset_lifecycle.failuremode, Inspection, asset_lifecycle.inspection

Loaded relationships

asset_lifecycle.asset__relates_to__asset_lifecycle.equipment, carbon_sustainability.emissionsource__relates_to__carbon_sustainability.emissionevent, downstream.refinery__contains__downstream.refinery_unit, downstream.refinery__processes__downstream.crude, downstream.refinery_unit__produces__downstream.product, downstream.product__transported_via__downstream.pipeline, downstream.pipeline__delivers_to__downstream.terminal, downstream.terminal__stores__downstream.storage_tank

Loaded events

equipment_health_drop, sensor_threshold_breach, failure_pattern_detected, vibration_threshold_breach, inspection_due, compliance_window_at_risk, work_order_backlog_growth, critical_asset_work_order_open

Source of truth

OntologyFabric domain contract. This prevents the registry from drifting from what the runtime actually loaded.

1 · Registry

Show enterprise context assets: objects, relationships, policies, events, decisions, evidence.

2 · Graph

Open Supplier -> Contract -> PO -> Invoice -> Payment -> Decision path.

3 · Coverage

Show whether the context slice is complete enough for governed decisions.

4 · Confidence

Explain freshness, completeness, source agreement, lineage, and evidence quality.

5 · ContextOps

Operate findings through assign, approve, reject, promote, and stale-state actions.

6 · Replay

Prove the decision used the context package and show what changed afterward.

Latest Runtime Capability Update

This page is evaluated against the current runtime baseline: governed chat, WIIF assistant portability, Token Economy controls, fail-closed policy enforcement, deterministic replay, signed evidence, runtime adoption audit, skill learning promotion, autonomy demotion enforcement, case-state propagation, and observability readiness.

Evidence-backed answersPolicy before actionReplay-ready decisionsValue attributionAssistant portabilityRuntime observability

Compact-SOR proof anchor for BP validation pages

INV-LIVE-DUP-1778594510 · OceanFloor Subsea Services Ltd · £2.8M

Policy FIN-P2P-DUP-04 · Evidence EP-P2P-OCEANFLOOR-LIVE · PO PO-100421 · $2.3M protected.

Latest Runtime Capability Update: governed chat, WIIF assistant portability, Token Economy controls, fail-closed policy, deterministic replay, signed evidence, runtime adoption audit, case-state propagation, and observability readiness.

Open P2P case Evidence pack Replay

Minimum viable context

Start with one bounded slice instead of waiting for a full enterprise ontology.

Duplicate invoiceJournal anomalyCredit exposureForecast risk

Platform surfaces

The operating entrypoint links the Canonical Registry, Context Graph, Decision Records, Evidence Vault, ContextOps Center, and Context Engineering Brief into one context operating view.

Canonical RegistryContext GraphDecision RecordsEvidence VaultContextOps CenterContext Engineering Brief

ContextOps actions

Stewards can assign findings, approve discovered context, reject weak context, promote certified packs, and mark stale nodes before agents consume them.

Assign stewardApprove findingReject findingPromote context packMark stale

Decision mining

Replay and decision memory expose common approval paths, exception reasons, override hotspots, reusable patterns, and policy friction.

Approval pathsHold reasonsOverride hotspotsReusable patternsPolicy friction

Finance dimensions

Business unit, legal entity, cost center, profit center, account, supplier, counterparty, asset, project.

BULegal entityCost centerAccount

Source access

Context can come directly from SAP/Ariba APIs or from curated Databricks products depending on bp readiness.

APIEventExtractData product

Agent consumption

Agents receive resolved business objects, not raw tables.

Context packEvidence contractPolicy bindingDecision owner

Open full studioLive context renderer ContextOps CenterOperate context drift and findings Coverage MethodologyCoverage scoring model Runtime architectureContext layer Agent inventoryAgent data needs Technology mappingSOR mapping

Provenance: validation-safe first-paint view backed by BP Sphere platform contracts and linked live proof surfaces. Refreshed 2026-07-19 09:20 UTC. Use the linked pages to inspect source records, policies, agent dependencies, evidence, replay, cost, and decision history.