Five questions cut across the entire system. Each traces through multiple membranes. Follow a vein to understand how one concern ripples through the architecture.

Payment Processing
payment-loop → invoice-truth → dunning-brain

Users get entitlements for free because the system commits state before payment confirms. A solution isn't possible without breaking some eggs — every downstream system has to adapt.

State Consistency
drift-reconciliation → dunning-brain

How do six stores converge to one truth? The recompute engine reads all stores and computes correct state. The brain consumes that unified view to make decisions.

Platform Unification
payment-loop → registrar-uc → paypal-topology

How do bespoke product flows become one platform? Registrar moves onto unified checkout. PayPal is the exception that proves the rule — dual-processor topology.

Customer Clarity
invoice-truth → customer-segment → dunning-brain

What does the customer actually owe, and how do we tell them? Credit notes make invoices truthful. Account type determines the response when payment fails.

Billing Clock
subscription-lifecycle → payment-loop → invoice-truth

Who decides when things get billed? Stripe owns the clock today. Taking it over means controlling when invoices generate, when charges fire, when periods start.

Three membranes sit where multiple veins converge. Start with any hub and follow the connections outward.

3 veins converge

Users get entitlements for free because state commits before payment confirms. Fixing this breaks eggs everywhere — every downstream system adapts to the new ordering.

3 veins converge

Where ordering correctness meets state consistency meets customer clarity. Reads all six stores, decides based on confirmed payment state, routes per account type.

3 veins converge

Where payment ordering becomes visible to the customer. Credit notes make the debt truthful. The invoice lifecycle is the unit of collection.

Strict dependency chain. Each act unlocks the next.

Foundation Correction Expansion
Act 1: Foundation
No dependencies — ships first

Prove that confirm-before-commit works and that six stores can be read as one. These two capabilities gate everything else.

Act 2: Correction
Requires Foundation

Make the invoice tell the truth and give dunning a single decision point. These require the foundation but not each other.

Act 3: Expansion
Requires Foundation + Correction

Bring external products onto the platform. Specialize the brain for account types. Extend the billing clock.

Payment Loop confirm-before-commit PDE unified-checkout HUB — 3 veins
Drift & Reconciliation recompute-engine six-stores independent
Invoice Truth credit-notes invoice-lifecycle HUB — 3 veins
Dunning Brain single-decision-point idempotent HUB — 3 veins
Registrar orders-abstraction
Pay Pal dual-processor
Lifecycle billing-clock threshold
Segmentation account-types
requires feeds requires feeds complicates extends
MembraneActArcVeins
[Payment Loop](/payment-loop/)Foundation13ordering, unification, lifecycle
[Drift & Reconciliation](/drift-reconciliation/)Foundation10consistency
[Invoice Truth](/invoice-truth/)Correction17ordering, clarity, lifecycle
[Dunning Brain](/dunning-brain/)Correction17ordering, consistency, clarity
[Registrar Unification](/registrar-uc/)Expansion9unification
[Customer Segmentation](/customer-segment/)Expansion11clarity
[Subscription Lifecycle](/subscription-lifecycle/)Expansion7lifecycle
[PayPal Topology](/paypal-topology/)Expansion8unification