bp Sphere

Introduction · what it is
Executive narrative Business-first framing 12 registered runtime seams bp Sphere

bp Sphere is the operating layer for enterprise understanding, judgment, execution, and learning.

bp Sphere does not replace SAP, Ariba, ServiceNow, Foundry, Databricks, AWS, Azure, or hyperscaler AI. It connects them, understands them, reasons across them, governs decisions across them, and progressively turns fragmented enterprise work into replayable, evidence-backed operating judgment.

Open By Function Open Evolution Roadmap Realizing at bp Open Workshop Story
Strategic role
Enterprise judgment layer
Primary output
Governed decisions
What it adds
Context, evidence, policy, memory, orchestration
What it avoids
Another siloed AI platform

How to use this page

  • Use Overview and Why for first-time orientation.
  • Use How It Thinks and Operating Model when the team asks how Sphere actually works.
  • Use Architecture and Technology + Data when the room asks how this fits with SAP, Ariba, Foundry, Databricks, AWS, and Azure.
  • Use By Function and Functional Packs to connect the platform story to P2P, O2C, R2R, FP&A, Treasury, and ST&S.
  • Use Roadmap to explain why bp should invest over time even with strong existing platforms.

Why bp Sphere exists

The problem is not a lack of enterprise systems. The problem is that those systems do not create a unified judgment, execution, and learning layer across the enterprise.

What existing systems do well

Store transactions, documents, approvals, balances, workflows, and analytics.

What bp leaders still need

Why it happened, what should happen next, what policy applies, what evidence matters, and who should act now.

Why invest now

Because SAP, Ariba, ServiceNow, Foundry, Databricks, Claude, and hyperscaler services do not provide one enterprise layer for judgment, orchestration, and learning.

What existing systems answer vs what bp Sphere answers

Existing systems answerbp Sphere answers
What happened?Why did it happen and what should happen next?
What was posted or approved?What policy should govern the next action?
Where is the document?What evidence supports the decision?
What is the workflow state?Which team, agent, or executive should intervene?
What was the result?What should the enterprise learn and reuse?

Latest Runtime Capability Update

Every Introduction tab is now grounded in the same current runtime baseline: Continuous Finance Command Center, Continuous Close digital twin, CLI runtime proof, provenance badges, 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.

How to read “Status”: “Surface available” and “Endpoint available” mean the named surface or endpoint is implemented and registered in this build — they are not real-time health probes. Open any surface for its own ● live / ◐ seeded provenance badge; production SOR connectivity stays fail-closed until BP credentials and feeds are supplied.

Experience Orchestration Layer

Surface available - Shared decision objects render across desktop, mobile, and chat surfaces.

/ui/mission/p2p, /ui/mobile-cockpit, /ui/enterprise-chat

Governed Chat Interface

Surface available - Chat resolves role, mission, case, evidence, policy, action contract, replay, and feedback.

/ui/enterprise-chat

Workforce Intelligence Integration Fabric

Surface available - Assistant registry, connector packages, certification, compliance mappings, identity resolution, failover drills, and workforce coordination APIs.

/ui/workforce-intelligence-fabric, /ui/assistant-operations-center

Token Economy Control Plane

Surface available - LLM calls are routed, cached, denied, downgraded, or escalated before spend occurs; token value is attributed to decisions.

/ui/ai-cost-usage, /api/iaf/decision-intelligence/token-economy/decision

Guardrail Policy Engine

Surface available - Policy evaluation fails closed in production posture; non-fail-closed failures route to escalation instead of silent execution.

/ui/policy-registry, /ui/control-plane

Decision Replay + LLM Determinism

Surface available - Execution seed, prompt/context hash, evidence hash, policy version, and replay records are persisted and validated.

/ui/decision-journey, /ui/single-decision-audit, /ui/decision-replay-studio

Continuous Finance Runtime

The hero story is now “if BP closed the books right now, what would the financial statements look like?” The runtime combines actuals, forecast accruals, provisions, reconciliations, controls, evidence, confidence, and replay.

Open Continuous Close intro

CLI Proof Path

Architects can run bp-now, bp-close-now, bp-financial-position, bp-digital-twin, bp-runtime, and bp-provenance to prove the runtime without the UI.

The CLI is intentionally self-disclosing: the runtime query is live; the workshop baseline is seeded and marked.

Provenance Badges

● live API query · ◐ seeded BP-shaped baseline · ◇ model/estimate with basis · ◆ deterministic policy/replay path.

Production SOR connectivity remains fail-closed until BP credentials and feeds are supplied.