Why Guilds exist: Trust you can verify
Guilds are designed for a sandbox playground—open to anyone willing to show up, participate, and let the record speak for itself. The "Small Street Applied – Atlanta" GitHub repo is the public presentation layer of that record: an append-only trail of receipts, obligations, and extinguishments posted on a monthly cadence.
Three income lanes (kept separate)
-
APatronage dividends (Guild/LCA lane) Guild outcomes distributed based on participation rules—recorded as patronage dividends.
-
BMerchant income (commerce lane) Product/service merchant receipts are accounted for as merchant income.
-
CReferral bonuses (non-employee lane) Referral compensation is tracked as non-employee income (separate from patronage).
The point is simple: no mixing buckets. When categories are clean, trust becomes easier—for members, auditors, and regulators.
Monthly MSB-style statement posting
Each Guild posts a monthly statement that mirrors money-services discipline, even when the "game" is simply presence + proof + community accounting.
- Receipts posted What was pledged/earned/recorded during the month (by category).
- Obligations posted What the Guild owes (patronage distributions, operational obligations, etc.).
- Extinguishments posted What obligations were closed out (extinguished) according to the algorithm and rules.
Links above are placeholders—wire them to your Small Street Applied – Atlanta repo pages.
How a kite festival becomes a Guild trust event
Kite festivals are where the concept stays human: no slogans, no outrage, no wallets—just presence, participation, and a smartphone-based pledge. A Guild makes that participation legible by converting it into clean monthly reporting.
Festival flow (wallet stays home)
- Show up with your smartphone Your device is your proof-of-presence anchor—simple, personal, and hard to fake at scale.
- Pledge $30 Your pledge is the commitment signal that the Guild can account for and report.
- Take to the sky Participation is the product. The Guild records outcomes and posts them monthly.
- Monthly posting builds Trust Receipts, obligations, extinguishments—published to the append-only record.
What gets posted (example format)
Below is a human-readable example (not financial advice—just the structure of what a Guild publishes for verification).
GUILD MONTHLY STATEMENT (Example)
Period: YYYY-MM (local time)
Entity: POC Guild (LCA-aligned)
Posting: Append-only (Small Street Applied – Atlanta)
1) RECEIPTS
- Patronage receipts (eligible for dividends): $______
- Merchant income receipts: $______
- Referral bonuses (non-employee): $______
2) OBLIGATIONS
- Patronage dividend obligation: $______
- Operations / fulfillment obligation: $______
- Other disclosed obligations: $______
3) EXTINGUISHMENTS
- Obligations extinguished this period: $______
- Method: published Guild algorithm + rules
- References: txn ids / event ids / proofs (links)
The algorithm is the promise. The monthly posting is the proof. Trust becomes a habit.
Guild promise
A Guild does not ask people to "trust the vibe." It asks them to trust a process: play in the sandbox, pledge with your phone, then verify the monthly record.
If your community can gather to fly kites—peacefully, playfully, and consistently—then the Guild can do what money systems rarely do: show its work in public.
"Join a Guild" and "Start a POC" open the demand-signal modal on the home page. Replace "Open the Guild Ledger" / "How the Algorithm Works" with your repo URLs when ready.