Flip 360 Commission Platform
Bottom-up Status Report · WS2 · Steerco #2

WS2 · Commission Engine · bottom-up status for Steerco #2.

Compiled 17 June 2026 by Carla Oliver · PMO Director · CoSai for the Steering Committee meeting on 22 June 2026 at Wotso Sippy Downs. Steerco attendees: Mathew Punter (Founder/CEO, Flip 360), Corrina McGowan (CEO, YDT), Carla Oliver (CEO, CoSai).

Live board Workstream ops Registers Steerco papers Scoping · CRM CRM · user requirements Deal room Hardening backlog Learn (ADKAR) Framework
Source Vol 4 Ch 12 · PMO Structure · bottom-up reporting discipline  |  Vol 1 Ch 8 · Programme Governance · evidence-based PMO  |  Vol 1 Ch 10 · Future-State PMO · the PMO Control System
Overall verdict
At risk
0 done  ·  1 partial  ·  0 at-risk  ·  2 not started  ·  1 not done
Steerco
#2 · Baseline lock · vendor selection
22 June 2026 · 11:00–14:00 · Wotso Sippy Downs

1  ·  Headline · what Steerco needs to know in one paragraph

PMO Director · Carla Oliver · PMO Director · CoSai

WS2 Commission Engine is real on the CRM, rules, ledger and ABA-payout side — 50+ live routes, 9 verticals, 30 products, 9 active commission rules and a $10,700 seed ledger demonstrate the engine end-to-end. It is a sophisticated mockup on the Stripe Connect, hardware-signature and observability side. Milestone 1 (six functional guarantees demo + ADR-7 at SC#1) was not formally evidenced; Milestone 2 (Stripe Connect test mode by SC#2) cannot be met by 22 Jun 2026 because the Stripe SDK is not installed and no API keys are wired. The PMO recommends Steerco #2 (a) acknowledge the structural gap between marketing copy and runtime, (b) ratify a hardening sprint to make the copy true by SC#4, and (c) approve a re-baseline of Milestone 2 to "ABA file generation validated end-to-end + Stripe Connect integration scoped" pending vendor selection.

2  ·  Live engine metrics · pulled from D1 17 June 2026

These numbers are not narrative. They are the actual row counts in the live Cloudflare D1 database flip360-commission (6bf8957f-c714-46c7-b752-ef9b0d597d1f) at the moment this report was compiled. They will move as the engine moves. Seed data is identified inline where it is the source.

Active verticals
9
D1 query · verticals WHERE active=1
Products configured
30
D1 query · products WHERE active=1
Commission rules active
9
D1 query · commission_rules WHERE active=1
Sales pipelines
9
D1 query · pipelines WHERE active=1
Members on platform
8
D1 query · contacts WHERE contact_type=MEMBER (seed data)
Partner contacts
9
D1 query · contacts WHERE contact_type=PARTNER (seed data)
Customer contacts
23
D1 query · contacts WHERE contact_type=CUSTOMER (seed data)
Deals tracked
17
D1 query · deals (seed data)
Ledger accruals (gross)
$10,700.00
D1 query · SUM(amount_cents) FROM ledger_entries WHERE entry_type=ACCRUAL (seed data)
Causation receipts
13
D1 query · causation_receipts (seed data, placeholder signatures)
Chain events
58
D1 query · receipt_events (seed data)
Registered device keys
21
D1 query · device_keys WHERE revoked_at IS NULL (seed data, placeholder public keys)
Routes hitting D1
8 files
grep "env.DB" src/routes/ — commission, member, attribution, payouts, sweetener, architecture, community-manager, engagement
D1 migrations applied
9
ls migrations/ · 0001 through 0009

3  ·  Phase 1 milestones · evidence vs target

One section per Phase 1 milestone for this workstream. Each section names the target, surfaces the evidence that does or does not exist in the repo today, identifies the gap in plain English, names the owner and a realistic ETA, and where Steerco action is required, states the escalation ask.

Milestone 1 of 4 · W1 · SC#1

Six functional guarantees demo run for Mathew · ADR-7 ratified at first Steerco

Partial

Evidence in repo / D1 / runtime

/demo route exists. Five-minute walkthrough surface live and routable /demo
/walkthrough route exists. Interactive make-a-referral walkthrough live /walkthrough
/see-it-work route exists. Investor-facing platform proof surface live /see-it-work
/architecture six-guarantees section. Architecture doc enumerates the six functional guarantees /architecture
ADR-7 document. No /docs/adr-7 artefact in repo; no published ADR file; no countersigned record of ADR-7 ratification at SC#1
SC#1 demo recording / sign-off. No artefact in /engagement/pmo evidencing the SC#1 demo was conducted with explicit pass/fail on each of the six guarantees

Gap

The surfaces that *would* support a six-guarantees demo exist (/demo, /walkthrough, /see-it-work, /architecture). What does not exist is a formally captured demo run with Mathew signing off each guarantee against a defined acceptance test. This is a documentation gap, not a platform gap.

OwnerCarla Oliver
ETA2026-06-22
Steerco askRun a 30-minute formal six-guarantees demo at the start of Steerco #2 (already at Wotso, all parties present). Mathew signs the acceptance card live. ADR-7 drafted into /docs by 24 Jun 2026 and ratified by email.
Milestone 2 of 4 · W4 · SC#2

Stripe Connect test mode validated end-to-end · idempotency hardening complete

Not done

Evidence in repo / D1 / runtime

Stripe SDK. package.json does not contain "stripe" or any Stripe library. No npm install. No SDK code.
STRIPE_* secrets. No Cloudflare Worker secrets named STRIPE_SECRET_KEY or STRIPE_PUBLISHABLE_KEY configured
Connect onboarding flow. No route exists for partner Connect Express onboarding. No webhook handler.
ABA file rail in place (alternative). src/routes/payouts.tsx generates APCA 120-char ABA files for manual bank upload. Real, working code with SHA-256 hash anchoring. /me/payouts
Idempotency keys at schema level. commission_events.idempotency_key column exists (UNIQUE NOT NULL). 18 references in src/engine/. No runtime replay test published. /architecture

Gap

The single largest gap between marketing copy and runtime. The site references Stripe Connect heavily (faq.tsx, sweetener.tsx, architecture.tsx) as the rail that lets the platform take a 1% application_fee_amount while principal moves member-to-member. None of it is wired. The honest alternative — ABA file generation — *is* wired, tested, and produces APCA-format files. The decision in front of Steerco is whether to integrate Stripe Connect during Phase 1 (3-4 day sprint) or formally re-baseline to ABA-only for the Vertical-1 pilot and defer Stripe Connect to Phase 2.

OwnerCarla Oliver (Workstream Lead)
ETAblocked — needs Steerco #2 decision
Steerco askSteerco #2 must decide one of three paths: (a) approve a 3-4 day Stripe Connect sprint between SC#2 and SC#3 (10 working days available); (b) re-baseline the milestone to "ABA validated end-to-end + Stripe Connect scoped & estimated" and defer Connect integration to Phase 2; (c) accept the slip with no re-baseline and carry as Red RAID. The PMO recommends (a) — Stripe Connect is the rail the investor narrative depends on. Cost is 3-4 days of engineering. Air BnB, Afterpay and Uber all run on platforms with the equivalent integration — Flip 360 cannot credibly claim the same breed without it.
Milestone 3 of 4 · W8 · SC#4

Observability stack live · error-rate dashboard · payout SLA dashboard

Not started

Evidence in repo / D1 / runtime

No observability dependency. No Sentry / Datadog / Honeycomb / OpenTelemetry package in package.json
No error-rate dashboard route. No /admin/observability or equivalent surface in the repo
No payout SLA dashboard. Payouts queue at /me/payouts shows current state; no SLA tracking, no time-to-payout metric

Gap

Eight weeks away from this Steerco — still time to plan, not yet time to escalate. Recommended action at SC#2: confirm vendor choice (Sentry vs Honeycomb vs native Cloudflare Workers Analytics Engine). Cloudflare Workers Analytics Engine is the lowest-friction choice and aligns with the existing Worker runtime — recommend scoping at SC#3 and shipping by SC#4.

OwnerCarla Oliver
ETA2026-07-20
Milestone 4 of 4 · W12 · SC#6

Platform handover-ready for Phase 2 BAU operation · FY27 budget ratified for KPI lock

Not started

Evidence in repo / D1 / runtime

FY27 budget document. No /docs/fy27-budget or equivalent in the repo. To be drafted across Steercos #3-#5 per phase1Deliverable.
Investor trajectory baseline exists. ASSUMPTIONS.trajectory in src/routes/investors.tsx already encodes 1k→175k members and $240k→$42M revenue across FY27-FY31 /investors

Gap

12 weeks out, on the critical path. No escalation needed at SC#2. Carla flags at SC#2 that FY27 budget drafting will commence in W6 (post SC#3) and lock at SC#6 for Phase 2 Schedule signature. SC#6 has been brought forward by 1 week to 17 Aug to preserve the fortnightly cadence — the 14-day gap from SC#6 to G4 cutover on 31 Aug is used for sign-off paperwork.

OwnerCarla Oliver
ETA2026-08-17

4  ·  Decisions Steerco needs to make

What this report needs the Steering Committee to decide at meeting #2. Each ask is named, scoped, and carries a PMO recommendation. The Steerco paper at /engagement/pmo/steerco/2 records the disposition.

Recommendation 1 of 4
Decision D204 · Re-baseline Milestone W4·SC#2 OR approve Stripe Connect sprint

Steerco to choose: (a) 3-4 day Stripe Connect sprint between SC#2 and SC#3, (b) re-baseline to "ABA validated + Connect scoped", or (c) accept slip as Red RAID. PMO recommends (a).

Recommendation 2 of 4
Decision D205 · Ratify ADR-7 by-email after live demo at SC#2

Conduct the six-functional-guarantees demo at the start of SC#2 (Wotso, in person). Mathew signs the acceptance card live. ADR-7 drafted by 24 Jun and ratified by countersigned email by 27 Jun.

Recommendation 3 of 4
Decision D206 · Lock observability vendor decision for SC#3

Steerco to nominate the observability path — Cloudflare Workers Analytics Engine (recommended), Sentry, or Honeycomb. Decision required at SC#3 to allow SC#4 ship date.

Recommendation 4 of 4
Decision D207 · Acknowledge marketing-copy-vs-runtime delta and approve hardening sprint plan

Steerco to formally acknowledge that current marketing copy on /faq, /sweetener and /architecture references capabilities (Stripe Connect, Apple Pay-grade signatures, KPMG/EY anchoring) that are aspirational at this date. PMO to publish a "Phase 1 hardening" backlog at /engagement/pmo/backlog that tracks every claim to either evidence or a sprint, with copy scrubbed only when no sprint is committed. NEVER soften the ambition — accelerate the build so the copy becomes true.

Open Phase 1 hardening backlog

5  ·  Standard of diligence

Flip 360 is in the same breed as the tech IPOs of Air BnB, Afterpay, Uber, AirTasker, Canva, Atlassian and Zoom. The standard of diligence applied to this workstream is the standard those companies were held to at this stage of their journey — not the standard a corporate pre-revenue SaaS gets away with. Every claim in marketing copy is either evidenced today or has a sprint committed against it on the published backlog. The PMO will never soften the ambition to make the report look better — we accelerate the build so the report becomes truer.


WS2 drill-down Steerco #2 paper Live PMO board Report compiled 17 June 2026