docs: add maker-platform PR-FAQ; deepen strategy memo (demand, why-now, TAM, Patreon, governance)

New docs/maker-platform-pr-faq.md — an Amazon working-backwards PR-FAQ derived
from the strategy memo for a tech-expert, commerce-novice audience (press release
+ customer/internal FAQ, citing memo sections). Finalized: name "Wiggleverse
Makers", target launch 2026-08-01, market.wiggleverse.org, illustrative-persona
quotes.

Strategy memo (docs/maker-platform-strategy.md):
- §2: "Why now" grounded in the Wiggleverse three-moats thesis; "Why this product
  is the Wiggleverse's beachhead".
- §4 + Appendix B/D: Patreon as the continuous-membership incumbent and
  membership-side walled garden (recruit-out + out-tool + out-flank).
- §12: "Market size" TAM/SAM with researched anchors; SOM kept parametric.
- §13: Demand strategy & buyer-side go-to-market promoted from backlog (the
  unvalidated keystone); backlog → §14, cross-refs updated.
- §14 #1: governance direction set (progressive delegation; maker self-governance
  vision modeled on a functioning democracy), mechanics deferred.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/maker-platform-strategy.md

@@ -36,6 +36,21 @@ The reframe: commitment commerce is not a feature of the storefront — it *is*
 
 **Business model (detail in §7):** the **network is the product and the value capture** (referral take + network subscription, charged identically whether a maker is on your storefront or Shopify); the **storefront is an optional, SaaS-priced convenience — never GMV-fee'd, never sold as hosting.** You are a *vertical commitment-commerce product*, not a hosting company; a partner/consultant network onboards the high-touch tail.
 
