KNOWLEDGE GRAPH
Semantic Billing
The billing system's knowledge graph. 1,142 nodes organized into 8 membranes, connected by 5 veins — the questions that no single membrane answers alone.
Five questions cut across the entire system. Each traces through multiple membranes. Follow a vein to understand how one concern ripples through the architecture.
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.
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.
How do bespoke product flows become one platform? Registrar moves onto unified checkout. PayPal is the exception that proves the rule — dual-processor topology.
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.
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.
Users get entitlements for free because state commits before payment confirms. Fixing this breaks eggs everywhere — every downstream system adapts to the new ordering.
Where ordering correctness meets state consistency meets customer clarity. Reads all six stores, decides based on confirmed payment state, routes per account type.
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.
Prove that confirm-before-commit works and that six stores can be read as one. These two capabilities gate everything else.
Make the invoice tell the truth and give dunning a single decision point. These require the foundation but not each other.
Bring external products onto the platform. Specialize the brain for account types. Extend the billing clock.
| Membrane | Act | Arc | Veins |
|---|---|---|---|
| [Payment Loop](/payment-loop/) | Foundation | 13 | ordering, unification, lifecycle |
| [Drift & Reconciliation](/drift-reconciliation/) | Foundation | 10 | consistency |
| [Invoice Truth](/invoice-truth/) | Correction | 17 | ordering, clarity, lifecycle |
| [Dunning Brain](/dunning-brain/) | Correction | 17 | ordering, consistency, clarity |
| [Registrar Unification](/registrar-uc/) | Expansion | 9 | unification |
| [Customer Segmentation](/customer-segment/) | Expansion | 11 | clarity |
| [Subscription Lifecycle](/subscription-lifecycle/) | Expansion | 7 | lifecycle |
| [PayPal Topology](/paypal-topology/) | Expansion | 8 | unification |
8 membranes. 5 veins. 3 acts. Start at a hub, follow a vein, read the arc.