wiggleverse-ecomm-content/docs/maker-platform-pr-faq.md

Wiggleverse Maker Collective - A Platform for Makers to Connect — PR-FAQ

What this doc is. An Amazon-style PR-FAQ ("working backwards") version of 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 artifact, not a new strategy — every claim traces to the memo, with section citations (§7, Appendix C, …) into it. Where the two disagree, the memo wins (and the memo in turn defers to the Open Human Model on load-bearing concepts).

Audience. Technology experts who know Etsy/Shopify as users but aren't commerce specialists — so commerce jargon (merchant of record, money transmission, marketplace-facilitator tax, chargebacks, GMV) is defined inline; architecture is not.

Product name. "Wiggleverse Maker Collective"

---

PRESS RELEASE

Wiggleverse launches Wiggleverse Maker Collective, the first commerce platform built for commit-then-make, not just stock-then-sell

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 keeps their own storefront, checkout, customers, and far more of every sale — all-in fees around 4–7% versus Etsy's ~20%.

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. 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.

The problem. The tools makers rely on serve them poorly at exactly the moments that matter. Generic storefronts treat a scheduled drop or a 10-piece lottery as an afterthought, and marketplaces have drifted the other way: Etsy, founded on "handmade," is now flooded with mass-produced and AI-generated goods, so the buyer can no longer tell what's authentically created by a Maker. Makers are left choosing between a tool that 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. 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. Second, a verified merchant referral network: each maker's storefront (and, optionally, email marketing content) carries a "Curated By This Maker" section featuring other verified makers whose work they genuinely admire, with the curating maker's reputation on the line. Placement is earned, never sold — the opposite of pay-for-placement advertising. Every 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, 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 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 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 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 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 either couldn't handle it or wanted a cut of money it had no business touching," said a founding miniatures maker. "Here the drops just work, my customers are mine, and the makers I respect send buyers my way because they actually like my work — not because someone bought the slot."

"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 even real," said a tabletop hobbyist. "Here every piece tells me it's the 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. 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 expands along the adjacent-buyer arc — miniatures → resin dice → broader tabletop — 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.

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.

---

FAQ

Part 1 — Customer questions (makers & buyers)

What is "commitment commerce," and why is it so important to the pitch? It's the inverse of normal retail. Stock commerce is make it, shelve it, someone buys it (Shopify's model). Commitment commerce is collect committed demand, then make against it — a drop, a pre-order, a deposit-and-waitlist, a monthly club, a made-to-order commission. Many makers live in this mode; generic tools treat it as a bolt-on. The memo's core claim (§2) is that the drop/pre-order/club/commission cadence isn't a feature of a storefront — it is the platform, and it's the part that's genuinely hard to build well (the "gnarly 20%"). The storefront itself is a commodity we build as little of as possible and rent the rest.

I already use Etsy/Shopify. How is this actually different?

• vs. Etsy: Etsy is a marketplace that owns your buyer and takes a large cut, and its "handmade" guarantee has eroded. Here you own your buyer and your checkout, pay far less, and verification is real and reputation-staked.
• vs. Shopify: Shopify is a great stock storefront but mediocre at the commit-then-make cadence, and it has no cross-merchant referral network where sellers vouch for each other (it has a resell network — Collective — which is a different thing; see below).
• vs. Shopify Collective / Carro: those let merchants resell each other's products through one checkout, which forces the reseller to become merchant of record and handle payouts. Our network is referral, not resale — a vouch and a handoff, money stays siloed (§7, "the fork"). We deliberately don't compete on the plumbing, which is commoditized; we compete on verified provenance and reputation-staked curation, which a commission-optimized network structurally can't have (§3).

Isn't this just Patreon, for makers? Patreon is the closest comparison for one primitive — the monthly club — and it's worth being precise about why, because it's the de-facto club infrastructure in the beachhead (Appendix A/B). Unlike Etsy/Shopify, Patreon isn't the opposite motion: a membership is already commit-then-make (patrons commit ahead, the creator produces against it), so Patreon genuinely is doing this category for recurring clubs. But it sits on the wrong side of three things we treat as non-negotiable:

