Merge: Wiggleverse Maker Collective rename + PR-FAQ review-hardening (Tiers 1-5) + referral-model evolution + memo reconciliation

Squashes a full Amazon-style PR-FAQ review of docs/maker-platform-pr-faq.md (provenance, trust & safety, crowdfunding, pricing numbers, GDPR, buyer journey, kill-criteria, stored-value, press-release craft), an operator-directed referral-model evolution (fixed platform spread + negotiable maker rewards + structural ranking-neutrality), a memo<->PR-FAQ superset reconciliation, and honest §14 backlog flags for the remaining gaps (international tax, infosec, IP-moderation, verification method, support ops, competitor engagement). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-15 13:04:52 -07:00
parent adcf97f13e 25c26592cb
commit faaed0281c
2 changed files with 355 additions and 66 deletions
@@ -1,6 +1,6 @@
-# Maker Platform — PR-FAQ
+# Wiggleverse Maker Collective - A Platform for Makers to Connect — PR-FAQ
-> **What this is.** An Amazon-style **PR-FAQ** ("working backwards") version of
+> **What this doc is.** An Amazon-style **PR-FAQ** ("working backwards") version of
 > [`maker-platform-strategy.md`](./maker-platform-strategy.md). It opens with a
 > future-dated *press release* written as if the product had already launched,
 > then answers the questions a smart skeptic would ask. It is a communication
@@ -13,30 +13,25 @@
 > transmission, marketplace-facilitator tax, chargebacks, GMV) is defined inline;
 > architecture is not.
 >
-> **Product name.** "Wiggleverse Makers" — chosen over "Wiggleverse Market" to keep
+> **Product name.** "Wiggleverse Maker Collective"
 > the *network, not marketplace* positioning (memo §7); the public URL is
 > makers.wiggleverse.org, matching the brand. Pre-launch, so not
 > necessarily the final legal brand. **Dateline is aspirational** (target launch
 > Aug 1, 2026), per the working-backwards method: the press release is the
 > *target*, written before the build, not a record of a shipped thing.
 ---
 ## PRESS RELEASE
-### Wiggleverse launches Wiggleverse Makers, the first commerce platform built for *commit-then-make*, not just *stock-then-sell*
+### Wiggleverse launches Maker Collective, a verified-maker network where makers keep their own customers — and far more of every sale than on Etsy
 **A verified-maker network where independent makers run customized orders, drops, pre-orders, and
-clubs in addition to traditional *stock-then-sell* commerce — and earn demand by vouching for each other, not by buying ads. The maker
+clubs — not just ready-made inventory — and earn demand by vouching for each other, not by buying ads. The maker
-keeps their own storefront, checkout, customers, and ~20% more of every sale than
+keeps their own storefront, checkout, customers, and far more of every sale — all-in
-on Etsy.**
+fees around 4–7% versus Etsy's ~20%.**
-**SEATTLE, WA — August 1, 2026** — Wiggleverse Makers today opened to
+**SEATTLE, WA — August 1, 2026** — Maker Collective today opened to
 its first community of independent makers — the tabletop-miniatures scene: a
 commerce platform built around the way makers actually sell. Where Shopify and Etsy assume *stock-then-sell* — make
 inventory, shelve it, wait for a buyer — many makers run on *commit-then-make*: collect
 committed demand first (a drop, a pre-order, a deposit-and-waitlist, a monthly club, a made-to-order
-commission), then produce against it. Wiggleverse Makers is built for that motion
+commission), then produce against it. Maker Collective is built for that motion
 end to end, and adds something no storefront tool has: a **reputation-staked
 referral network** where makers send each other real buyers.
@@ -48,7 +43,7 @@ buyer can no longer tell what's authentically created by a Maker. Makers are lef
 doesn't fit and a marketplace that has stopped standing for anything — while
 paying marketplace fees that can approach 20% of each sale.
-**The solution.** Wiggleverse Makers is two things at once. First, a
+**The solution.** Maker Collective is two things at once. First, a
 **commitment-commerce engine** — scheduled drops, pre-orders and deposits,
 raffle/queue allocation, recurring clubs, made-to-order workflows, digital-file
 delivery — that runs on the maker's *own* storefront and *own* payment processor.
@@ -60,7 +55,7 @@ item carries a buyer-visible **provenance badge** (original / partly original /
 resale), so a buyer always knows what they're buying, and the platform never
 points a buyer at an Etsy or Amazon listing.
-Critically, **Wiggleverse Makers never touches the buyer's money.** The maker is
+Critically, **Maker Collective never touches the buyer's money.** The maker is
 the merchant of record on their own processor; the platform sells optional storefront software (or Makers can bring their own existing storefront) and
 bills its fee separately. That single architectural choice keeps the platform out
 of the financial and regulatory machinery that sinks marketplaces, and lets it
@@ -68,14 +63,14 @@ charge a fraction of Etsy's take.
 > "Every 'Etsy but actually handmade' before us recruited angry makers and died
 > for lack of buyers, because curation and liquidity pull against each other," said
-> a spokesperson for the non-profit behind Wiggleverse Makers. "We didn't launch a
+> a spokesperson for the non-profit behind Maker Collective. "We didn't launch a
 > marketplace. We launched a great tool for one tight community, and let demand
 > *emerge* from makers vouching for makers. The network is the product; the
 > storefront is just how some makers choose to plug in."
 **How it works.** A maker joins by invitation from an existing member who vouches
 that they make original work — a rooted trust graph, not an anonymous signup. They
-run their commitment-commerce events on a Wiggleverse Makers storefront *or* keep
+run their commitment-commerce events on a Maker Collective storefront *or* keep
 their existing Shopify store and connect it (the platform federates over both).
 Once verified, they can curate other makers and be curated; a signed referral
 token rides each "Curated By" link so the platform can credit the referrer and
@@ -83,11 +78,12 @@ bill the referred maker — without ever sitting in the payment flow. Referral
 income draws down the maker's own future platform fees, so curating well literally
 erases your bill.
-> "I run a drop every other Saturday and a monthly club, and every tool I tried
+> "Honestly, I almost didn't bother — I already have a Shopify store and a following, and
-> either couldn't handle it or wanted a cut of money it had no business touching,"
+> I didn't want to migrate everything to Some New Platform," said a founding miniatures
-> said a founding miniatures maker. "Here the drops just work, my customers are *mine*, and the makers
+> maker. "I didn't have to move anything: I kept my store, connected it, and ran my Saturday
-> I respect send buyers my way because they actually like my work — not because
+> drop and my monthly club right through it. What sold me was the referrals — makers I
-> someone bought the slot."
+> respect started sending me real buyers, because they actually like my work, not because
 > someone bought a slot. And nobody ever took a cut of money that wasn't theirs."
 > "I follow maybe a dozen casters and painters and I live for their drops — but I
 > got burned twice buying recasts off a marketplace, and lately I can't tell what's
@@ -95,7 +91,7 @@ erases your bill.
 > maker's own original work, and the makers I already trust point me to new ones I
 > end up loving. It's the people I follow — not an algorithm guessing."
-**Availability.** Wiggleverse Makers is opening invitation-only inside one tight
+**Availability.** Maker Collective is opening invitation-only inside one tight
 community — independent **miniatures makers** (resin/STL casters,
 sculptors, painters) — chosen because it expresses every commit-then-make motion at
 once and its makers already run drops, clubs, and made-to-order commissions. It
@@ -103,7 +99,7 @@ expands along the adjacent-buyer arc — **miniatures → resin dice → broader
 — as each community compounds. Makers on any controllable storefront — Wiggleverse,
 Shopify, or self-hosted — can be invited to verify and join. Learn more at makers.wiggleverse.org.
-*Wiggleverse Makers is operated as a true non-profit: open books, no equity, no
+*Maker Collective is operated as a true non-profit: open books, no equity, no
 sale, engineered by volunteers with LLM-accelerated development. The structure
 exists so the promise — that "verified" stays incorruptible — is enforced by law,
 not by good intentions.*
