Foundation Control Intelligence
Autonomous Control Intelligence
Transform finance controls from detective and sampled testing into continuously operating preventive intelligence services.
Core decision question
Should this transaction be allowed to proceed?
Every signal, context package, evidence pack, policy result, recommendation, human approval, action, replay, and learning artifact should serve this question.
North Star KPIs
Control effectivenessControl automationFraud reductionAudit effort reductionIssue prevention rateAgent workforce
Control Intelligence AgentPolicy Intelligence AgentAuthority Intelligence AgentEvidence Intelligence AgentFraud Intelligence AgentAudit Intelligence AgentEnterprise integrations
SAP S/4HANABlackLineAribaMaximoIdentity systemsApproval systemsDocument repositoriesPolicy repositoriesFuture UDP enterprise graphMonitored domains
Invoice ControlsJournal ControlsApproval ControlsVendor ControlsPayment ControlsAccess ControlsTrading ControlsTreasury ControlsTax ControlsCompliance ControlsReference signal ticker
Signal visibility must be more than the word signal. Each mission shows reference signal counts, severity, scenario REF-TICK ID, and current blocked/recommended state. These are scenario proof shapes until connected to live traversal.
Reference signal generated from the scenario library; REF-TICK IDs show the expected production trace shape and are not attested live events.
9191 reference control signals / scenario
1212 preventive blocks
ScenarioScenario event REF-TICK-30577 at 14:23
33 override requests
Reference signals and recommended responses
| Signal | Source | Impact | Recommended response |
|---|---|---|---|
| Duplicate invoice enters system | SAP + Ariba | $482K payment risk blocked | Block and notify controller |
| Journal above authority threshold | SAP S/4 | SOX evidence required | Escalate for controller approval |
| Supplier bank change before payment | Supplier master | Fraud risk elevated | Hold payment and verify bank details |
Demo sequence
- Duplicate invoice enters system
- Agent detects duplicate
- Policy evaluated
- Evidence retrieved
- Payment blocked
- Controller notified
- Replay generated
Source-system traceability for major numbers
Every major value is tied to a source system, API object, data product, or source transaction. This answers where the number came from before BP asks.
Context pack: business unit: Group Finance · cost center: CC-1042 · entity code: BP-GROUP · owner: mission runtime.
| Number / metric | Source system or data product | Record / API object | Business context |
|---|---|---|---|
| $482K duplicate block | SAP S/4HANA + Ariba invoice | invoice=INV-LIVE-DUP-1778594510 | Control: P2P duplicate payment |
| Authority breach | Identity system + approval matrix | approver=AAD-CTRL-447 | Policy: FIN-DOA-2026-07 |
| SoD violation | SAP workflow + IAM logs | user=AAD-REQ-118 | Control: SOX-SOD-014 |
Evidence, policy, replay, learning, and action artifacts
Decision memory
| Runtime artifact | Identifier | Credibility proof |
|---|---|---|
| Evidence pack | EP-CTL-30577 | data-evidence="pack" · source records and supporting documents |
| Policy ID | FIN-DOA-2026-07 | Policy runtime gate evaluated before recommendation |
| Replay ID | REPLAY-CTL-30577 | Replay available from signal through human judgment and action |
| Learning | patterns learned: 5 | Decision memory updates after accepted/rejected outcome |
| Action payload | Block payment / escalate approver | Next action: governed execution after approval limit $500K and human override check |
Alternative actions table
Alternative actions table. This is the concrete recommendation surface: bp Sphere shows what it recommends, what it rejected, the expected value, the risk, and the action path.
| Alternative action | Confidence | Expected value / impact | Risk / tradeoff | Action path |
|---|---|---|---|---|
| Allow transaction | 18% | No process delay | $482K duplicate/fraud exposure | Denied by control gate |
| Block transaction | 96% | $482K prevented | Supplier validation required | Payment hold |
| Escalate authority | 89% | Policy-compliant release path | Supervisor queue load | Alternate approver identified |
| Request evidence | 83% | Audit-ready support | Cycle time +4h | Evidence pack request |
Workshop challenge proof
| Challenge | Visible answer |
|---|---|
| Authority control | FIN-DOA-2026-07 checks approval threshold and identifies alternate approver when authority is exceeded. |
| Segregation control | SOX-SOD-014 checks creator/approver separation before release. |
| Duplicate control | P2P duplicate payment control blocks invoice INV-LIVE-DUP-1778594510 before payment release. |
Runtime injection console
Use these controls during the workshop to show the mission changing state. Injection creates a named runtime event, updates mission KPI/readiness, adds a replay row, and opens the trace from signal to learning.
Mission KPI
Control effectiveness
Awaiting scenario injection.
Mission readiness
Baseline
No injected blockers or opportunities yet.
Latest replay event
None
Click an injection below to create a replayable runtime event.
| Time | Event | Scenario | Decision impact |
|---|---|---|---|
| --:--:-- | Waiting | No scenario injected | No mission state change |
Decision portfolio
| Decision | Impact | Owner | Status |
|---|---|---|---|
| Block duplicate invoice | $482K prevented | P2P Supervisor | Prevented |
| Hold supplier bank update | $2.1M payment run protected | Controls Lead | Human-controlled |
| Escalate material journal | $5.2M close risk | Controller | Evidence required |
Vertical operating-model audit
This validates that the mission is useful from frontline work through enterprise steering: Agent Runtime → Analyst → Supervisor → Function Leader/Controller → FB&T Leader → CFO.
| Role layer | What this layer can do | Executive credibility proof |
|---|---|---|
| Agent Runtime | Control, policy, authority, evidence, fraud, and audit agents evaluate transactions before release. | Preventive-control trace with source transaction, policy, evidence, action, and replay. |
| Analyst | See control failure, understand cause, and resolve or escalate. | Can explain what failed and what action is allowed. |
| Supervisor | See recurring failures, analyst workload, and risk trends. | Can manage teams and unresolved control work. |
| Function Leader / Control Manager | Review effectiveness, control trends, failing controls, and remediation actions. | Can see which controls are weakening and why. |
| FB&T Leader | Understand finance control health, audit exposure, and mission-level control posture. | Can identify where intervention is needed across finance operations. |
| CFO | Understand enterprise control posture and regulatory exposure. | Can see issues prevented, fraud exposure avoided, and audit-readiness impact. |
Executive credibility scenarios
These are the scenarios BP can challenge live. The mission must show signal, context, evidence, policy, decision, action, replay, learning, and enterprise impact for each.
| Scenario | Inject | Expected runtime proof | Action |
|---|---|---|---|
| Duplicate invoice | Known duplicate enters system | Signal, evidence, policy, block recommendation, audit trail, and replay are visible. | |
| Authority violation | Approver exceeds authority | Control triggers, escalation generated, and alternative approver identified. | |
| Segregation violation | Creator and approver same user | Control block, policy reference, and evidence lineage are generated. |
12+ dimension BP credibility audit
| Dimension | Visible proof requirement | This mission's answer |
|---|---|---|
| Signal | Business event or market movement is visible and linked to a mission decision. | Duplicate invoice enters system · Scenario event REF-TICK-30577 at 14:23 |
| Context | Entity, business unit, owner, system object, policy domain, and history are resolved. | Resolved through enterprise context graph: owner, system object, business unit, history, and policy domain. |
| Evidence | Source records, documents, approvals, and source-system snapshots are inspectable. | Evidence pack includes source system record, curated data snapshot, policy reference, and supporting document where applicable. |
| Policy | Authority, control, risk, accounting, tax, treasury, or investment policies are referenced. | Policy/runtime gate is evaluated before recommendation or action. |
| Decision | The mission produces a named decision object, not just a metric or chart. | Block duplicate invoice |
| Recommendation | Recommended response and alternatives are shown with impact. | Allow transaction · confidence 18% · impact No process delay |
| Human Override | Human approval, rejection, override, or escalation path is explicit. | Approval, rejection, override reason, and escalation owner are retained in replay. |
| Action | Action payload is traceable to workflow, system update, notification, hold, hedge, or approval. | Prevented |
| Replay | Event, context, evidence, policy, recommendation, human judgment, action, and outcome can be replayed. | Replay captures signal, context, evidence, policy, agent output, human judgment, action, outcome, and learning. |
| Learning | Accepted/rejected outcomes are captured as future pattern memory. | Outcome becomes pattern memory after human decision and realized impact are known. |
| Business Impact | Financial, risk, cash, control, or value impact is quantified. | $482K prevented |
| Enterprise Integration | Systems of record, data products, APIs, and future UDP context layer are named. | SAP S/4HANA · BlackLine · Ariba · Maximo · example: SAP S/4HANA + Ariba invoice |
| Source Drill-down | Users can drill from decision to source transaction, document, or curated data product. | Source drill-down points to SOR/API record, Databricks/UDP data product, document, or market feed behind the decision. |
| Confidence | The decision carries confidence and uncertainty drivers. | Confidence is shown in decision formation and decomposed into data freshness, evidence completeness, policy clarity, and model uncertainty. |
| Alternatives | At least two alternative actions or scenarios are available. | Allow transaction | Block transaction | Escalate authority |
| Audit Trail | Every material step is retained with timestamp, actor/agent, evidence, and policy result. | Timestamped audit trail spans agent, human, policy, evidence, and action events. |
| Executive Narrative | The mission can produce an executive answer: what happened, why, what to do, and expected outcome. | Narrative answers what happened, why, recommended action, value, risk, and next owner. |
| Mission KPI | A mission-level KPI changes when the scenario changes. | Control effectiveness |
| Readiness | Readiness or confidence updates when blockers, policies, or evidence status change. | Mission readiness/confidence updates when signals, evidence, policies, or blockers change. |
| Enterprise Impact | The mission shows enterprise-level consequence beyond one transaction. | Should this transaction be allowed to proceed? |
Runtime architecture
SignalBusiness event, market movement, policy breach, or performance variance.
ContextEntity, asset, customer, project, policy, historical pattern, and owner resolution.
Evidence + PolicySource records, documents, controls, authority, and data-quality checks.
Decision + ActionAlternatives, confidence, financial impact, owner, action payload, and approval path.
Replay + LearningFull trace, outcome, accepted/rejected recommendation, and pattern memory.