• It's in the money flow. Patreon is merchant of record, processes the recurring charge, takes ~8–12% all-in, and pays out. We keep the maker as merchant of record on their own processor (recurring billing via Stripe on a Standard account) and bill our software fee separately — so makers keep more and get usage-rights ownership of the patron, which Patreon doesn't grant.
• It's a walled garden on the buyer. You can't host a curation block on a Patreon page, attribute a referral through its checkout, or take the patron relationship with you — the same captive model as Etsy, applied to recurring relationships. So Patreon is an invitation target, not something we integrate into: "I'd feature your work the moment you own your commerce." (The one thing you can lift is your patron email list.)
• It can't build the network. Patreon is single-creator with platform-run algorithmic discovery — the opposite of maker-vouches-for-maker. Every patron there is a follow that never enters the cross-maker graph (our North Star), and it won't add reputation-staked cross-maker referral for the same reason Shopify won't build shared identity: it would have to become a different company.

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, on a tier that auto-graduates by volume so you never overpay: Starter at $0 + a small percentage (~2–4%) on captured orders (so a low-price-point maker isn't over-taxed), or Pro at a flat $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? No — and de-risking that question is a deliberate design goal (§7, "Shopify makers: federate, don't migrate"). You keep Shopify as your merchant-of-record storefront and connect via two hooks: a catalog sync (Shopify's Admin API + product webhooks feed our verified index) and referral attribution (the Curated-By link carries a signed token that rides in as a Shopify cart attribute → order note attribute, read off the order webhook). No checkout customization, works on any plan. The "hybrid wedge": keep your evergreen catalog on Shopify, use us only for the drop/pre-order/club events Shopify handles badly. Migrate later only if you want to.

What does "own the customer" mean here? The headline meaning is usage rights (§7, validated in interviews): the buyer relationship is yours to market to, on any channel, including off our network. This is the exact inverse of Etsy/Amazon, who forbid you from marketing to "their" captive buyers. We can grant it unconditionally because we don't monetize the captive relationship — we don't have one. Separately and optionally, sovereignty- minded makers can keep their buyers private from the cross-maker network graph; that's an opt-out, not the core meaning.

What does "verified" mean, and how do I get it? Verification answers "is this a real maker of original work?" at the door, and it's the gate to the demand surfaces (referrals, Curated-By, the buyer feed, AI-agent feed). Early on, staff verify a seed set directly; at scale, makers verify makers ("peer verification"), staking their own reputation — a rooted, multi-vouch trust graph with sampling audits, because it's the highest-stakes mechanism in the system (§7, "Verification"). The unverified tier still gets the full storefront tool — we 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 — and only with the featured maker's approval: B opts in to being curated by A, per relationship, so no one is featured against their will. On a referred sale two things stack. The platform's cut is fixed and never negotiated — a 3–5% spread on the order (it may scale with the sale and carry a $ cap), the network's one piece of referral revenue. Everything above it is the makers' to set: A and B define A's referral reward through platform tooling — a flat percentage, a tiered rate ("x% on orders over y"), a max- cap — and can renegotiate it as the relationship evolves, with 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 guardrail is to separate placement from economics (§3, §7). Placement is reputation-staked vouching, never pay-for-placement: you cannot buy your way into a maker's curation, the platform never sells a slot, featuring is capped per maker, visibly personal (name + face), gated by the featured maker's approval, and biased toward complementary makers, not rivals. The economics (A's referral reward) are a private term A and B negotiate, floored at the platform's fixed spread — but because 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 — not via curation, the buyer feed, or the agent feed. A maker who's only on Etsy is an invitation target, not a destination: "I'd feature your work the moment you own your commerce." The absence of the link is the recruiting signal.

Why invitation-only? That limits growth. On purpose, at launch (§7, "The membership gate phases"). A trust network cold- starts on density, not breadth — one community tight enough that word-of-mouth replaces a marketing budget. Scarcity keeps the trust guarantee absolute while the verified web is small, and makes every early member high-intent. The gate loosens toward open signup once roots and community density exist.

As a buyer, why should I care? Three things, in the order they matter (the buyer value prop, memo §13):

