Runtime status
live
bp Industry Context Pack Registry - bp Sphere
Reusable context packs instead of tenant-only one-offs
ScaleMarketplaceProductization
Industry Context Pack Registry
This surface closes the gap between tenant-specific workshop content and a scalable platform product. It shows how bp-specific finance and upstream context can extend reusable industry packs instead of forking the platform.
Objects loaded
1,155
Relationships
394
Events
901
Pack model
The platform owns reusable packs. bp extends them. That keeps the Context Studio product model clean while still allowing bp-specific operating detail where it matters.
| Core Finance Pack | Supplier, Invoice, Payment, Cash, Policy |
|---|---|
| Energy Operations Pack | Work Order, Maintenance Plan, Asset, Spec |
| Credit Intelligence Pack | Counterparty, Exposure, Market Signal |
| bp extension: Upstream AP | Milestones, waivers, AFE overlays |
| bp extension: T&S Credit | Commodity stress + counterparty posture |
| Lifecycle | Draft → certified → promoted |
Why this scales
Without packs, every workshop becomes a tenant-only customization story. With packs, the message becomes: the same context substrate can be reused across finance, procurement, supply chain, and operations.
| Certification | Platform certification + tenant overlay review |
|---|---|
| Versioning | SemVer + steward approval |
| Replay compatibility | Required |
| Coverage scoring | Per-pack and per-domain |
| Marketplace view | Shared + tenant extension |
| Cross-tenant | Reusable base context pack with tenant-governed extensions |
| Promotion rule | No production use without certified pack |
Loaded runtime packs
Live runtime
| BP Finance Runtime Contract | loaded | 1,155 objects · 394 relationships · 901 events |
|---|
Objects loaded
threat, Threat, vulnerability, Vulnerability, Control, control, RiskFinding, risk_finding
Relationships loaded
downstream.refinery__has_many__downstream.refinery_unit, downstream.refinery__produces__downstream.product_batch, downstream.refinery_unit__contains__downstream.process_stream, downstream.product_batch__tested_against__downstream.quality_spec, downstream.product_batch__follows__downstream.blend_recipe, downstream.product_batch__shipped_via__downstream.shipment, downstream.terminal__has_many__downstream.tank, downstream.terminal__receives__downstream.shipment
Events loaded
security_incident_lifecycle, vulnerability_lifecycle, identity_event_lifecycle, control_test_lifecycle, exposure_lifecycle, threat_lifecycle, control_lifecycle, risk_finding_lifecycle
Why this matters
It converts the workshop from ‘custom demo for bp’ into ‘bp using a reusable enterprise context product model.’
Workshop proof points
Use this when asked how much of the solution is reusable. The answer becomes: the packs, coverage model, and discovery engine are shared; bp adds governed extensions.