fragment-dev/fragment
Build money flows in your app (prepaid credits, wallets, payouts, escrow, spending limits) on a Fragment ledger whose rules the ledger itself enforces, and prove them with an independent judge.
Proves a ledger-backed money flow works by writing an independent judge from the spec alone, fixing its fingerprint before the build is read, then testing the service over HTTP (amounts, races, crashes, retries) and posting forbidden entries straight to the ledger, each of which must be refused. Use when the user asks to prove, audit or judge a flow, or whether it is correct. It is not a routine step of building one.
Designs a Fragment ledger schema whose entry types enforce a money flow's invariants as ledger conditions — no negative balances, settle-once state machines, exact splits, bounded captures and refunds, fees proved on the ledger — using the kit's tested primitives. Use when writing or reviewing a Fragment schema, or when a rule must hold even if the app's code is wrong.
Load this before designing or writing any code that keeps balances of money or credits in an app, even for a quick sketch or a short answer. Covers prepaid credits and promo credits, wallets, top-ups, usage drawn from a balance, reservations or holds for long jobs, marketplace payouts and fee splits, escrow, refunds and chargebacks, and spending limits or budgets for agents and teams. Gives a design where a Fragment ledger enforces the rules (no negative balance, exact splits, settle or capture once), with tested recipes and code.