• You can finally trust what you're buying — every item shows a provenance badge (original / partly original / resale), the thing Etsy can no longer tell you, and worth more as AI-generated and recast fakes proliferate. That's the floor under everything.
• You're a fan, not a shopper — you follow makers and live for their drop/club/commission cadence. That relationship is what brings you back; it's what "commitment commerce" feels like from your side.
• The makers you trust introduce you to new ones — discovery comes from people you chose to follow and the makers they vouch for, never an algorithm pushing whatever converts (§7, "The buyer-facing feed").

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 enforces the FTC 30-Day Rule — a maker who can't ship on time must notify and offer a refund — 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)

The single most important design choice: why "stay out of the money flow"? Because touching the buyer's money detonates three regulatory regimes at once, and not touching it discharges all three (§7, §11):

• Money-transmitter licensing (MTL). In the US, holding customer funds (escrow, a balance, a payout you control) triggers state-by-state money-transmitter licenses — the single most expensive regime a small org could wander into. We never hold buyer funds, so: none.
• Marketplace-facilitator sales tax. Post-Wayfair, states can force a "marketplace facilitator" to collect and remit sales tax — but the test is conjunctive: you must both (1) facilitate the listing and (2) collect the buyer's payment. We fail prong 2 by design (the maker's processor collects), so the duty doesn't attach.
• Merchant-of-record (MoR) liability. The MoR is the legal seller — it owns chargebacks, refunds, and delivery liability. We make the maker MoR on their own processor, so all of that sits with them, not us.

The cost of this stance is forgoing payment take-rate — but that's exactly the slice that carries the risk. The cross-maker identity moat doesn't need checkout anyway: the asset lives at the follow, captured at the account layer regardless of whose processor runs the charge.

For the technically inclined: where exactly is the line? Custody. "Coordination and bookkeeping are free; custody — funds resting in an account you control — is the line" (the spine). We can record that maker A owes maker B, and even notify B that their component sold in A's kit — but routing a single dollar from A to B is custody. When we do eventually need cashable payouts (Phase 2), we rent a licensed transmitter (Stripe Connect/Treasury, Dwolla) rather than becoming one. One subtlety worth flagging to an engineer who'll wire Stripe: Connect's charge type and account type are legal-posture switches, not implementation details — Stripe's own tutorials default to "destination charges," 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").

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 cost) that compound with use. The honest competitive read (§11, "Novelty"): every component already exists — cross-merchant inclusion, drop/pre-order tooling, affiliate networks, verification badges, non-profit governance. The novelty is the specific combination, scoped to one dense vertical: verified per-item provenance

• reputation-staked cross-maker referral + native commitment-commerce + non-profit governance. The moat is positioning and governance, not patents — community standing, the rooted trust graph, the no-walled-garden value rule, and a 501(c)(3) structure a commission-optimized incumbent cannot copy without betraying its own 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 Medusa, a headless Node/TS commerce backend; we add drops/pre-orders/clubs as custom modules) or the maker's existing Shopify store, federated.
• Shared network service (cross-tenant — the moat) — the verification graph, a canonical catalog index, the cross-maker follow/identity graph, the referral/fee ledger, the buyer feed, and the agent feed. A standalone service with its own datastore that federates over heterogeneous storefronts.

The discipline a technical reader will appreciate: the network catalog is a read-optimized index (a normalized, verified projection of products that live and sell elsewhere), not a "mega-store." Pouring every maker into one Medusa instance would build "a thing shaped like a store that must never behave like one" and couple the neutral network to one engine. Each storefront stays system of record; the network holds the projection. Attribution is stateless — a signed token (origin maker + item + expiry + nonce) carries the referral path, so it works for guests in Phase 1 with no identity layer.

Why a non-profit built by volunteers? Isn't that fragile? The structure converts the trust position from a promise into a guarantee (§7, "Entity structure"): a 501(c)(3) legally cannot be sold or distribute profits, which is the strongest possible answer to "will you sell our trust for GMV the way Etsy did?" Open books let the community verify the incorruptibility of "verified" rather than take it on faith. And it's viable for a thematically exact reason: the cost center that usually makes non-profit tech infeasible — engineering — is the one LLMs just collapsed. The honest risk (§4, §12): the danger moved, it didn't vanish. The failure mode of volunteer orgs is sustaining, not building. So the critical core (network service, ledger, verification) must be funded, documented, and more 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):