@@ -168,14 +164,41 @@ So the play is two-sided: **out-tool** Patreon's club with a native, out-of-flow
 lower-fee version the maker owns (the Tool), and **out-flank** it with the cross-maker
 referral network it structurally can't grow (the Network).
 **Isn't this just Kickstarter / Gamefound / BackerKit?**
 No — and the distinction *is* the opening: **campaign vs. cadence** (Appendix B).
 Kickstarter, **Gamefound** (tabletop-native, Kickstarter's biggest tabletop rival —
 sitting *in* the miniatures vertical), and BackerKit are built for **episodic,
 project-scale campaigns**: a big push that funds a project, then fulfillment. None of them
 serves the maker running a small drop **every other Saturday**, a 10-piece lottery, a
 monthly club, or a standing made-to-order queue — the **continuous** commitment-commerce
 cadence. That continuous, relationship-driven, small-batch motion is the unserved space
 *between* Shopify (continuous but stock-only) and Kickstarter/Gamefound (commitment but
 episodic), and it's where we play. So the posture is **coexist, not compete**: run your big
 annual campaign on Gamefound if that's the right tool for it — keep us for the continuous
 cadence *between* campaigns, plus the cross-maker referral network none of them have. Two
 structural cuts underline it: Kickstarter is itself **in the money flow** (it processes
 pledges, takes a cut, and pays out, disclaiming only *delivery* liability), where we keep
 the maker merchant-of-record on their own processor and shed both the flow and the
 delivery liability (§7/§11); and the campaign players are single-project tools with **no
 reputation-staked cross-maker referral graph** — the durable moat — which they won't build
 for the same reason the others won't.
 **What does it cost, and what's the "~20%" claim?**
 Marketplaces like Etsy bundle everything into one fee that, all-in, can approach
 ~20% of a sale (GMV = gross merchandise value, the total sold). We **unbundle**:
 you pay your own payment processor directly (their normal ~3%), and pay us a
