Credit Decision Intelligence Mission Demo Script

Step-by-step validation click path for the live use case.
Launch Credit Intelligence Open Credit Committee Pack
Credit Decision Intelligence Mission Demo Script
Refreshed: 2026-07-19 03:23:30 UTC
SOURCE
bp Sphere validation click path
Scope: Step-by-step presenter guidance
POLICY
Narrative first · proof second · action third
EVIDENCE
AR exposure, payment history, counterparty hierarchy, financial statements, guarantees, trading agreements, external ratings, sanctions, commodity-price signals, geopolitical risk, board-limit policy
RECORDS
7 guided steps
ACTION
Launch Credit Decision Mission
Validation Click Script
Credit Decision Intelligence Mission
Prove that credit decisions are runtime-generated from signal, context, evidence, policy, agent execution, human approval, action, replay, and learning.
Audience
Credit analyst, credit committee, CFO, commercial lead
Duration
5-6 minutes
Default role
operator
Live launch
Launch Credit Decision Mission
Back To Use Case Introduction Launch Credit Decision Mission View Runtime Payload

Step-By-Step Click Script

1
Open the launch page
Click/ui/use-case-launch?case=credit_intelligence
What to say
Frame this as a Credit Decision Mission powered by bp Sphere Runtime, not a credit dashboard.
What proof to land on
Business Problem and counterparty-specific context.
2
Review the credit operating model
ClickStay on the launch page and point to Customer Dossier, Consolidated Exposure View, and Scenario Intelligence
What to say
Tell the room this combines customer context, evidence, exposure, risk, policy, and monitoring.
What proof to land on
Customer dossier, exposure, scenarios, and controlled truth sources.
3
Launch the live mission
ClickLaunch Credit Decision Mission
What to say
Open the runtime mission surface after the room understands the trust contract.
What proof to land on
KPIs, signals, watchlist, agent timeline, and decision formation load from one runtime payload.
4
Open the critical signal
ClickOpen Counterparty Drawer on Etihad Airways
What to say
Start with a real credit event: collateral expires in 9 days while exposure remains $30M.
What proof to land on
Summary, exposure, collateral, confidence, and recommendation.
5
Show evidence and policy
ClickUse Evidence and Policy tabs in the drawer
What to say
Prove the recommendation is grounded in source documents and policy thresholds.
What proof to land on
Guarantee, SAP credit master, rating report, approval memo, UC-13, AOM-08.
6
Show agent execution and replay
ClickUse Agents and Replay tabs
What to say
Show exactly which agents participated and how the decision can be reconstructed later.
What proof to land on
Agent execution timeline and replay hashes.
7
Close with governed action and learning
ClickUse Actions tab and Learning Runtime
What to say
Show the platform does not stop at recommendations; it creates governed action requests and captures learning.
What proof to land on
ActionRequest, approval chain, execution record, and learning outcomes.

How To Use This In The Room

  • Start on the introduction page, not the live workspace.
  • Use the script to control the order: business problem, trust model, live proof, then action.
  • Spend most of the time on source-backed evidence rather than UI chrome.
  • If the room asks a skeptical question early, jump directly to the step that answers it.
Presenter note:
The recommendation is not the product. The product is the governed combination of context, evidence, policy, impact, human judgment, and memory.