• The core is protected by structure, not by trust. The trust guarantee, non-extraction, the no-walled-garden rule, and the out-of-flow stance are held by the non-profit and entrenched — a 501(c)(3) can't sell or distribute them, and they aren't editable by a simple majority. So the first answer to "who watches the watchers" is the structure does, and open books make it checkable.
• Authority over maker issues is progressively delegated as the network scales. The non-profit can't (and shouldn't) adjudicate every verification call or maker dispute at scale, so authority over maker-facing standards moves to representatives of the network as it grows beyond what the non-profit can manage — a vision of maker self-governance modeled on a functioning democracy: members elected to network roles (resolving disputes among them), where holding a role well earns standing in the network — the same reputation currency as making and vouching well. Phased in the same start-closed-open-as-earned way as verification itself.
• The mechanics are deliberately unspecified for now. Standing up a full governance apparatus before the community exists would be premature; the 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 ("the era of infinite alternatives") applied to maker commerce: every era commoditizes something — the internet commoditized knowledge, the cloud commoditized IT and then SaaS, and LLMs are now commoditizing platforms themselves. As that happens, the three moats incumbents stood on each turn into anchors — which is the opening:

• Build-cost / scale → anchor. The engineering to run a platform at scale was moat #1; LLMs deflate it, which is the only reason a no-equity non-profit can credibly build and sustain this (memo §7/§12). (Headless commerce — "build the 20%, rent the 80%" — is the same force at the storefront layer.)
• Vendor lock-in → dissolving. Commoditized custom software makes migrating between platforms cheap and fast; the network's federation and data portability ride this.
• Network effect → fragmenting — the one that matters most here. Our own moat is a network, so the obvious objection is that incumbents' network effects make them 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 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.

Two maker-specific accelerants sit on top: AI shopping agents are arriving and need trustworthy supply they can't scrape (the window to be their verified maker-supply rails is open now), and the platform's out-of-flow, never-GMV-fee, you-own-your-buyer stance is the org's non-extraction ethic in commerce form.

Why is this the Wiggleverse's first product — its beachhead? Mind the overloaded word: within this product the launch community is tabletop miniatures, but the product itself is the beachhead for the whole Wiggleverse — its first product and the proving ground for the org's mission (ethical, non-extractive alternatives to extractive platforms). It's first for four reasons:

• Fastest honest path to self-sustenance. Commerce is where money moves, so building close to it is the quickest route to a non-profit standing on its own feet (why ecomm first) — and a self-sustaining beachhead funds the rest of the portfolio (apps, learn).
• The most complete test of the thesis. It exercises every org bet at once: non-extraction (the out-of-flow stance is "take only what it takes to run"), the 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 ≈ 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)? 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 GMV. (The ~$0.8–1.2T global handicrafts market is backdrop, not a revenue base.) Sized properly:

• TAM — every independent maker who runs commit-then-make. Because the network federates over existing storefronts, the addressable supply is the whole controllable-storefront + marketplace install base, not just switchers: Shopify reports ~4.8M active merchants, Etsy ~5.6M active sellers. The true TAM is the commit-then-make subset — millions of makers, not thousands.
• SAM — commit-then-make-native makers, reached community-by-community. The model only works where you show up as a member, so it's summed over verticals. The tabletop-miniatures beachhead is a ~$3.8–4.2B/yr market growing ~7–10%/yr; Patreon's ~286k paying creators is a proxy for the commit-then-make creator population, of which tabletop is one slice.
• SOM — deliberately parametric, not a "capture X% of $Y" number. That top-down fiction is exactly what the memo's discipline refuses. Obtainable near-term scale is governed by the §12 break-even (N* ≈ F/(m−v)): clear the dozen-maker validation gate in one community, reach break-even density (~150–300 makers under illustrative midpoints), then compound vertical by vertical. The story is "reach self-sustaining density in one scene, then repeat" — not a slice of a giant pie.

(Figures from Shopify/Etsy/Patreon public reporting, Marketplace Pulse, and tabletop market-research reports; sourced links in memo §12.)