+**Why now — the Wiggleverse thesis, applied to maker commerce.** The timing argument here isn't particular to makers; it is the org-level [Wiggleverse thesis](https://wiggleverse.org/about/) — *"the era of infinite alternatives"* — specialized to one vertical. Every era commoditizes something: the internet commoditized knowledge, the cloud commoditized IT infrastructure and then small SaaS, and **LLMs are now commoditizing the platforms themselves.** As they do, the three moats incumbents were built on each turn into *anchors* — and that is precisely the opening:
+
+- **Build-cost / scale → anchor.** The manpower and capital to run software at platform scale was the first moat; LLMs deflate it (the §1 stock-moat lens), which is exactly what makes a volunteer/non-profit build viable here (§7, §12) — the entity and the opportunity are the same bet. (Headless commerce maturing — *build the 20%, rent the 80%*, §6 — is the same force at the storefront layer.)
+- **Vendor lock-in → dissolving.** Commoditized custom software makes migrating off a platform cheap and fast; you no longer wait for a vendor's export tools. The memo's federation, data portability, and ESP-as-source-of-truth (§7) ride this directly.
+- **Network effect → fragmenting — and this is the one that matters most here.** The memo's *own* moat is a network (§2), so the obvious objection is that incumbents' network effects make them unassailable — the §4 graveyard. The Wiggleverse 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. (No contradiction with §1, where flow moats compound: a flow moat compounds only while it is *stewarded* — the incumbents spent theirs.) Etsy's authenticity reckoning *is* that erosion made concrete — its active-seller base fell from ~9M to ~5.6M as it purged for quality (§12 sizing) while AI-generated and recast fakes flood the marketplaces, so verified provenance is at once scarcer, more valuable, and surrounded by freshly-disaffected, recruitable supply (§3).
+
+Two maker-commerce-specific accelerants sit on top of the org thesis: **AI shopping agents are standing up** and need structured, trustworthy, real-time supply they cannot scrape — the narrow window to be the verified maker-supply rails agents route through opens now (§3, §7); and the same **non-extraction ethic** the org is built on (give value, don't extract — an OHM principle) is precisely what the out-of-the-money-flow, never-GMV-fee, usage-rights-ownership stance (§7) *is*, in maker-commerce form. Miss the window and the provenance grievance normalizes, the agent rails get built by someone *in* the flow, and the build-cost advantage commoditizes for everyone at once (§1).
+
+**Why this product is the Wiggleverse's beachhead.** Two nested beachheads are in play and shouldn't be confused: within *this* product, the launch *community* is tabletop miniatures (§5, Appendix A); but the product *itself* is the **beachhead for the whole [Wiggleverse](https://wiggleverse.org/) portfolio** — its first product, the proving ground for the org-level mission of ethical, non-extractive alternatives to extractive platforms. It earns that role on four counts:
+
+- **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").
+- **"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.
+
 ---
 
 ## 3. Positioning: what's yours vs. what's commodity
@@ -60,7 +75,8 @@ Longer term, the verified-supply graph becomes **agent-ready rails** — the tru
 - **n = 2 is learning, not validation.** The engineer's trap is over-abstracting for two clients when the right abstraction only reveals itself around ten.
 - **Commitment commerce carries financial/delivery liability.** Taking money before delivery inherits structural delivery risk — chargebacks, non-delivery, makers who collect pre-orders and don't ship. This is *why* the 20% is gnarly (financial risk, not just UX). The design answer (§7): stay out of the money flow so the maker, as merchant of record, carries it.
 - **Raffle/lottery legality.** The raffle drop mechanic can be regulated as a lottery/gambling depending on jurisdiction — the one primitive with real compliance exposure. Understand it *before* building it as a headline feature.
-- **Campaign vs. cadence is a product fork — pick cadence.** Episodic, project-scale crowdfunding is owned by entrenched incumbents (Kickstarter, Gamefound, BackerKit — Appendix B). The unserved gap is the *continuous* drop cadence (the biweekly drop, the monthly club). Don't drift into competing with Gamefound; own the continuous-relationship layer they don't serve.
+- **Campaign vs. cadence is a product fork — pick cadence.** Episodic, project-scale crowdfunding is owned by entrenched incumbents (Kickstarter, Gamefound, BackerKit — Appendix B). The unserved gap is the *continuous* drop cadence (the biweekly drop, the monthly club). Don't drift into competing with Gamefound; own the continuous-relationship layer they don't serve. (One continuous-cadence slice *does* have an incumbent — the monthly club, owned by **Patreon**; the next bullet faces it.)
+- **Your beachhead lives on a walled garden you're recruiting them off of.** In miniatures, the de-facto club infrastructure is **Patreon** — the *membership-side* walled garden (Appendix D) and the commitment-commerce incumbent for the recurring-club primitive (Appendix B). It is a *sharper* competitor than Shopify for that slice — a club is already commit-then-make, not Shopify's stock-then-sell — and unavoidable, because your first community is already on it. The posture it forces — **recruit-out + replace-the-club (native, out-of-flow, maker-MoR) + lift-the-patron-list** — is therefore materially more load-bearing than the memo's posture toward Etsy, which is otherwise the lead walled-garden example.
 - **Volunteer-core sustainability is the single point of failure** (given the non-profit/volunteer model, §7). LLMs make a smaller core go further but don't fix volunteer attrition or bus-factor. The parts touching money, catalog data, and verification need *reliability*, not best-effort — so the critical core (network service, ledger, verification) must not be bus-factor-one. The historical killer of volunteer orgs is *sustaining*, not building; transfer the rigor you'd spend on fundraising onto this.
 
 ---
@@ -236,7 +252,7 @@ Two rules ride on the classification:
 - **Buyer transparency is the point.** Every item shows its provenance badge — the consumer-facing expression of the moat: not merely "this maker is verified," but "this *item* is original / partly original / a resale / not original (and contains these makers' work)." It is the precise anti-Etsy signal — you always know what you're buying — and it *appreciates* as AI-generated and drop-shipped fakes proliferate.
 - **Trust-surface eligibility keys off it, per item.** Only **original** and **original-+-(in-network)-components** items are surfaced as the maker's original work in Curated-By / buyer feed / agent feed. A **fellow-Maker resale** may surface *attributed to the true maker* (that *is* Curated-By). **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). A composite that contains any non-original component is flagged as such wherever it appears.
 
-The hard, still-open part is the **line between making and reselling** — finishing, assembling, and kitting sit in between (the standard to write, §13 #3): purchased supplies don't taint "original," but assembling mostly-third-party parts isn't original either. Misclassifying a resale as "original" is a provenance lie → a verification-revocation trigger (trust & safety, §10). Self-attestation makes classifying cheap; the sampling audit plus buyer reporting make gaming it risky.
+The hard, still-open part is the **line between making and reselling** — finishing, assembling, and kitting sit in between (the standard to write, §14 #2): purchased supplies don't taint "original," but assembling mostly-third-party parts isn't original either. Misclassifying a resale as "original" is a provenance lie → a verification-revocation trigger (trust & safety, §10). Self-attestation makes classifying cheap; the sampling audit plus buyer reporting make gaming it risky.
 
 ### Non-maker referrers: the verified taste-maker tier (Phase 2)
 
@@ -382,7 +398,7 @@ The **shape** below is settled; the **reputation engine itself is explicitly OHM
 
 ### Authority & appeal
 
-- **The inviter holds primary suspend/expel authority** over their own sub-graph — the person who vouched is the person best placed, and most motivated (their standing is on the line), to act. Layered on top: a **platform floor for active buyer harm** (the platform can act directly when buyers are being harmed, regardless of what an inviter does), and a **governance appeal path** (§13 #2) for the maker who believes a consequence was unjust. **Expulsion is the rare extreme**, reserved for active harm — the default consequence is loss of standing, above.
+- **The inviter holds primary suspend/expel authority** over their own sub-graph — the person who vouched is the person best placed, and most motivated (their standing is on the line), to act. Layered on top: a **platform floor for active buyer harm** (the platform can act directly when buyers are being harmed, regardless of what an inviter does), and a **governance appeal path** (§14 #1) for the maker who believes a consequence was unjust. **Expulsion is the rare extreme**, reserved for active harm — the default consequence is loss of standing, above.
 - **Provenance lies are trust violations.** Misclassifying a resale as "original" (§7 per-item provenance) is not a clerical error — it is a deception that pollutes the trust surfaces, and so it is a verification-revocation trigger handled by this machinery.
 - **The legal spine of the ghosting case is in §11.** Non-delivery isn't only a reputation event: the FTC 30-Day Rule (§11, "Consumer protection / FTC") is what a ghosting maker is *violating*, and the platform's compliance-by-design notice/refund UX is the buyer's first recourse *before* a chargeback against the maker's processor. Reputation consequence and legal recourse are two responses to the same act.
 
@@ -473,7 +489,7 @@ Recap the §7 consent architecture, now read as the privacy-law posture.
 
 ## 12. Sustainability economics & health metrics
 
-The memo is deep on architecture and silent on whether the architecture pays for itself. That silence is the dangerous kind: ventures rarely die of a bad money-flow diagram, they die of a cost base no one modeled. Two questions sit under "is this sustainable," and they are different questions. **Does the fee model cover the cost base, and at what scale?** — the unit-economics question. And **is the network actually working?** — the health/liquidity question that turns the §9 gates from enthusiasm-readings into instruments. Both rest on the same asset: the cross-merchant order history the network already holds to compute referrals (§7, "Storefront architecture & Shopify coexistence"), which is *uniquely* able to see across stores. The numbers here are deliberately left as variables — n = 2 can't calibrate them (§4) — because the contribution this section makes is the *model and the instruments*, not invented values. This whole section turns on OHM **value** (the metric must track *earned* value, not gamed volume) and **trust/recourse** (the trust guarantee is only as good as the funded reliability behind it); where it names one, the canonical RFC governs (top-of-file note).
+The memo is deep on architecture and silent on whether the architecture pays for itself. That silence is the dangerous kind: ventures rarely die of a bad money-flow diagram, they die of a cost base no one modeled. Two questions sit under "is this sustainable," and they are different questions. **Does the fee model cover the cost base, and at what scale?** — the unit-economics question. And **is the network actually working?** — the health/liquidity question that turns the §9 gates from enthusiasm-readings into instruments. Both rest on the same asset: the cross-merchant order history the network already holds to compute referrals (§7, "Storefront architecture & Shopify coexistence"), which is *uniquely* able to see across stores. The *unit-economics* numbers here are deliberately left as variables — n = 2 can't calibrate them (§4) — because the contribution this section makes is the *model and the instruments*, not invented values; the **market-sizing anchors** added below are the one deliberate exception, since external market structure is publicly knowable rather than an uncalibrated internal variable. This whole section turns on OHM **value** (the metric must track *earned* value, not gamed volume) and **trust/recourse** (the trust guarantee is only as good as the funded reliability behind it); where it names one, the canonical RFC governs (top-of-file note).
 
 ### "Non-profit" is not "needn't cover costs"
 
@@ -524,6 +540,14 @@ Two readings fall out, both reinforcing the parametric conclusions above. The re
 
 **The honest caveat (memo voice).** These are the variables, not values: n = 2 cannot calibrate per-maker GMV, the referred-GMV share, churn, or graduation rate. Naming the model is the point — and the §9 gate should start **instrumenting** the inputs (per-maker GMV, referred share) so that break-even stops being unknown by the time the dozen-maker gate is cleared. The same order-history asset that powers the metrics below makes every one of these variables measurable per maker (§7) — the model and the instruments are the same build.
 
+### Market size — count makers, not craft-market GMV
+
+The memo asserts *TAM = every maker* (§7, "Business model") but never sizes it. The sizing discipline that matters: **the unit of TAM is makers, not the dollar size of the craft market** — because revenue is per-maker subscription + referral spread, never a GMV take (§7). A roughly **$0.8–1.2 trillion** global handicrafts market ([Fortune Business Insights](https://www.fortunebusinessinsights.com/handicraft-market-108435)) is a category-scale backdrop, *not* our revenue base; counting *makers who run commit-then-make* is the honest denominator. And note the category distinction from the parametric caveat above: external market structure is publicly knowable, so unlike the *unit-economics* variables (per-maker GMV, churn — calibrated only by discovery), these are **researched anchors** — but anchors are proxies and ranges, not point truths.
+
+- **TAM — every independent maker who runs commit-then-make.** Federation makes the addressable supply *the entire controllable-storefront + marketplace install base* (§7, "Strategic payoff"), not just makers willing to switch: Shopify reports ~4.8M active merchants (~2.5M live storefronts — [cropink](https://cropink.com/how-many-shopify-stores-are-there)), and Etsy ~5.6M active sellers — *down from ~9M in 2023* as it purged for quality ([Marketplace Pulse](https://www.marketplacepulse.com/stats/etsy-number-of-active-sellers)), which is the authenticity reckoning this thesis rides on, expressed as a number. Not all of these run commit-then-make; the true TAM is that subset — unknowable precisely, but **millions of makers, not thousands**.
+- **SAM — commit-then-make-native makers, reachable community-by-community.** The model only works where you show up as a member (§5), so the serviceable market is *summed over verticals*, not addressed at once. The beachhead (tabletop minis/dice, Appendix A) sits in a **~$3.8–4.2B/yr tabletop-miniatures market growing ~7–10%/yr** ([DataIntelo](https://dataintelo.com/report/tabletop-miniatures-game-market)); the relevant maker population is the independent casters/sculptors/dice-makers running drops and clubs. Patreon's **~286k paying creators** ([Backlinko](https://backlinko.com/patreon-users)) is a usable proxy for the *commit-then-make creator* population across all verticals — tabletop is one slice, and SAM grows dice → broad tabletop → adjacent craft scenes.
+- **SOM — left parametric, by design.** This is deliberately *not* a top-down "capture X% of a $Y market" number — that is exactly the fiction the "variables not values" discipline refuses. The obtainable near-term market is governed by the break-even `N* ≈ F/(m−v)` above: clear the **dozen-maker §9 demand gate** in one community, reach **break-even density (~150–300 makers under the illustrative midpoints)**, then compound vertical by vertical. The honest SOM story is *reach self-sustaining density in one scene, then repeat* — not a share of a giant pie.
+
 ### Network-health & liquidity metrics — instrumenting the §9 gates
 
 The §9 gates are all qualitative — *do makers refer you? is the pain consistent? do they have audiences? can you reach a dozen?* Those are the right questions, but the network's success is fundamentally a **liquidity** outcome (§4: curation fights liquidity, and the graveyard is full of platforms that had supply and no demand). Liquidity needs liquidity instruments.
@@ -535,7 +559,7 @@ The §9 gates are all qualitative — *do makers refer you? is the pain consiste
 - **Follower growth** — the §2 flow asset (drop-followers accumulating across makers, the embryonic cross-merchant identity graph). The leading-most signal: follows precede referred GMV by definition.
 - **Curated-By activation** — the share of verified makers who actually *vouch*, and the breadth of their curation. Referred GMV cannot exist without curators curating; a network rich in follows but where makers don't vouch is still dead.
 - **Drop sell-through** — the commitment-commerce engine's own vitality (do drops clear?). The tool-layer health the network rides on; a stalling engine starves the network upstream.
-- **Repeat-buyer rate, especially cross-maker repeat** — demand durability, and whether the buyer-side keystone (§13 #1; §8) is real. A buyer who returns *across* makers is the network effect made visible at the buyer level.
+- **Repeat-buyer rate, especially cross-maker repeat** — demand durability, and whether the buyer-side keystone (§13; §8) is real. A buyer who returns *across* makers is the network effect made visible at the buyer level.
 
 **Mapped onto the §9 gates, making each quantitative:**
 
@@ -567,15 +591,63 @@ So the model's job is to fund *enough* of that reliability core that it **surviv
 
 ---
 
-## 13. Open sections to develop (backlog)
+## 13. Demand strategy & buyer-side go-to-market
 
-This memo is deep on the architectural/strategic axes (money flow, network mechanics, moat theory, consent) and thin on several operational ones that matter as much or more. The gaps cluster on the un-fun, operational side — which is usually where ventures actually die. Each below is a separate future session. (Trust & safety, legal & compliance, and sustainability economics & health metrics were written up in prior sessions — now §10, §11, and §12 — and have left the backlog. Concrete MVP scope, the build roadmap, and the data-model sketch are intentionally *not* tracked here: this is a **strategic memo, not a roadmap/rollout doc** — those belong in the implementation plan the strategy feeds, not in the strategy itself.) Rough priority order; the **recommended next session** is the demand strategy below (#1) — the unvalidated keystone the whole thesis rests on — with §10's open reputation-engine work (gathered in that section's last subsection) the other live thread.
+The memo names demand as the unvalidated keystone everywhere — *the binding constraint* (§4), *earn into the marketplace* (§5), *the unvalidated keystone is demand, not technology* (the spine) — but never attempts a plan; everything concrete is supply-side. This section is that plan, carried to the depth the memo's own logic supports: a buyer-side value proposition stated as its own thing, where buyers actually come from, the content/community posture, and the §8 extension that tests *demand* rather than supply. It is the most consequential section because it is the keystone — and it remains, by construction, the **least validated**: the §8 interviews tested the supply/storefront-convenience layer, not this. The deliverable is the strategy and its test, not a claim that demand is proven. The section turns on OHM **trust** and **value** (the buyer's reason to return must track *earned* value, not manufactured engagement); where it names one, the canonical RFC governs (top-of-file note).
 
-1. **Demand strategy / buyer-side go-to-market — the keystone, currently only *admitted* as a risk.** The doc names "demand is the unvalidated keystone" repeatedly but never attempts a plan; everything concrete is supply-side. Needs: a crisp *buyer-side* value proposition (why a buyer shows up and comes back, stated as its own thing); a first-100 / first-1,000-buyers plan; a content/community/SEO posture for the buyer side; and a §8 extension that tests buyer demand, not just supply. Naming the risk ≠ grappling with it. (The §12 North Star — share of GMV that's cross-maker-referred — and its repeat-buyer leading indicator are the *instruments* for this; the *strategy* that moves them is still unwritten.)
+### The buyer value proposition — a three-pillar stack, not three claims
 
-2. **Governance, concretely.** The non-profit's trust rests on governance that's been floated ("open governance / maker council") but never specified: who sets and changes verification standards, board/maker representation, and how disputes about *the network itself* resolve. (This is the §10 governance-appeal-path home and the body that would steward the §12 UBIT band.)
+The buyer-side "why" is not one reason but three, each doing a different job in the funnel; the discipline is to say what each is *for*, never to lead with all three flatly (a value prop that leads with everything leads with nothing):
 
-3. **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).
+- **Authenticity / provenance — the precondition, not the magnet.** The floor that makes everything else safe. The per-item provenance badge and verification (§7) are the thing a buyer *cannot* get on a polluted Etsy, and the signal **appreciates** as AI-generated and recast fakes proliferate (§3). It is the advertised trust guarantee and the grievance-content angle — but trust is a tiebreaker/enabler, not a thing buyers wake up wanting. In the dice/miniatures beachhead (Appendix A) it runs *hottest*, because recasting is literal piracy there; the weighting across the three pillars is therefore community-dependent.
+- **The fan relationship — the acquisition-and-retention engine.** Commitment commerce, from the buyer's side, is *being a fan*: following a maker, waiting for the drop, joining the club, holding insider status. This is why the buyer is present at all (they follow a maker) and why they return (the cadence) — the §2 asset of "people who *wait for* makers and commit ahead," seen from the buyer. It is the pillar word-of-mouth carries and the one the beachhead's density compounds.
+- **Trusted discovery — the compounding mechanism.** "Makers I trust point me to makers I'll love" — Curated-By (§7) as the buyer experiences it. This is the §12 North Star (cross-maker-referred GMV) made human, and it is the *growth lever, not the entry hook*. Hard rule inherited from §7: it is framed as *emerging from makers the buyer chose to follow*, **never** as the platform performing discovery. Leading with discovery-as-destination is the curation-vs-liquidity graveyard (§4/§5) and violates *maker-as-discovery-engine, platform-as-pipe* (the spine).
+
+### Buyer surface & the "come back" mechanic — phased like the rest
+
+Mirror the §7 unified phasing — the buyer surface appears late and stays deliberately thin:
+
+- **Phase 1 — invisible / maker-fronted.** Buyers transact as guests on the maker's own storefront; attribution is stateless (§7), so no buyer identity exists yet. "Come back" runs entirely through the *maker's own* channels — the maker's ESP / IG / Discord "next drop" notice (§7, martech). The platform's only retention role is powering follow/notify; it has no buyer-facing surface and needs none.
+- **Phase 2+ — the soft destination.** The buyer-facing feed (§7) becomes an *opt-in* surface — "your makers, in one place" — with a light identity buyers return to, every item still traced to a follow. This is a retention **upgrade** layered on the maker's own channels, not a replacement, and pointedly **not** a buyer-facing *brand* a buyer evangelizes ("I shop on X") — that is the marketplace-destination posture §5/§7 reject. The platform earns a thin buyer-facing presence; it never becomes the buyer's primary relationship.
+
+### Where buyers actually come from
+
+The conclusion forced by *platform-as-pipe* (§7) and *demand must be earned, not bought* (§4): **buyers do not arrive at the platform; they arrive at makers, and the network compounds them.**
+
+- **The first ~100 are activation, not acquisition.** They are the founding (invited — §7) makers' *existing* audiences, transacting on the new rails. The platform acquires no one; the test is whether a maker's existing fans will follow them into a drop here. This is precisely why an audience-having maker is an asset and an audienceless one is a cost (§8) — restated as a buyer-acquisition fact.
+- **The first ~1,000 come from compounding plus supply.** Two engines: cross-maker propagation (a buyer who follows A discovers and follows A's Curated-By makers — the §12 cross-maker-repeat indicator), and more makers onboarding, each bringing an audience. Word-of-mouth inside the one tight beachhead (§5) is the multiplier — the reason density, not breadth, is the correct cold-start move.
+- **Net-new demand is deliberately deferred — and named, not hidden.** Everything above is *reshuffle and deepening* of audiences that already exist; the buyer feed is **by design** weak at net-new reach (§7). The two net-new hedges are scheduled, not early: **verified taste-makers (Phase 2)** are the genuine net-new-demand engine — community voices who bring *their* audiences (§7) — and **AI shopping agents (Phase 2+)** are net-new reach (§3, §7). Early demand is therefore honestly a reshuffle; pretending otherwise is the graveyard's mistake (§4). *Concede the timeline, not the moat* (§8).
+
+### Content, community & SEO posture
+
+The §5 *member, not vendor* principle applied to demand — and an explicit rejection of the marketplace-SEO play:
+
+- **Embed in the beachhead's existing hubs; don't broadcast.** Show up inside the tabletop Discords, subreddits, painting forums, and conventions as a member of the scene (§5) — the same standing that recruits makers recruits buyers.
+- **Maker-amplified, not platform-voiced.** The platform's owned content surface is the network digest (§7, network marketing channel): followed makers' drops plus their Curated-By picks, aggregated and personalized but never platform-injected. Buyer-side SEO accrues to *makers' own* verified-provenance product pages, not a marketplace landing page — competing with Etsy/Amazon on generic "shop handmade" search is unwinnable and off-strategy (the discovery war §7 declines to fight).
+- **One native editorial voice: the authenticity grievance.** "How to spot a real cast," provenance explainers, the anti-recast / anti-AI-slop story — community-native in the beachhead, doubling as SEO and values signaling. Plus the **verified badge as a portable trust mark** makers display wherever they already are (their IG, their leaving-Etsy posts), pulling buyer awareness back to the verified graph.
+
+### The §8 extension — test demand, not supply
+
+§8 discovery talked only to makers, and the two interviewed were *greenfield, with no audience* (§8) — so it tested the supply/storefront-convenience layer and **could not test the demand moat at all** (you cannot measure "do a maker's fans follow them here" with makers who have no fans). The buyer-side extension must therefore:
+
+- **Recruit audience-having makers specifically** — a different discovery target from the greenfield on-ramp. The demand moat can only be probed where an audience exists to move.
+- **Test behaviorally, not by survey** (§8's *weight what makers do over what they say*, carried to buyers): run a real instrumented drop; run a Curated-By referral between two makers and measure click → follow → buy **propagation** (the keystone network assumption, made measurable); measure provenance's effect on willingness-to-pay / switch; track repeat and cross-maker-repeat (§12).
+- **Avoid the Shop Pay measurement trap (§8).** Don't ask buyers what they'd value — measure the driver: the repeat-fan vs. first-time-stranger revenue mix, and whether buyers already carry a recognized cross-merchant identity.
+- **Feed the §9 gates and §12 instruments.** These tests populate the very inputs §12 said the dozen-maker gate should start instrumenting (per-maker GMV, referred share, repeat rate) — the demand strategy and the health metrics are the same build, validated together.
+
+### The through-line
+
+The keystone, finally grappled with rather than admitted: **buyers arrive at makers, and the network compounds them** — so the value prop is a three-pillar stack (authenticity the precondition, the fan relationship the engine, trusted discovery the compounding), the surface stays maker-fronted and only *softly* a destination, net-new demand is honestly deferred to taste-makers and agents, and the §8 extension tests it **behaviorally, with audience-having makers, before the platform is built.** It is the most consequential section and remains the least validated — by design, that is the next thing to *earn*, not assume.
+
+---
+
+## 14. Open sections to develop (backlog)
+
+This memo is deep on the architectural/strategic axes (money flow, network mechanics, moat theory, consent) and thin on several operational ones that matter as much or more. The gaps cluster on the un-fun, operational side — which is usually where ventures actually die. Each below is a separate future session. (Trust & safety, legal & compliance, sustainability economics & health metrics, and demand strategy & buyer-side go-to-market were written up in prior sessions — now §10, §11, §12, and §13 — and have left the backlog. Concrete MVP scope, the build roadmap, and the data-model sketch are intentionally *not* tracked here: this is a **strategic memo, not a roadmap/rollout doc** — those belong in the implementation plan the strategy feeds, not in the strategy itself.) Rough priority order; with the demand keystone now drafted (§13, still to be *validated* via its §8 extension), the **live threads** are §10's open reputation-engine work (gathered in that section's last subsection) and the governance mechanics below (#1) — whose *direction* (progressive delegation to network representatives; §7/§10) is now set, but whose machinery is deliberately deferred.
+
+1. **Governance — progressive delegation (direction set; mechanics deferred).** *Direction set:* a **layered hybrid**. The non-profit (its board, with fiduciary duty) retains the **legal floor and the entrenched core** — the trust guarantee, non-extraction, the no-walled-garden value rule, the out-of-flow stance — which *bind with structure*, not a changeable majority (a 501(c)(3) cannot sell or distribute them — §7). Authority over **maker issues** (verification standards, the provenance line, the §10 standing thresholds — §7, §10, §14 #2) is **progressively delegated to representatives of the network as it scales beyond what the non-profit can manage**, on the same *start-closed, open-as-the-trust-web-earns-it* phasing as the membership gate and peer verification (§7): founder/staff-led at launch, delegated as density demands. The vision is **network self-governance for maker issues, modeled on a functioning democracy**: members *elected* to network roles — dispute-resolution among them — where **holding and discharging a role well is itself a way to earn standing**, the same reputation currency as making and vouching well (§10's positive-reinforcement model). It is also how the org *scales* without the volunteer core adjudicating every dispute (§12). *Still open — and deliberately not fleshed out now:* what those representative bodies are and how they're constituted, how delegation resists capture (the §7 verification concern applied to governance itself), and the concrete appeal/dispute machinery (the §10 governance-appeal-path home). Over-specifying a governance apparatus before the community exists would be premature; the direction is set, the machinery is later work. (Also the body that stewards the §12 UBIT band.)
+
+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).
 
 ---
 
@@ -601,15 +673,24 @@ The platform serves makers in general, but it must *launch* into one dense commu
 
 ## Appendix B — The commitment-commerce layer: incumbents & the open gap
 
-"This feels Kickstarter-ish" is correct, and the incumbents are specific. The crowdfunding/pledge-management space is large, mature, and consolidating — but built for **episodic, project-scale campaigns**, not an individual maker's **continuous drop cadence.** That distinction is the entire opening. (The pattern: every incumbent started as the tool managing the gap between committed demand and delivery — pledge management — then grew up into the funding layer.)
+"This feels Kickstarter-ish" is correct, and the incumbents are specific. The crowdfunding/pledge-management space is large, mature, and consolidating — but built for **episodic, project-scale campaigns**, not an individual maker's **continuous drop cadence.** That distinction is the entire opening — with one correction this appendix originally missed: there are **two** incumbent shapes, not one. The *episodic* campaign players below (Kickstarter / Gamefound / BackerKit), and — easy to miss because it doesn't look like crowdfunding — the *continuous-membership* incumbent, **Patreon**, which already serves the monthly-club primitive and sits *inside* the beachhead (its own treatment after the table). (The pattern for the campaign players: every one started as the tool managing the gap between committed demand and delivery — pledge management — then grew up into the funding layer.)
 
 | Player | What it is | Built for | Relevance |
 |---|---|---|---|
 | **Kickstarter** | All-or-nothing campaign crowdfunding; no integrated pledge manager | Episodic, project-scale campaigns | The launchpad |
 | **Gamefound** | Tabletop-native; pledge-manager → full crowdfunding platform with late-pledge stores | Episodic tabletop campaigns + post-campaign stores | **Sitting in your adjacent vertical**; fast-growing, Kickstarter's biggest tabletop rival |
 | **BackerKit** | Pledge-manager (surveys/shipping/tax/add-ons) → also crowdfunding | Post-campaign fulfillment + campaigns | "Mission control" for fulfillment |
+| **Patreon** | Per-creator recurring memberships; platform is MoR, processes the charge (~8–12% all-in), pays out | **Continuous** creator membership (the monthly club) | **The recurring-club incumbent — and it's *inside* your beachhead** (the Patreon/Cults3D model in minis, Appendix A); a sharper competitor than Shopify for the club slice, on the wrong side of three invariants — treatment below |
 
-**The open gap (where to play):** none of these serve the maker running a small drop every other Saturday, a monthly made-to-order club, or a 10-piece lottery. The unserved space is **continuous commitment-commerce cadence** — the recurring, relationship-driven, small-batch motion *between* Shopify (continuous but stock-only) and Kickstarter/Gamefound (commitment but episodic). The recurring strategic shape (the same as the rest of this memo): there's always an entrenched incumbent owning the *episodic/distribution* layer — Shopify (stock), MyMiniFactory (file distribution), Gamefound (campaigns) — and the open prize is the *continuous cross-maker relationship* layer they don't serve. **Coexist with the episodic incumbent; own the continuous demand-relationship network.**
+**The open gap (where to play):** none of these *campaign* players serve the maker running a small drop every other Saturday or a 10-piece lottery — and the **monthly club**, the one continuous-cadence slice that *does* have an incumbent, is served by **Patreon** on the wrong side of the invariants (below). The unserved space is **continuous commitment-commerce cadence** — the recurring, relationship-driven, small-batch motion *between* Shopify (continuous but stock-only) and Kickstarter/Gamefound (commitment but episodic). The recurring strategic shape (the same as the rest of this memo): there's always an entrenched incumbent owning the *episodic/distribution* layer — Shopify (stock), MyMiniFactory (file distribution), Gamefound (campaigns) — and the open prize is the *continuous cross-maker relationship* layer they don't serve. **Coexist with the episodic incumbent; own the continuous demand-relationship network.**
+
+**Patreon — the continuous-membership incumbent inside the beachhead.** Patreon is *not* §2's stock-then-sell foil the way Shopify is: a monthly club is already *commit-then-make* (patrons commit ahead; the creator produces against it), so Patreon is genuinely doing this category for the recurring-club/membership primitive (§2, §6, §7) — and in miniatures it's the de-facto infrastructure (the "Patreon / Cults3D model", Appendix A). That makes it a *sharper-edged* competitor than Shopify for the slice it touches, and an unavoidable one: your first community lives on it. But it sits on the wrong side of three invariants at once —
+
+- **In the money flow.** Patreon is MoR, processes the recurring charge, takes ~8–12% all-in, and pays out — precisely the thing §7/§11 design out. A native replacement must keep the maker MoR on their own processor (Stripe Billing on a **Standard account + direct charges + `application_fee`**, §7). *Recurring billing is the sharpest test of that dial*, because Patreon's whole model is "platform is MoR for a subscription" — one config-flip away, and the flip would quietly rebuild Patreon.
+- **A walled garden on the buyer.** Run Patreon through Appendix D's three-surfaces gate and it scores like **Etsy, not Shopify**: you can't host a Curated-By block on a Patreon page, you can't attribute a referral through Patreon checkout, and Patreon owns the patron payment relationship. By the value rule it's an **invitation target, not an integration/destination** — "I'd feature your work the moment you own your commerce." The one federatable seam is **patron-email export → seed the maker's ESP** (§7, ESP-as-source-of-truth): billing and delivery you want native, the *list* you can lift.
+- **No moat, and structurally can't grow one.** Patreon is single-creator; its cross-creator discovery is platform-performed engagement-algo — the inverse of *maker-as-discovery-engine* (§7 buyer feed) — with zero reputation-staked, attributed cross-maker referral. It won't build that, for the same *shape* of reason Shopify won't (§7, "Why this is the defensible core") but a different specific one: its business *is* the captive recurring relationship and the algorithmic discovery surface. So it contributes nothing to your North Star (§12, cross-maker-referred GMV) — every patron on Patreon is a follow you never capture into the cross-maker identity graph.
+
+**The play is two-sided, and already latent in the sequencing (§5).** *Act 1 (Tool) — out-tool it:* the engine already lists "recurring clubs/memberships" + "digital-file delivery + licensing" as primitives (§2, §6); for minis that *is* the Patreon feature set (monthly STL drop, tiered licensing, patron list). Build it **maker-MoR**, grant **usage-rights ownership of the patron** (§7 — the exact inversion Patreon doesn't offer), lower the all-in fee, and wire it into the network. (Appendix-A discipline holds: don't build a Cults3D/MyMiniFactory *file marketplace* — "partner/coexist; don't build" — but the club mechanic + storefront + network layer is yours.) *Act 2+ (Network) — out-flank it:* the cross-maker referral/feed is the durable reason a maker prefers you **even if Patreon matched the club features** — which it can't, without becoming a different company.
 
 ---
 
@@ -687,6 +768,7 @@ Legend: ✓ supported · ◐ partial/limited · ✗ not supported.
 | **Etsy** | ◐ Open API v3 — *unused as a destination by value rule* | ✗ can't modify the page | ✗ **value rule** — invitation target only | ✗ Etsy owns checkout | ✗ Etsy owns the buyer | ✗ Etsy's decision |
 | **eBay** | ◐ APIs (read) — *unused* | ✗ can't modify the listing | ✗ value rule; invitation target | ✗ eBay owns checkout | ✗ eBay owns the buyer | ✗ eBay's decision |
 | **Amazon Handmade** | ✗ gated/restricted API | ✗ zero storefront control | ✗ value rule + Amazon owns all; invitation target | ✗ Amazon owns checkout | ✗ Amazon owns the buyer (most completely) | ✗ Amazon's own agents treat you as a competitor |
+| **Patreon** *(membership)* | ◐ API reads tiers/posts — *unused as destination by value rule* | ✗ can't host a Curated-By block on the page | ✗ value rule; invitation target | ✗ Patreon is MoR for the subscription | ✗ Patreon owns the patron — *one seam: email export* | ✗ Patreon's decision |
 
 The table's shape *is* the thesis: **controllable storefronts ✓ across; walled gardens ✗ across.** Not a coverage gap — a restatement of who the network is *for* (makers who own their commerce, or will) and what it's an alternative *to*.
 
@@ -694,6 +776,8 @@ The table's shape *is* the thesis: **controllable storefronts ✓ across; walled
 
 **Walled gardens are who you're an alternative to — not a gap to cover.** A maker deep in Amazon Handmade who can't participate is the person the pitch is *aimed at*, who hasn't left yet. The right move is **invitation, not integration**: "I'd feature your work the moment you own your commerce" — the absence of a link is the recruiting signal, making membership the price of inclusion rather than subsidizing captivity. Notes: Etsy is the *most permissive* walled garden (Open API v3, models made-to-order, runs an affiliate program) but the value rule forecloses using it as a buyable destination anyway; a maker on *both* Etsy and a controllable storefront participates via the controllable one. Amazon Handmade is the most walled and the most hostile (restricted API, total buyer ownership, its own agentic-commerce ambitions). The **verification inversion** becomes a recruiting message: "we'd vouch for your work — verified independent of any marketplace's compromised badge — the moment you own your commerce."
 
+**Patreon is the *membership-side* walled garden — the gap this table originally missed.** Every other walled garden above is a *transactional* marketplace (one-shot sales); Patreon applies the identical captive-commerce model to *recurring relationships*, and — unlike Etsy/Amazon for most makers — it is the **actual home of the beachhead audience** (Appendix A; the recurring-club incumbent, Appendix B). On the three-surfaces gate it scores like Etsy, not Shopify: no page control (no Curated-By block), no checkout control (no referral attribution — Patreon is MoR for the subscription), no buyer ownership (Patreon owns the patron) — the lone federatable seam is **patron-email export → seed the maker's ESP** (§7). So the Patreon posture is the same **recruit-out, don't integrate** rule, but materially more load-bearing than the Etsy one the memo otherwise leads with: the tension to face head-on is that *your first community lives on the very walled garden you are recruiting them off of* (§4). The answer is the two-sided play in Appendix B — **replace the club** (native, out-of-flow, maker-MoR) **+ lift the list + out-flank with the network.**
+
 ---
 
 ## Recurring principles (the spine)