-separate, modest software fee billed in arrears — a small percentage on captured
+separate, modest software fee billed in arrears, on a tier that **auto-graduates by
-orders for cold-start makers, or a flat **$29–49/month at 0%** once you graduate by
+volume so you never overpay**: **Starter** at $0 + a small percentage (~2–4%) on
-volume (§7, "How the platform gets paid"). The wedge is transparency: "our fee +
+captured orders (so a low-price-point maker isn't over-taxed), or **Pro** at a flat
-your processor ≈ X%, versus Etsy's ~20%" — stated in numbers. We bill on
+**$29–49/month + 0%** once your volume makes the flat fee cheaper (§7, "How the
 platform gets paid"). Worked through, all-in — *illustrative; real rates are set at
 launch*:
 - a **Starter maker doing ~$1,200/mo**: ~2–4% platform + ~3% processor ≈ **5–7%** all-in;
 - a **Pro maker doing ~$6,000/mo**: $39/mo + ~3% processor ≈ **~3.6%** all-in;
 - **Etsy, for either of them: ~20%.**
 That's the wedge in the numbers the doc owes you, not a slogan: a maker keeps roughly
 **13–16 percentage points more of every sale** than on Etsy. We bill only on
 *captured/fulfilled* orders, never on pledges that never cleared.
 **Do I have to abandon my Shopify store to join?**
@@ -208,25 +231,84 @@ graph with sampling audits, because it's the highest-stakes mechanism in the sys
 **gate the demand, not the tool** — so verification is something makers are pulled
 toward, not blocked at.
 **How do you know a specific *item* is original — not just that the maker is real?**
 Two different checks, and conflating them is the Etsy failure mode. **Verification** is
 about the *maker* ("a real maker of original work?"); **provenance** is per-*item* ("is
 *this product* their original work?"). A real maker's catalog is legitimately mixed — a
 potter sells their pots *and* resells pottery tools — so every item carries its own
 **provenance classification** (§7), **self-attested** by the maker, **audited** by the
 trust machinery, and **shown to the buyer**: *Original* (bought raw materials like clay
 are inputs to making, not other-sourced parts) · *Original + components* (primarily
 theirs, with identifiable parts from others attributed — the "partly original" kit case)
 · *Resale – fellow maker* (an in-network maker's original item, provenance tracing to the
 true maker — Curated-By as a catalog item) · *Resale – third-party* (commercial goods,
 tools, supplies — honest, allowed, clearly *not* original).
 Two things make the badge a guarantee rather than a self-serve sticker. **Eligibility
 keys off it, per item:** only *original* and *original-+-in-network-components* surface as
 the maker's original work in Curated-By / the buyer feed / the agent feed; a fellow-maker
 resale surfaces only *attributed to the true maker*; **third-party resale never enters a
 trust surface** — surfacing it would launder non-original goods through a trusted face,
 the Etsy pollution failure mode from the inside. And **misclassification has teeth:**
 calling a resale "original" is a *provenance lie*, not a clerical slip — a
 **verification-revocation trigger** (§10), with self-attestation (cheap to classify)
 policed by **sampling audits plus buyer reporting** (risky to game). One useful
 consequence: because "handmade/original" are advertising claims the FTC can require you to
 substantiate, this system *is* the substantiation mechanism (§11) — the product-defining
 feature and the compliance obligation are the same build.
 What's still open, deliberately: the precise, auditable line between *making* and
 *reselling* — purchased supplies don't taint "original," but assembling mostly-third-party
 parts isn't original either; finishing, assembling, and kitting sit in between. That
 standard is named as later work (§14 #2), not claimed as solved.
 **What is "Curated By This Maker," and how do referrals pay?**
 Each storefront carries a section where the maker features other *verified* makers'
-products they genuinely admire. When a buyer follows that link and buys, the
+products they genuinely admire — and **only with the featured maker's approval**: B opts in
-referred maker (B) pays a **referral fee** (~15%, the Faire/Amazon Handmade
+to being curated by A, per relationship, so no one is featured against their will. On a
-convention) and the curating maker (A) is *independently* credited (~10–12%) — two
+referred sale two things stack. **The platform's cut is fixed and never negotiated** — a
-separate events, so we're never a conduit moving money from B to A (which would be
+**3–5% spread on the order** (it may scale with the sale and carry a $ cap), the network's
-regulated money transmission). A's credit is **non-cashable**: it draws down A's own
+one piece of referral revenue. **Everything above it is the makers' to set:** A and B define
-future platform fees, so the more you curate, the closer your bill gets to zero
+A's referral reward through platform tooling — a flat percentage, a tiered rate ("x% on
-(§7, "Referral economics"). The spread (~3–5%) is our margin. It works at **n=2** —
+orders over $y"), a max-$ cap — and can **renegotiate** it as the relationship evolves, with
-two makers are enough for it to be useful, which is rare for a network feature.
+one floor, the platform spread. So B always pays *at least* the spread; if A and B set A's
 reward to zero, **no referral money changes hands and the platform still takes its spread.**
 The two legs stay independent — B pays on B's own invoice, A is *credited* separately — so
 the platform is never a conduit moving money B→A (which would be regulated money
 transmission). A's credit is **non-cashable** (it draws down A's own future platform fees,
 so curating well drives your bill toward zero). It works at **n=2** — two makers are enough
 for it to be useful, rare for a network feature (§7, "Referral economics").
 **Won't paid referrals just become advertising in disguise?**
-That's the central risk, and the guardrails are structural (§3, §7). Placement is
+That's the central risk, and the guardrail is to separate **placement** from **economics**
-**reputation-staked vouching**, never **pay-for-placement** (retail media): rates are
+(§3, §7). *Placement* is **reputation-staked vouching, never pay-for-placement**: you cannot
-**uniform and non-biddable** (you can't pay to rank higher), featuring is capped per
+buy your way into a maker's curation, the platform never sells a slot, featuring is capped
-maker, curation is visibly personal (name + face), and it's biased toward
+per maker, visibly personal (name + face), gated by the featured maker's approval, and
-*complementary* makers, not direct rivals. The name itself — *verified merchant
+biased toward *complementary* makers, not rivals. The *economics* (A's referral reward) are
-referral network*, not *retail media* — is a guardrail: the moment it starts
+a private term A and B negotiate, floored at the platform's fixed spread — but because
-selling slots, it's a self-evident lie.
+placement itself is non-biddable and the curator stakes their **own audience's trust**
 (feature junk for the money and your conversions and standing erode), a richer split can't
 buy a feature it didn't earn.
 The subtler version: among the items a maker curates, *the platform* decides which to
 surface to a given buyer — and we **do** use algorithms (personalization, popularity) to do
 it, because lifting conversions is the job. The guarantee is that **referral economics are
 never an input to that ranking** — and it's *structural*, not a pinky-swear: because the
 platform earns the **same fixed spread no matter which referred item sells**, it has **no
 incentive** to favor a higher-paying referral, so the ranking optimizes for the buyer's
 conversion, full stop. The name itself — *verified merchant referral network*, not *retail
 media* — is the backstop: the moment it starts selling slots, it's a self-evident lie.
 **If I'm the maker being *featured*, do I have a say — and am I just paying to be advertised?**
 Full say — on both the placement and the price. **Nobody features you without your
 approval:** being curated by a specific maker is **opt-in, per relationship** (A can feature
 B only if B agrees), and *buyer-identity* participation is a separate opt-in on top, never
 bundled. **You and the curator set the terms** (above) — you're not handed a rate, you agree
 to one, floored at the platform's fixed spread. And you're **not paying for an ad:** you pay only on an
 *actual referred sale* — incremental business you wouldn't otherwise have had — and the
 placement itself can't be bought (a curator features you only on genuine merit, their own
 audience-trust on the line, capped, name-and-face). Being featured is a *vouch you both
 agreed to*, not a slot — which is exactly why it's worth more than an ad.
 **Will you ever link a buyer to my Etsy/Amazon listing?**
 Never (§7; Appendix D). The network never routes a buyer *into* a walled garden —
@@ -254,6 +336,41 @@ Three things, in the order they matter (the buyer value prop, memo §13):
  *you* chose to follow and the makers *they* vouch for, never an algorithm pushing
  whatever converts (§7, "The buyer-facing feed").
 **As a buyer, where do I actually shop — is there an app, a site, a login?**
 Deliberately almost nowhere at first, and that's the point (§13). **At launch the platform
 is invisible to you:** you buy on the *maker's own storefront*, as a guest, the way you
 already do — there's no "Maker Collective" destination to sign up for, and "come back for
 the next drop" runs through the maker's *own* channels (their email, Instagram, Discord).
 The one thing the platform quietly powers is **follow/notify**, so you hear about the drops
 you care about. Later — Phase 2+, opt-in — a light **"your makers, in one place" feed**
 appears: followed makers' drops, "buy it again," and the Curated-By picks of makers you
 follow, with a light identity you can return to. But it's a *retention upgrade* on top of
 the makers' own channels, **pointedly not** a marketplace you evangelize ("I shop on X") —
 every item still traces to a maker *you* chose to follow, and the platform never becomes
 your primary relationship; the maker does. The mental model: **you're a fan of makers, and
 the platform is the wiring that keeps you connected to them**, not a store you shop at.
 **I pre-ordered, and the maker never delivered. What protects me?**
 This is the *signature* risk of commitment commerce, not an edge case — the model collects
 money before delivery, so "a verified maker takes pre-orders/deposits and ghosts" is the
 structurally most-likely scam, and a PR-FAQ that skipped it would be dishonest (§10). Two
 straight answers. **First, the platform is not a guarantor.** The same out-of-the-money-
 flow design that keeps fees low means the network never holds your funds — so it has
 nothing to refund *from*; escrow was declined deliberately (holding buyer funds is exactly
 what triggers money-transmitter licensing — §11). Your monetary recourse is a
 **chargeback against the maker's own payment processor** (the maker is merchant of
 record), and the platform's compliance-by-design checkout **eases the maker's FTC 30-Day
 Rule duty** — prompting the delay notice and one-click cancel/refund when a window slips (the
 duty is the maker's; the platform doesn't assume it) — which is your first recourse *before*
 a chargeback (§11). **Second, the platform's contribution is
 consequence, not insurance.** Non-delivery drops the maker's standing: a **low,
 buyer-visible reputation score** and **loss of all network amplification** (Curated-By, the
 buyer feed, referrals, the agent feed). They keep their storefront, but they fall out of
 every surface that sends them buyers, and you — and every future buyer — can see the score.
 That's *transparency as enforcement* (§10): the network doesn't promise nobody ever
 behaves badly; it makes bad behavior legible and costly, and keeps the trusted surfaces
 clean by construction, since a low-standing maker has already dropped out of them.
 ---
 ### Part 2 — Strategy & build questions (for the technically-minded skeptic)
@@ -292,6 +409,42 @@ which silently flip you to merchant-of-record and into facilitator-tax territory
 The stance holds *only* at Standard accounts + direct charges + `application_fee`
 (§7, "Money flow").
 **"You own the buyer" — doesn't that collide with GDPR and CAN-SPAM?**
 No, because "own" means **usage-rights to a *consented* relationship**, not a license to
 message anyone (§7, §11). The mechanics: the network captures **email + per-type marketing
 consent at checkout** and pushes the subscriber to the **maker's own ESP**, which is the
 source of truth and owns everything after — compliant unsubscribe, suppression,
 deliverability. So what the maker owns is the right to market — *on any channel, on or off
 the network* — to buyers **who consented**, with the unsubscribe machinery a real ESP
 already enforces. That's the precise inverse of Etsy/Amazon (who forbid off-platform
 marketing because the captive buyer is *their* asset), and it's lawful *because* it's
 consent-first. Two more structural points a privacy reviewer will want:
 - **Two consent domains, strictly separate.** *Maker-originating* marketing lives in the
  maker's ESP (the maker is controller); *network-originating* communications (the buyer
  feed, follow notifications, aggregate digests) run on **network-communication consent the
  network owns** — and the network **never borrows a maker's ESP list** for its own sends.
  That separation is what keeps every personal-data flow attributable to a lawful basis and
  a controller.
 - **The cross-maker identity graph is opt-in by design.** Being recognized across makers is
  a *buyer* opt-in, not a default-share — so the architecture is already aligned with the
  strictest "no sharing without affirmative consent" reading rather than retrofitting
  opt-outs. The posture is **build to the strictest law** (CCPA/CPRA plus the newer state
  laws, and **GDPR the moment EU buyers appear**), with access/deletion and
  opt-out-of-sale/sharing built in. (Per the handbook, "consent" defers to the OHM *consent*
  RFC, not a local definition.)
 **Isn't the referral "wallet" itself a regulatory problem — stored value?**
 No, by deliberate design (§11). The fee-offset wallet credits a maker against their **own
 future platform fees** — a *discount / accounts-receivable entry*, not a balance the maker
 can withdraw or spend with third parties. So it's neither stored value, a prepaid-access
 instrument, nor transmittable money, and stays outside the money-transmission and
 stored-value regimes *by construction*. The line is **cashing out:** the moment a credit
 becomes withdrawable cash, that's the deliberate crossing that re-opens the door — which is
 exactly why cashable payouts are **gated to Phase 2 behind a rented licensed transmitter**
 (Stripe Connect/Treasury, Dwolla), never a toggle flipped early. (Flagged for counsel:
 verify the non-cashable design against each state's stored-value / prepaid-access
 definitions before launch — *flag and verify, not legal advice*.)
 **What's the actual moat? Can't a competent team rebuild this in a week with LLMs?**
 The memo's organizing lens (§1): cheap production destroys **stock moats**
 (accumulated build/features) and rewards **flow moats** (data, network, switching
@@ -306,6 +459,34 @@ structure a commission-optimized incumbent *cannot* copy without betraying its o
 customers (§7, "Why this is the defensible core": Shopify won't build cross-merchant
 shared identity because its DTC merchants would experience it as theft).
 **What if Shopify just adds native drops and pre-orders — doesn't the tool wedge evaporate?**
 The answer depends on splitting two things both loosely called "the storefront" (§1, §3,
 §7). The **commodity surface** — cart, catalog, checkout, customer accounts — we
 deliberately *don't* build; we rent it ("build the 20%, rent the 80%," on a headless
 backend like Medusa, or federate over the maker's existing Shopify). The
 **commitment-commerce engine** — scheduled drops, raffle/queue allocation, deposits, clubs,
 made-to-order — is the part we *do* build, and the honest claim isn't that it's *hard*: it's
 that **no continuous (non-campaign) platform treats it as a first-class citizen.** Outside the
 Kickstarter-likes the table-stakes simply aren't covered first-class anywhere, so makers bolt
 the cadence onto tools that treat it as an afterthought. Being its first-class home is also the
 on-ramp to something nobody else is positioned for — wiring in the emerging generative/LLM
 maker tools (e.g. **cuttle.xyz**) that campaign platforms and stock storefronts have no reason
 to integrate, *because* they never made the cadence first-class. (It carries real
 financial/delivery liability too — taking money before delivery — which the
 out-of-the-money-flow architecture handles; but the claim is **first-class + integration
 headroom**, not difficulty.)
 But here's the part the doc won't dodge: **the tool is the wedge, not the moat.** The memo
 is explicit that storefront hosting isn't durably defensible — Medusa makes it cheap for
 everyone, and federation means a maker doesn't even *need* our storefront to be in the
 network (§7). The tool earns the cold-start (a real business at zero network liquidity) and
 gets makers in the door; the **durable** moat is the layer Shopify structurally *won't*
 build — the cross-maker **verified-provenance + reputation-staked curation network**, which
 its own DTC merchants would experience as theft (§3, §7, "the defensible core"). So if
 Shopify shipped excellent drops tomorrow it would neutralize a *convenience*, not the moat
 — the reason a maker stays is the network it can't copy without becoming a different
 company.
 **What's the architecture, in one breath?**
 Two layers, kept strictly separate (§7, "Storefront architecture"):
 - **Storefront layer (per maker)** — either our white-label storefront (built on
@@ -338,6 +519,24 @@ core (network service, ledger, verification) must be **funded, documented, and m
 than one person deep** — not bus-factor-one. The fragile-perception risk with
 professional makers is real and is something discovery explicitly tests (§8).
 **What happens to *my* drop if the platform goes down at 9am Saturday?**
 The honest answer has an architectural half and a staffing half. **Architecturally, the
 blast radius is small for most makers:** you are merchant of record on *your own* processor,
 and if you federate your existing Shopify store your drop and checkout run on *Shopify's*
 infrastructure — so if our cross-tenant network service is down, what degrades is *network
 features* (Curated-By, the buyer feed, the agent feed), **not your ability to take the
 order.** The sale doesn't ride on the moat layer. **Operationally,** for a maker on our
 white-label storefront the drop *does* run on our infrastructure — which is exactly why
 network-service uptime, the money-adjacent ledger, and verification are the **funded,
 documented, more-than-one-deep reliability core** (§12), explicitly *not* volunteer
 best-effort and *not* bus-factor-one. Drops are spiky by nature, and "a storefront falling
 over *during* a drop is the worst possible moment for maker trust" (§7, Hosting) — so the
 spike is designed for (autoscaling infrastructure, load-checked before a real drop), and
 the on-call reliability of those pieces is a **budget line, not a hope.** What the doc won't
 pretend: this is the single point of failure §4 names, so the reliability core is bound with
 structure (funded + redundant), and the fragile-*perception* risk with professional makers
 is something discovery explicitly tests (§8).
 **Who decides what "verified" means — and who watches the watchers?**
 Two answers, by time horizon (memo §14 #1 — direction set, mechanics deliberately
 deferred):
@@ -360,6 +559,40 @@ deferred):
  *direction* (progressive delegation, phased, capture-resistant) is set — the
  machinery is later work.
 **What actually stops collusion — a ring of fake makers vouching each other in, or weaponized reports?**
 The highest-stakes surface in the system, because one polluted "verified" item breaks the
 guarantee for every buyer and agent downstream (§7, §10). The defenses are structural, not
 best-effort:
 - **The trust graph is rooted, never flat.** It is emphatically *not* "anyone verified can
  verify anyone." Every maker enters by invitation and traces back, by a chain of vouches,
  to a seed set Wiggleverse staff verified directly — a **permanent topology** that
  persists even after open signup arrives, so a compromised subtree can be found and
  revoked at its root.
 - **Inviting pays nothing.** There is deliberately **no per-invite bounty** — a payout
  would manufacture the exact Sybil/farming incentive the rooted graph exists to resist.
  You invite people whose work you'd stake your standing on, because that is the only thing
  the edge means.
 - **The vouch is a slashable stake, and consequence flows uphill.** When a maker
  misbehaves, consequence propagates **back toward whoever vouched for them** — transitively,
  **decayed per hop, and hop-capped**: strong right next to the misbehavior (the inviter who
  can actually act), negligible by ~6 degrees out (a distant root isn't punished for a
  great-great-invitee's fraud). A bad vouch costs the voucher standing; a good one compounds
  it.
 - **The consequence is loss of standing, not expulsion.** A bad actor keeps the storefront
  tool (a paying customer; the tool was never gated) but loses a buyer-visible score and
  all amplification. Authority is layered: the **inviter** holds primary suspend authority
  over their sub-graph, a **platform floor** lets staff act directly on active buyer harm
  regardless, and a **governance appeal path** (§14 #1) protects the wrongly-penalized.
 - **Sampling audits + buyer reporting** sit underneath — and the abuse surface of the
  reporting system *itself* (false reports, retaliatory scores, collusion rings) is named
  as instrumented from day one alongside ring-detection.
 What's deliberately deferred (and marked so): the *reputation engine's* concrete mechanics
 — the scoring math, the decay-coefficient and hop-cap *values*, the benefit-gating
 thresholds, and the false-report/collusion controls — are explicit OHM-guided open work
 (§10, §14 #1), not claimed as solved. The *shape* is settled; the *values* are later work,
 because n=2 can't calibrate them yet.
 **Why now?**
 This is the org-level [Wiggleverse thesis](https://wiggleverse.org/about/) ("the era
 of infinite alternatives") applied to maker commerce: every era commoditizes something
@@ -377,7 +610,7 @@ incumbents stood on each turn into anchors — which is the opening:
  unassailable. The answer: incumbents got greedy and extractive and **eroded their own
  network stickiness**, so a values-aligned alternative can now contest a network moat
  that used to be untouchable. Etsy's reckoning is that erosion made concrete — its
-  active-seller base fell ~9M → ~5.6M as it purged for quality, while AI-generated and
+  active-seller base fell from ~9M (2023) to ~5.6M as it purged for quality, while AI-generated and
  recast fakes flood marketplaces, leaving verified provenance scarcer, more valuable,
  and surrounded by disaffected makers to recruit.
@@ -401,13 +634,11 @@ first for four reasons:
  network moat against eroding incumbents, OHM ethics made concrete (verification,
  provenance, usage-rights), and the open-core partner ecosystem. Prove it here and the
  rest is de-risked.
- **The ethic, legible in dollars.** "Our fee + your processor ≈ X% vs Etsy's ~20%" —
+- **The ethic, legible in dollars.** "Our fee + your processor ≈ 4–7% vs Etsy's ~20%" —
  the mission is a number on every sale, not a slogan.
 - **"Small businesses are really just people."** Serving makers directly is the mission
  — treat humans as humans — applied where commerce most turned them into accounts.
 **How big is the opportunity (TAM)?**
 **How big is the opportunity (TAM)?**
 The honest unit of TAM here is **makers, not the dollar size of the craft market** —
 because the platform earns per-maker subscription + referral spread, never a cut of
@@ -443,9 +674,22 @@ break-even is driven by keeping F lean (the LLM-deflated-cost bet) and by makers
 *graduating and referring*, not merely by adding low-GMV makers; (2) there's also a
 *ceiling* — earn too much, too commercially, and a non-profit risks **UBIT**
 (Unrelated Business Income Tax) or its exemption. An illustrative pass (explicitly
-*shape, not validated values*) puts break-even around **~150–300 makers**, well past
+*shape, not validated values*, §12) puts the fixed reliability floor at **F ≈
-the **dozen-maker** validation gate — and naming that gap is the point. The numbers
+$75–150k/yr** — funded core ops + the fee/wallet ledger + the verification audit +
-are variables because n=2 can't calibrate them yet.
+hosting — and break-even around **~150–300 makers**, where the revenue mix has flipped from thin
 Starter percentages to Pro flat fees + referral spread (≈$170k/yr at ~200 makers under
 those midpoints), well past the **dozen-maker** validation gate — and naming that gap is the
 point.
 The number a CFO will press on is F, so the doc is blunt about it: **F is not the cloud
 bill.** The seductive error is to model F as the pilot's tens-of-dollars-a-month GCP
 invoice; the honest F is dominated by **compensated, documented, more-than-one-deep
 ownership** of the reliability core — network-service uptime, the money-adjacent ledger,
 the verification audit — none of which can be best-effort. Under-modeling F is exactly how
 an org clears break-even *on paper* and still dies of bus-factor (§4). The
 LLM-deflated-cost bet is that F can be kept **lean, not that it's near-zero** — and the
 numbers stay variables because n=2 can't calibrate per-maker GMV, churn, or graduation rate
 yet.
 **How will you know if it's working?**
 One **North Star: the share of GMV that is cross-maker-referred** (§12). It's near-
@@ -493,6 +737,29 @@ audiences and vouching for each other — but that's the **unvalidated keystone*
 it's gated on discovery (§8): do enough audience-having, vouch-willing makers exist
 in one tight community? Everything is downstream of that question.
 **What's the falsifiable hypothesis here — and what would make you kill it?**
 The thesis rests on one keystone, stated to be falsifiable, not asserted: **demand can be
 *earned* — makers bring their own audiences and vouch for each other — rather than bought**
 (§4, §13). The go/no-go is concrete (§9 decision gates), and a failed gate *stops the build*,
 not just dings it:
 - **The dozen-maker gate.** Can you reach ~a dozen makers in one tight community who feel the
  *same* commit-then-make pain *and* refer you onward? Two makers justify a portable data
  model; they do **not** justify building the platform. If the dozen doesn't cohere, you
  don't build — full stop.
 - **The behavioral demand test (the decisive one).** Discovery so far talked only to makers —
  and *greenfield* ones with no audience. So before the platform is built, run a **real
  instrumented drop** and measure whether a referral from maker A actually converts A's
  buyers into followers of B. If that propagation doesn't happen, the network thesis is
  falsified at the cheapest possible point.
 - **The North Star as a live kill-signal.** Post-launch the one number is **the share of GMV
  that is cross-maker-referred** (§12) — near-zero for a pile of disconnected storefronts,
  rising *only* if the network does real work. A persistently low North Star is the explicit
  failure mode ("a great tool that never becomes a network"), and it can't hide behind a
  vanity supply count.
 The honest posture: **the tool is a real business even if the network never lights** — so
 failure is survivable, not ruinous — but the *network*, the actual moat, is gated on a
 falsifiable demand test the org commits to running *before* betting on it.
 **What's the sequencing? You keep saying "don't launch a marketplace."**
 Four acts, each viable alone, each earning the next (§5): **Tool** (the
 commitment-commerce engine — a real business at zero network liquidity) → **Community**
@@ -518,7 +785,14 @@ cost. It's the hedge against the buyer feed's deliberate weakness at net-new rea
 The memo's full depth on trust-&-safety/accountability (§10), the complete
 legal/compliance analysis (§11), composite multi-maker kits (Appendix C), the
 beachhead-selection method and worked example — miniatures → dice → broad tabletop
-(Appendix A), and the crowdfunding-incumbent landscape (Appendix B). A technical
+(Appendix A), and the crowdfunding-incumbent landscape (Appendix B). Also **honestly
-reader who wants the real architecture should read the
+unfinished** and tracked as open work in the memo's backlog (§14): the **international
-[strategy memo](./maker-platform-strategy.md) directly — this document is the
+tax / cross-border** posture (the legal analysis is US-only today, under a digital-heavy
 global beachhead), **information security & breach posture** for the cross-tenant graph,
 **content moderation beyond authenticity** (third-party IP / DMCA), the **verification
 *methodology*** (how a verifier actually confirms original work), **support/dispute
 operations** as a funded function, and a head-to-head against the **creator-commerce
 tools** (Gumroad/Payhip/Ko-fi/Fourthwall). A technical reader who wants the real
 architecture — and the honest open edges — should read the
 [strategy memo](./maker-platform-strategy.md) directly; this document is the
 elevator version, not a replacement.
@@ -27,7 +27,7 @@ Build for **independent makers** — positioned as "the curated maker marketplac
 Two halves, treated differently:
- **Commitment-commerce engine (the real product).** The maker-native cadence layer Shopify lacks: scheduled drops, pre-orders and deposits, raffle/queue allocation, made-to-order workflows, recurring clubs/memberships, digital-file delivery + licensing where relevant, and variant/bundle handling. This *is* the gnarly 20% and the reason vertical infrastructure here is defensible — emphatically *not* "the same as Shopify." (The white-label storefront is the commodity surface, subsumed here: build the least of it you can, rent the rest.)
+- **Commitment-commerce engine (the real product).** The maker-native cadence layer Shopify lacks: scheduled drops, pre-orders and deposits, raffle/queue allocation, made-to-order workflows, recurring clubs/memberships, digital-file delivery + licensing where relevant, and variant/bundle handling. This *is* the gnarly 20% and the reason vertical infrastructure here is defensible — emphatically *not* "the same as Shopify." The defensibility isn't that the cadence is *hard* to build — it's that **no continuous (non-campaign) platform treats it as a first-class citizen**, so the table-stakes go uncovered everywhere outside the Kickstarter-likes (Appendix B); being its first-class home is also the on-ramp to integrating emerging generative/LLM maker tools (e.g. **cuttle.xyz**) that campaign platforms and stock storefronts have no reason to touch. (The white-label storefront is the commodity surface, subsumed here: build the least of it you can, rent the rest.)
 - **Cross-maker demand network (the moat).** The flow asset, accruing as a *byproduct* of the engine. Every drop/pre-order captures a buyer who *follows* a maker and commits early; a base of drop-followers across many makers is the embryonic cross-merchant identity network — the niche-scoped Shop Pay equivalent. Stock commerce gives you people who bought once; commitment commerce gives you people who *wait for* makers and commit ahead — a far stronger flow asset. Reputation-staked cross-maker curation turns that into *earned* demand, not just relocated demand.
 The reframe: commitment commerce is not a feature of the storefront — it *is* the platform, and the mechanism that builds the flow moat, rather than something engineered separately alongside it.
@@ -48,7 +48,7 @@ Two maker-commerce-specific accelerants sit on top of the org thesis: **AI shopp
 - **The fastest honest path to standing on its own feet.** Running a non-profit and the infrastructure under a platform takes money; commerce is where money moves most, so building close to commerce is the quickest route to a sustainable economic position ([Wiggleverse — why ecomm first](https://wiggleverse.org/ecomm/)). A self-sustaining beachhead is also what funds the rest of the portfolio (the *apps* and *learn* products to come) — the §12 economics read at org scale.
 - **The hardest, most complete test of the thesis.** This product exercises *every* load-bearing Wiggleverse bet at once: **non-extraction** (the out-of-flow, never-GMV-fee stance, §7/§11, *is* the org's "take only what it takes to run"), the **flow/network moat** against eroding incumbents (the §2/§4 thesis and the three moats above), **OHM ethics made concrete** (consent, agency, dignity, value, recourse show up as verification, provenance, and usage-rights — §7/§10/§11), and the **open-core partner ecosystem** (§7 partner network). Prove it here and the rest of the portfolio is de-risked.
- **The most tangible "give value, not extract" demonstration.** Commerce makes the ethic legible in dollars — *our fee + your processor ≈ X% vs Etsy's ~20%* (§7) — so the mission is a number on every sale, not a slogan ("what is enough? — enough to keep the lights on, and no more").
+- **The most tangible "give value, not extract" demonstration.** Commerce makes the ethic legible in dollars — *our fee + your processor ≈ 4–7% vs Etsy's ~20%* (§7) — so the mission is a number on every sale, not a slogan ("what is enough? — enough to keep the lights on, and no more").
 - **"Small businesses are really just people."** Serving independent makers directly *is* the OHM mission — *treat humans as humans* — applied to the place commerce had most thoroughly turned them into accounts and line items.
 ---
@@ -152,7 +152,8 @@ Model A is reputation-staked human curation (the anti-pollution, can't-be-gamed
 **Guardrails:**
 - **Attribution is stateless — no identity layer required.** A signed referral token (origin maker + item + expiry + nonce) rides the A→B handoff into B's order; you read it to bill B and credit A. It tracks the *referral path*, not the buyer, so it works in Phase 1 for guests and sovereign makers. Persistent identity is only for the *durable* effects (follows, cross-session credit).
- **Commission-corruption trap.** When Curated-By pays well, curation drifts to "feature whoever converts/pays most." Keep it reputation-staked: cap how much any maker can feature, make it visibly personal (name + face), prefer "A owns/uses this," and never sell slots. The sincere vouch is the whole value.
+- **Commission-corruption trap.** When Curated-By pays well, curation drifts to "feature whoever converts/pays most." Keep it reputation-staked: **B must approve being curated by A** (per-relationship opt-in — placement is consented on both sides, distinct from the default-on *catalog presence* switch below), cap how much any maker can feature, make it visibly personal (name + face), prefer "A owns/uses this," and never sell slots. The sincere vouch is the whole value.
 - **Ranking neutrality — structural, not a promise.** Among the items a maker curates, the *platform* chooses which to surface to a given buyer, and it **will** use algorithms (personalization, popularity) to lift conversions — that's the platform's job. The guarantee is that **referral economics are never an input to that ranking**, and it holds *by construction*: the platform's spread is the **same percentage no matter which referred item sells** ("Referral economics" below), so the platform has no incentive to favor a higher-paying referral. Structural indifference is a *stronger* guarantee than a flat uniform rate — it survives makers negotiating their own rewards.
 - **Complementary, not substitute.** Nudge toward complementary makers (a maker surfaces an adjacent craft, not a direct rival) — complementary curation is generative; substitute curation is cannibalistic and makers won't do it.
 ### How the platform gets paid
@@ -161,12 +162,12 @@ Out of the money flow, your fee is a **platform fee billed in arrears via ACH/in
 - **Tiered "graduate" pricing.** Starter: $0/low monthly + a modest **percentage** (≈2–4%) on captured orders (cold-start-friendly). Pro: flat **$29–49/mo + 0%** (predictable, easy to collect, at scale). Auto-graduate by GMV so makers don't overpay. Use a **percentage, not a per-order flat fee**, on low-AOV makers (a flat $0.50 over-taxes a $12 item).
 - **Charge on captured/fulfilled orders, not pledges** — don't bill money that never cleared.
- **Market the all-in transparently:** "our fee + your own processor ≈ X% vs Etsy's ~20%." Not bundling processing is the wedge — say it in numbers.
+- **Market the all-in transparently:** "our fee + your own processor ≈ X% vs Etsy's ~20%." Not bundling processing is the wedge — say it in numbers. Illustratively (shape, not validated rates): a Starter maker at ~$1,200/mo runs ~2–4% platform + ~3% processor ≈ **5–7%** all-in; a Pro maker at ~$6,000/mo runs $39/mo + ~3% processor ≈ **~3.6%** all-in — versus Etsy's ~20% either way, i.e. the maker keeps roughly **13–16 percentage points more of every sale.**
-**Referral economics.** On a referred order, charge Maker B a **referral fee** (≈15%, Faire/Amazon-Handmade convention) and *independently* credit Maker A. Keep them as **two separate events** — B→Platform (a fee on B's invoice) and Platform→A (a credit you extend) — so you're **principal on both sides, never a conduit** moving money B→A. That independence keeps it out of money-transmission territory, and holds *only* while A's credit is non-cashable.
+**Referral economics.** On a referred order, two layers stack. **The platform's spread is fixed and never negotiated** — ≈3–5% of the order (it may scale with the sale and carry a $ cap), the network's one piece of referral revenue, and *the same percentage regardless of which referred item sells* — which is what makes the ranking-neutrality guarantee structural rather than a promise ("Curated By This Maker" above). **Maker A's reward sits above the spread and is the makers' to set:** A and B negotiate it through platform tooling — a flat %, a tiered rate ("x% over $y"), a max-$ cap — and may **renegotiate** as the relationship evolves, with one floor, the spread. So B always pays *at least* the spread; set A's reward to zero and no referral money changes hands while the platform still earns its spread. (This negotiability is **scoped to maker↔maker** referrals; the pure non-maker taste-maker tier keeps **uniform, non-biddable** rates — it lacks the peer-respect counterweight — see "Non-maker referrers" below.) Keep the legs as **two separate events** — B→Platform (a fee on B's invoice) and Platform→A (a credit you extend) — so you're **principal on both sides, never a conduit** moving money B→A. That independence keeps it out of money-transmission territory, and holds *only* while A's credit is non-cashable.
- The referral fee **subsumes** the standard fee on referred orders (one clean "15% because referred"), rather than stacking toward Etsy-like ~19%.
+- The referred order's total **subsumes** the standard fee (one clean "this is the referred rate"), rather than stacking toward Etsy-like ~19%.
- **B's fee and A's credit are independent numbers; the spread is platform margin** (e.g., charge B 15%, credit A 10–12%, keep 3–5%) — one of the few places the network itself generates revenue.
+- **The fixed spread is the network's referral revenue line** (≈3–5%, $-capped) — not negotiable, and the *same percentage whatever is referred*; A's negotiated reward is the layer on top, non-cashable (below). One of the few places the network itself generates revenue.
 - **Non-cashable fee-offset wallet.** A's credit draws down *future platform fees first* — driving the curation flywheel ("curate → wipe out your fees"), lowering collection risk, and cleaner on tax (a fee discount, not income). **Cashing out re-opens the money-flow door** (rent BaaS — Connect/Treasury/Dwolla); a deliberate Phase-2 crossing, not a toggle.
 - **Pending → cleared settlement.** Credit A as *pending* (not spendable) and hold B's fee pending; settle **both legs together** after B's refund window (≈14–30 days) closes, so in-window refunds void both atomically with zero clawback. Negative balances are a debit on a continuing account: reverse pending, then available, then push any shortfall to the next ACH invoice; keep the ACH mandate active through offboarding; a rolling reserve only if a few high-volume curators make it material.
@@ -183,7 +184,7 @@ Out of the money flow, your fee is a **platform fee billed in arrears via ACH/in
 **Opt-in network model — carrot, not stick.** It self-selects the commons-minded makers the network works for. The benefit must be **concentrated and visibly fast** or opt-in becomes a ghost town. Keep the asymmetry **additive** (joiners get referral income, placement, cross-promotion, fee offset, feed surfacing) — never **punitive** (don't cripple the standalone storefront to force joining). Design for **granular** participation, **reciprocity** (surfacing proportional to participation), and a **social-proof opt-in moment** ("makers you respect sent each other 200 buyers last month — want in?").
-**Don't bundle "on our storefront ⇒ on the network."** Forcing full network participation on storefront makers is the coercion the opt-in model rules out, and it weakens the storefront's standalone (n=1) value. Split two switches: **catalog presence** (your products *can* be discovered/curated/fed) is reasonable to **default-on (opt-out)** for storefront makers (low-friction, low-sensitivity); **buyer-identity participation** (your *buyers* are recognized cross-maker) stays a **separate, consent-gated opt-in** (sovereignty-sensitive, and it's the buyer's data). Take the convenience (auto-catalog-sync); never the coercion (forced identity sharing).
+**Don't bundle "on our storefront ⇒ on the network."** Forcing full network participation on storefront makers is the coercion the opt-in model rules out, and it weakens the storefront's standalone (n=1) value. Split two switches: **catalog presence** (your products *can* be discovered/curated/fed) is reasonable to **default-on (opt-out)** for storefront makers (low-friction, low-sensitivity) — though being *featured in a specific maker's Curated-By* (a vouch carrying referral economics) is a **per-relationship opt-in** the featured maker approves (§7, "Curated By This Maker"); **buyer-identity participation** (your *buyers* are recognized cross-maker) stays a **separate, consent-gated opt-in** (sovereignty-sensitive, and it's the buyer's data). Take the convenience (auto-catalog-sync); never the coercion (forced identity sharing).
 **Why this is the defensible core.** Shopify *won't* build cross-merchant shared identity — its customers (sovereignty-seeking DTC merchants) would experience it as the platform claiming their buyers, betraying the exact promise Shopify sells. Shopify does the *resell* network (share *products*) but not the *referral* network (share *buyers* with attribution). Your bet: community-embedded makers relate to shared identity as *belonging*, not theft. The moat isn't the storefront, the commitment-commerce mechanics, or the resell network (Shopify has that) — it's the **cross-maker identity-and-attribution layer**, the one asset an island-based incumbent is fenced out of by its own positioning.
@@ -261,7 +262,7 @@ Any website can join as a *referrer* — a taste-maker/curator (a hobby YouTuber
 - **Unverified referrer (open tier).** Generates referral links to verified makers, earns on conversion, but is **not surfaced in any trust-dependent surface** — a traffic source, self-limiting (a bad one doesn't convert) and contained (can't touch trust surfaces).
 - **Verified taste-maker (trust tier).** A legitimate community voice verified as a *trusted curator* (not a maker), reputation-staked and slashable — badge, surfacing, loses status for shilling. Verification separates the genuine taste-maker (additive) from the affiliate-spam farm (corrosive).
-**The load-bearing guardrail: uniform, non-biddable referral rates.** A maker-curator's commission pull is counterbalanced by peer respect; a pure taste-maker's incentive is more purely the fee, so if makers could set different rates, taste-makers would chase the highest payer — retail media through the referrer door. A uniform rate means they feature on **taste, not who pays most.** Plus **disclosure/labeling** (distinguish a maker's peer vouch from a taste-maker's disclosed-affiliate pick; FTC-required anyway), **referrer-only/one-directional** (never a destination, never a maker-verifier), and the **no-walled-garden rule** still holds.
+**The load-bearing guardrail for this tier: uniform, non-biddable referral rates.** A maker-curator's commission pull is counterbalanced by peer respect (and the structural ranking-neutrality guarantee), which is why **maker↔maker rewards are negotiable above the fixed spread** (§7, "Referral economics"). A pure taste-maker's incentive is more purely the fee, so that same negotiability would let them chase the highest payer — retail media through the referrer door. **For non-maker taste-makers, therefore, rates stay uniform and non-biddable** — they feature on **taste, not who pays most.** Plus **disclosure/labeling** (distinguish a maker's peer vouch from a taste-maker's disclosed-affiliate pick; FTC-required anyway), **referrer-only/one-directional** (never a destination, never a maker-verifier), and the **no-walled-garden rule** still holds.
 **Why it's worth doing:** taste-makers are the **net-new-demand engine** the maker-only network is structurally weak at — a third source alongside maker-curation (deepens) and agents (reach), and the most community-native (a trusted human voice, not an algorithm).
@@ -316,7 +317,7 @@ Now that Medusa exists and the network federates over any storefront, *centering
 Implementation consultants (community-embedded especially) onboard the **high-touch tail** without the network becoming a services business, doubling as community-aligned distribution and mirroring the partner ecosystems that grew Shopify and Medusa — a second flywheel you *enable* (certification, a directory, the referral-income share below) but don't *staff*. Guardrails: keep the product **genuinely self-serve for the median maker** (if makers *need* a consultant for a basic store, the product failed and partners are masking it), and structure partners as **referral/implementation partners, not white-label resellers**, so they don't become the relationship-owner and disintermediate you.
-**How partners are paid — a negotiated, tapering share of the maker's *earned* referral income.** A maker may opt to bring on a partner to stand up their storefront and onboard them onto the referral network, and pay for that help out of the upside it creates: the partner earns a **share of the referral income the maker earns *as a curator*** (the 10–12% Curated-By credits in "Referral economics" above) — not a fee on the maker's sales, and not a cut of the platform's spread. The natural shape is **front-loaded and tapering** — e.g. 100% of the maker's first $X in referral earnings to the partner, then a declining share as the maker's curation takes off — a *help-me-start, earn-out* deal, not a perpetual tax. The two negotiate and structure the schedule through **platform tooling**; the network stores the agreed terms and settles the split. This is the *one* partner-compensation leg the network touches, and it rides the same invariants as the rest of the money model, so it adds posture, not exposure:
+**How partners are paid — a negotiated, tapering share of the maker's *earned* referral income.** A maker may opt to bring on a partner to stand up their storefront and onboard them onto the referral network, and pay for that help out of the upside it creates: the partner earns a **share of the referral income the maker earns *as a curator*** (the negotiated Curated-By referral reward in "Referral economics" above) — not a fee on the maker's sales, and not a cut of the platform's spread. The natural shape is **front-loaded and tapering** — e.g. 100% of the maker's first $X in referral earnings to the partner, then a declining share as the maker's curation takes off — a *help-me-start, earn-out* deal, not a perpetual tax. The two negotiate and structure the schedule through **platform tooling**; the network stores the agreed terms and settles the split. This is the *one* partner-compensation leg the network touches, and it rides the same invariants as the rest of the money model, so it adds posture, not exposure:
 - **Out of the flow, principal on both sides.** The platform never routes the maker's money to the partner (that is custody / transmission — Appendix C.2's line); it independently *reduces* the maker's referral credit and *extends* the partner a credit or payout — two events, principal on each, never a conduit (the §7 referral-economics pattern).
 - **A fourth consumer of the one Phase-2 cashable rail.** The maker's referral credit is non-cashable (fee-offset); a partner who isn't itself a maker has no platform fees to offset, so — exactly like the verified taste-maker and the kit pure-supplier — it needs *cashable* payout over the same scoped Connect/mass-pay crossing Phase 2 already builds. (A partner who *is* a maker can take non-cashable wallet credit instead.) One more rider on that crossing, not new money plumbing; Phase 1 can accrue the partner's split as *pending* and pay it on rail launch.
@@ -505,7 +506,7 @@ Per the decision above, this is a **parametric** model: the fee *rates* are desi
 **Two revenue lines, both from §7.**
 - **Subscription.** Cold-start makers pay Starter (≈2–4% of captured GMV, no/low monthly); at scale they auto-graduate to Pro (flat **$29–49/mo**, 0%). The flat Pro fee is the *predictable* margin; the Starter percentage is cold-start-friendly but thin on low-GMV makers.
- **Referral spread.** On a referred order, Maker B pays ≈15% and Maker A is credited 10–12%; the **spread (≈3–5%) is platform margin** (§7, "Referral economics"). But A's credit is a *non-cashable draw against A's own future platform fees* — so a referral credit is **foregone future fee revenue**, not free money. The model must net it: referral activity generates spread *and* erodes subscription/fee revenue as credits are drawn. Treat the credit as a cost line, not a wash.
+- **Referral spread.** On a referred order the platform takes a **fixed ≈3–5% spread** (the network's referral revenue line), and Maker A earns a **negotiated reward above it** (§7, "Referral economics"). The spread is the platform margin modeled here; A's reward is a *non-cashable draw against A's own future platform fees* — so it is **foregone future fee revenue**, not free money. The model must net it: referral activity generates spread *and* erodes subscription/fee revenue as credits are drawn. Treat the credit as a cost line, not a wash.
 **A note on partner-network splits.** Where a maker pays a partner out of its earned referral income (§7, "Partner / consultant network"), the split **redistributes the maker's curator income, not the platform's spread** — the platform stays principal on both legs and its 3–5% margin is unchanged. So partner comp does not move the platform's break-even directly; it is **maker-borne activation cost, paid from the upside**, that lowers the friction of turning a maker into an *active referrer*. Model it as a driver of the referral-activation rate (and thus of the North Star, below), not as a platform cost line.
@@ -569,7 +570,7 @@ The §9 gates are all qualitative — *do makers refer you? is the pain consiste
 **The order-history asset computes all of this for free.** §7 already commits it: *"One asset, three uses — the same order history powers the referral ledger, the network-health metrics, and this reporting."* The cross-tenant vantage is the only place cross-maker-referred GMV and cross-maker repeat *can* be computed — no single-store tool sees across stores (which is itself moat-deepening, §7). So these metrics are not new instrumentation to fund; they fall out of the ledger the referral system already requires.
-**Goodhart caution — the metric must measure *earned* referral.** A North Star is a target, and a target invites gaming. The corrupt way to lift "cross-maker-referred GMV" is to *manufacture* referrals — pay for placement, juice the slots — which is precisely the retail-media drift §3 and §7 ("Curated By This Maker") exist to forbid. The North Star is only valid as a measure of **reputation-staked, earned** cross-referral; optimized the wrong way it rebuilds Etsy's pollution from the inside, through the dashboard. This is the OHM **value** point in metric form: the number must track real value to buyers and makers, not gamed volume — so pair the North Star with the §7 anti-corruption guardrails (uniform non-biddable rates, capped per-maker featuring, reputation on the line) rather than reading it naked.
+**Goodhart caution — the metric must measure *earned* referral.** A North Star is a target, and a target invites gaming. The corrupt way to lift "cross-maker-referred GMV" is to *manufacture* referrals — pay for placement, juice the slots — which is precisely the retail-media drift §3 and §7 ("Curated By This Maker") exist to forbid. The North Star is only valid as a measure of **reputation-staked, earned** cross-referral; optimized the wrong way it rebuilds Etsy's pollution from the inside, through the dashboard. This is the OHM **value** point in metric form: the number must track real value to buyers and makers, not gamed volume — so pair the North Star with the §7 anti-corruption guardrails (structural ranking-neutrality — the platform's spread is constant, so its algorithms ignore referral economics; capped per-maker featuring; per-relationship approval; reputation on the line; uniform rates for non-maker taste-makers) rather than reading it naked.
 ### Volunteer-sustainability economics — funding the critical core off bus-factor-one
@@ -649,6 +650,20 @@ This memo is deep on the architectural/strategic axes (money flow, network mecha
 2. **Hybrid makers — the making-vs-reselling line (standard).** *Direction set:* provenance attaches **per-item, not per-maker**, via a self-attested, buyer-facing catalog classification (Original / Original + components / Resale – fellow Maker / Resale – third-party), with trust-surface eligibility keyed to it — see §7 "Per-item provenance: the catalog's originality layer." *Still open:* the precise, **auditable line between making and reselling** — purchased supplies don't taint "original," but where exactly do finishing, assembling, and kitting fall? — plus the enforcement/audit hook (ties to §10 accountability) and the exact buyer-facing label wording. Interacts with the consignment/resale "avoid" fork (§7) and the no-walled-garden value rule (Appendix D).
 3. **International tax & cross-border operation (US-only today — flag for specialist counsel).** §11's analysis is entirely US (the *Wayfair* facilitator test, MTL, FTC). But the beachhead is **STL/digital-file-heavy and globally distributed** (UK/EU/AUS casters), so this is a *live* hole, not a someday: **EU/UK VAT on digital goods** (OSS/IOSS — VAT owed in the buyer's country from the first unit) and the EU **"deemed-supplier"** marketplace rule, which can pull a *facilitating* platform into VAT collection on logic that **does not mirror** the US "we fail prong 2" defense — so the out-of-flow stance does not automatically transfer abroad. Adjacent: **PSD2/SCA** on EU recurring club billing (the maker's processor must handle it; a "Standard account" doesn't discharge it), multi-currency display/settlement, and **KYC/AML/OFAC** onboarding for non-US makers/taste-makers on the Phase-2 cashable rail. *Direction: scope which jurisdictions Phase 1 actually serves, and put the VAT/deemed-supplier question to specialist cross-border counsel before international participants are first-class. Flag and verify — not legal advice.*
 4. **Information security & breach posture for the cross-tenant network service.** §7/§11 cover privacy *consent* thoroughly; neither covers *security*. The shared network service holds the single most attractive breach target in the design — **every maker's full order history + buyer PII + the cross-maker identity graph** — and for a *trust* brand a breach is existential, not merely costly. Still open: encryption at rest/in transit + key management, tenant-isolation and least-privilege access to the cross-tenant store, secrets handling, and an incident-response / breach-notification plan (state laws + the GDPR 72-hour clock). *Direction set here: infosec of the network service belongs in the §12 **funded reliability core** alongside the ledger and the verification audit — a trust-moat budget line, not a volunteer-cadence nice-to-have; the concrete controls are later work.*
 5. **Content moderation beyond authenticity (third-party IP / DMCA / prohibited goods).** Provenance verifies *handmade*, not *lawful to sell*. The minis/tabletop beachhead carries a heavy **third-party-IP/DMCA** load (fan-sculpts of others' IP; the Games Workshop takedown culture), plus counterfeit, regulated, and offensive-content surfaces — and the network *amplifies* whatever it surfaces (Curated-By, the buyer feed, the agent feed), so it inherits **amplification / contributory liability** distinct from "is it handmade." Still open: a DMCA §512 notice-and-takedown posture + designated agent, an IP-complaint / repeat-infringer policy, and the line between *verified original craft* and *originality of the depicted IP* (a verified maker can still infringe). Interacts with verification (§7) and accountability (§10). *Flag for counsel; design the takedown path before the agent feed amplifies at scale.*
 6. **Verification methodology — the evidentiary act (currently treated as a primitive).** §7 specifies the verification *graph* (rooted, staked, multi-vouch, sampling audit) and §10/#1 above defer the reputation *engine* — but **how a verifier actually establishes that a human makes original work** (what proof, what process, what staff and peers inspect) is neither specified nor flagged, and it is the literal foundation of the trust moat and the §11 FTC-substantiation claim — the hard adversarial core in an AI-fake world. Still open: the **provenance-documentation standard** (studio evidence, work-in-progress, live demo?), the staff seed-set method, and what a peer verifier must attest. *Name it as load-bearing open work, not a solved primitive.*
 7. **Support & dispute operations — the function and its cost.** §12 funds the reliability core (uptime, ledger, verification audit) but never a **support/ops function**: maker tickets (a broken sync at drop time), buyer-harm report intake, and the verification-revocation / appeal queues (§10). For a volunteer-built, money-adjacent, trust-critical platform this is a real recurring **F-term omission** and an operational-credibility question. *Still open: the support model, triage/SLAs for money-adjacent vs cosmetic issues, and its line in the §12 cost base.*
 8. **Competitive engagement: creator-commerce tools.** The "no continuous (non-campaign) platform treats commit-then-make as first-class" claim (§2) is load-bearing and currently engages only Etsy/Shopify/Patreon/Kickstarter/Gamefound. The sharper counter-examples a skeptic raises are the **creator-commerce tools** — Gumroad, Payhip, Ko-fi Shop, Fourthwall, Lemon Squeezy — several of which already do drops + memberships + digital delivery at low fees. *Still open: a head-to-head that substantiates "first-class, not covered" against these specifically — the likely cut being that each does the storefront/transaction but none does the cross-maker reputation-staked referral network (the moat), and most treat the cadence as features rather than the spine; verify the claim rather than assert it.*
 9. **Lower-priority flagged items (named, not yet developed).** (a) **cuttle.xyz / generative-tool integration** is cited as a differentiator (§2) without substance — develop what the integration is and why it's defensible, or demote it to a mere example. (b) **Catalog-sync reliability at scale** — N adapters against rented APIs (Shopify rate limits, webhook-delivery failure, deprecation cycles, reconciliation) is a chronic ops burden the moat surfaces depend on. (c) **Accessibility** (WCAG/ADA) for generated storefronts and the buyer feed — a compliance surface and an OHM-*dignity*-aligned one. (d) **Trademark / certification mark for "verified"** — a certification mark is the natural instrument to protect the badge from imitation (FTO/patent is covered in §11; this isn't). (e) **Platform wind-down plan** for the network asset — given volunteer-sustainability is the named #1 risk (§4), what becomes of the cross-maker graph, follows, buyer accounts, and outstanding wallet credits/payables if the org folds. (f) **Team / execution capacity** — the docs argue the model is *affordable*; named team/board/recruiting capacity is a separate, unaddressed question (arguably a roadmap/ops-doc concern more than a strategy one).
 ---
 ## Appendix A — Choosing a beachhead vertical (and sequencing expansion)