Is it sustainable? How does a no-take-rate non-profit cover costs? "Non-profit" changes who keeps a surplus (no one), not the arithmetic that revenue must meet cost (§12). It's a fixed-cost-coverage problem, not a margin problem: N* ≈ F / (m − v) — where F is the fixed reliability floor, m is per-maker net contribution (subscription + referral spread − drawn credits), and v is marginal per-maker cost. Two consequences fall out without needing real numbers: (1) 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, §12) puts the fixed reliability floor at F ≈ $75–150k/yr — funded core ops + the fee/wallet ledger + the verification audit + 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- zero for a pile of disconnected storefronts and rises only as the referral network does real work — so a "great tool that never becomes a network" (the most-feared outcome) shows a low North Star and can't hide behind a vanity supply count. Leading indicators beneath it: follower growth → Curated-By activation → drop sell-through → cross-maker repeat-buyer rate. All of it computes "for free" from the cross-merchant order history the referral ledger already requires — and a Goodhart guard applies: the metric must measure earned referral, not manufactured slots.

How do you actually acquire buyers — and what's still unproven? This is the keystone, and the memo now grapples with it directly in §13 (it used to be an admitted gap). The honest mechanics:

• Buyers don't arrive at the platform — they arrive at makers. The platform acquires no one directly; that's "maker-as-discovery-engine, platform-as-pipe." The first ~100 buyers are activation, not acquisition — the founding makers' existing audiences transacting on the new rails.
• The first ~1,000 come from compounding + supply — buyers who follow maker A start following A's vouched makers (the cross-maker repeat that lifts the North Star), plus more makers onboarding, each bringing an audience. Word-of-mouth inside one tight community is the multiplier — which is why the beachhead is dense, not broad.
• Net-new demand is deliberately deferred, not hidden. Early on the network reshuffles existing maker audiences rather than creating net-new buyers — the correct cold-start move, but not to be mistaken for solving acquisition. The net-new engines arrive later: verified taste-makers (community voices who bring their own audiences, Phase 2) and AI shopping agents (Phase 2+).
• What's still unproven: essentially all of it. The §8 discovery interviews talked only to makers — and to greenfield makers with no audience, who by definition can't test "will fans follow them here." So the demand moat is the least-validated part of the whole thesis. The next step is a §8 extension that recruits audience-having makers and tests buyer behavior behaviorally (a real instrumented drop; does a referral from A actually convert A's buyers into followers of B?), not by survey. Until that runs, treat the buyer side as a reasoned plan, not a validated result — which is exactly how the memo frames it.

What's the biggest risk? Demand (§4, §13). "Etsy but handmade" is a graveyard (Goimagine, Artisans Cooperative, Folksy, Amazon Handmade…) because curation fights liquidity: these platforms recruit angry makers (supply) and die for lack of buyers (demand). Demand at scale must be earned, not bought; paid acquisition against Etsy/Amazon is the losing game. The thesis bets that demand can emerge from makers bringing their own audiences and vouching for each other — but that's the unvalidated keystone, and 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 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 (narrow to one beachhead, add curated discovery) → Marketplace (light the referral network once supply density + community exist, so it emerges rather than launching cold into the graveyard) → Infrastructure (expose the verified-supply graph to AI shopping agents as trustworthy rails). The phasing of money is parallel: Phase 1 stays entirely out of the flow (stateless referrals, non-cashable wallet); Phase 2 adds shared identity and one rented cashable payout rail; Phase 3 (much later, opt-in) is the only point shared checkout — and the money-flow question — returns.

Why is "agent-ready rails" in here? Longer term, the verified-supply graph becomes the structured, real-time, trustworthy supply layer AI shopping agents need and can't manufacture by scraping (§3). That repositions the moat from "win consumer eyeballs" (unwinnable for a newcomer) to "be the verified maker-supply layer agents route through." Agent inclusion is gated on verification (not network membership) and defaults on for verified makers, because agent sales route back through the maker as MoR — net-new demand with no sovereignty cost. It's the hedge against the buyer feed's deliberate weakness at net-new reach.

What got deliberately left out of this PR-FAQ? 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 reader who wants the real architecture should read the strategy memo directly — this document is the elevator version, not a replacement.