External proof cockpit
The remaining 4% depends on outside proof, not more internal screens
This cockpit keeps the last Flow blockers honest: CI secrets, Kustom merchant proof, connector credentials, live KPI data and independent security review.
Decision
Ready to prove, not yet fully proven
Flow is product-ready across the core domains. The remaining work is proof collection from real infrastructure, providers and customers.
5
external lanes
96.1%
current TODO
1
pilot tenant needed
Proof lanes
What is still missing and what can be done now
CI ring proof
Missing: Staging and production smoke auth secrets.
Codex can do: Keep preflight, source-of-truth, cadence and evidence surfaces ready.
Required artifact: release-governor + release-ultimate-gate output per ring
Kustom paid proof
Missing: One real paid reference plus failure/retry/refund or adjustment proof.
Codex can do: Keep Kustom report, payment closure and reconciliation surfaces ready.
Required artifact: signed Kustom report with provider reference and admin sign-off
Connector live proof
Missing: One authorized HubSpot/helpdesk/PMS credential lane and replay evidence.
Codex can do: Keep diagnostics, replay, reconciliation and closure checklists ready.
Required artifact: connector proof run with setup, webhook replay, reconciliation and provider status
Live KPI proof
Missing: Lead, booking and paid events from real customer traffic.
Codex can do: Keep KPI cockpit, ROI closure and funnel completeness guards ready.
Required artifact: weekly KPI target export with funnel completeness and conversion proof
Security final proof
Missing: External pentest or independent security review with retest closure.
Codex can do: Keep security closure, audit, trust and public attack-surface evidence ready.
Required artifact: security review report with findings, fixes, retest and owner sign-off
Rules
No false 100%
- These blockers must remain visible because they require external systems or live customer evidence.
- Product development can continue, but release claims must reference proof state, not roadmap optimism.
- A lane moves to green only when the required artifact exists and is archived.
- The safest next go-live path is one pilot tenant with widget install, RFP/proposal, payment and connector proof.
Next real-world move
Run one pilot customer from install to paid proof
The strongest path to true 100% is a single authorized tenant where we can collect widget install, first lead, RFP/proposal, signature, payment reference, connector replay and security/access review.