Legal entitlement (done at agreement signing) S2 fires

Back on 2024-11-03, Jane signed her Affiliate agreement on /legal/affiliate-2024. Pine Lawyers’ signing flow created commission_rules row R-7, stamped with the execution ID linking back to her signed PDF. Rule R-7: 8% commission, 50/50 split, 14-day cooling-off, 90-day lifecycle.

Jane signs H1 INTENT_SIGNED (the deal begins) S1 + Engine

Jane opens the Flip360 app on her phone. Declares: "I am referring my client Sarah Chen at Acme Pty Ltd to Member B for advisory work." Signs with her device-bound key (Secure Enclave). S1 fires: Chain creates a new causation_receipt + writes H1 event signed by Jane’s key. Engine consumes: creates the deals row at stage H1_INTENT. No commission yet — H1 is intent, not outcome.

Sarah signs H2 ACKNOWLEDGED S1 + Engine

Member B reaches out. Sarah confirms by signing on her device: "I confirm I am engaging Member B because of Jane’s referral." S1 fires: Chain adds H2, hash-linked to H1. Engine consumes: advances deal to H2_ACK.

Member B signs H3a INTAKE_CONFIRMED S1 + Engine

Member B accepts: "I will deliver the advisory work for Sarah and honour the commission split with Jane per rule R-7." S1 fires: Chain adds H3a, hash-linked to H2. Engine consumes: advances to H3a_INTAKE. Still no commission — work isn’t done.

Member B signs H3b SETTLED S1 + Engine

Work completes. Member B signs: "The underlying deal converted on 2025-09-15 for value $120,000." The signed payload carries the deal value. S1 fires: Chain adds H3b. Engine consumes: advances to H3b_SETTLED. Engine now has enough to compute commission — but waits for the customer’s H4.

Sarah signs H4 OUTCOME_CONFIRMED (the trigger) S1 fires the engine

Sarah signs the final handshake: "I confirm Member B did the work, and Jane should be paid for the referral." S1 fires: Chain adds H4. Chain now complete (5 events, 4 handshakes). Engine consumes H4 and fires commission: looks up rule R-7, computes $120,000 × 8% = $9,600, splits $4,800 Jane + $4,800 Member B, sets cooling-off 14d, advances deal to H4_OUTCOME.

Engine writes the ledger (the ONE money write) Engine → Ledger

Three rows to ledger_entries: Jane $4,800 ACCRUAL COOLING_OFF, Member B $4,800 ACCRUAL COOLING_OFF, platform fee $0. One commission_events row with UNIQUE idempotency key. Each ledger entry’s receipt_id points to the H4 chain event.

Chain block sealing S1 tail

H4 event + 2 ledger-entry-receipt links sealed into chain block B-0009. Block hash computed, queued for next external witness anchoring. Court-ready badge appears on any observer surface (integrity ≥ 95%).

Accounting picks it up S3 fires

Posting service reads the 2 ACCRUAL entries. Writes 2 journal entries: DR 6000 Commission Expense $4,800 / CR 2100 Commission Payable $4,800 (×2). P&L: expense +$9,600. Balance Sheet: liability +$9,600.

BI picks it up (next snapshot) S4 fires

Variance service includes $9,600 in actuals for KPI commission_paid_cents for Q1. Updates RAG status on /crm/bi.

Cascade rolls it up S5 fires

commission_paid_pct leaf attainment updated. Weighted roll-up to "revenue $42M" strategic KPI on /crm/cascade.

Observer surfaces render S6 fires

Jane opens /me: new entry, "Cooling-off — eligible 2025-10-21," chain visualisation of all 5 handshakes, Dispute button. Carla opens /crm/deals/14: same chain visualisation, same ledger entries, same court-ready badge. Carla did not advance this deal. Sarah’s H4 signature did. Carla’s surface is purely informational.

Cooling-off completes Engine state

14 days later, lifecycle cron flips both entries from COOLING_OFF → ELIGIBLE. New receipt_events row records the state transition (signed by platform scheduled-task key).

Payout S8 fires

Carla runs payout batch. Engine selects ELIGIBLE entries. RCTI-2025-10-0042 for Jane, RCTI-2025-10-0043 for Member B. ABA file + SHA-256. Two PAYMENT ledger entries written back. Accounting picks up: DR 2100 / CR 1000 Bank $4,800 (×2). Liability –$9,600. Bank –$9,600. Jane + Member B see "Paid" on /me.