BP finance runtime PRD surface
Production Migration Blueprint
A phased path from validation proof to governed enterprise pilot and production scale.
Signal
Context
Policy
Agent
Evidence
Human Gate
Control
Value
Replay
Learning
Migration path
| Phase | Objective | Build scope | Environment |
|---|
| 0-30 days | Credibility foundation | Topology, inventory, evidence/replay, runtime ops, policy simulations | Demo/sandbox |
| 31-60 days | Operational pilot | P2P and O2C case flows, value attribution, process twin, tower atlas | Controlled dev/test |
| 61-90 days | Enterprise hardening | Identity, data readiness, adapter onboarding, controls, support model | Pilot readiness |
| Post-90 days | Scaled deployment | Production change gates, support runbooks, phased tower rollout | Production candidate |
Production gates
| Gate | Requirement | Decision |
|---|
| Identity | Enterprise SSO, workload identity, role and attribute policy | Required before pilot |
| Data | Approved data products, lineage, freshness, master-data readiness | Required for AL2+ |
| Integration | Adapter contract, read/write boundary, failure handling | Required for write-back |
| Governance | Agent registration, owner, risk class, policy binding, kill switch | Required for every agent |
| Evidence | Evidence completeness, replay, audit export, retention | Required for material decisions |
| Operations | SLOs, incident handling, fallback, support ownership | Required for production |
Pilot recommendation
Start with bounded P2P duplicate/missing-GR and O2C unapplied-cash flows. Keep production write-back disabled until identity, adapter, policy, evidence, and support gates are signed off.
Simulated versus production
Validation surfaces prove architecture, governance, evidence, replay, and value logic. Production requires approved enterprise connectivity, identity, data products, policy ownership, control certification, and runbooks.