08a38879371fa5eca793359d8313b3cfb352f5c5
PR-FAQ (Tier-2 reviewer gaps): - Shopify-copies-the-tool: first-class-not-hard framing + cuttle.xyz/LLM-tool integration headroom; 'tool is the wedge, network is the moat' - featured maker's (B-side) consent + economics - ballpark F (~$75-150k/yr) and the 'F is not the cloud bill' reliability core - operational drop-time reliability (blast radius + funded core) Referral-model evolution (PR-FAQ + memo, source-of-truth reconciled): - platform spread stays FIXED (~3-5%, $-capped) — the network's referral revenue line, unchanged in §12 - Maker A's reward becomes NEGOTIABLE above the spread (flat/tiered/max-$ cap, renegotiable), floored at the spread; maker<->maker only - per-relationship approval: B must approve being curated by A - ranking-neutrality as a STRUCTURAL guarantee: platform ranks for conversion but never by referral economics, credible because its spread is constant - non-maker taste-makers keep uniform, non-biddable rates (peer-respect counterweight absent) Memo ports: §2 (first-class/cuttle), §7 Curated-By guardrails + Referral economics + catalog-presence + taste-maker tier, §7 partner comp, §12 spread + Goodhart guardrails. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
wiggleverse-ecomm-content
Content/corpus repo for the ecomm app (clean implementation, started
2026-06-10). The application code lives in the sibling
wiggleverse-ecomm
repo.
Layout
| Path | Holds |
|---|---|
specs/ |
reviewed Solution-Design specs (submitted at session finalize) |
plans/ |
archived implementation plans |
ui/designs/ |
UI-design artifacts (Claude Design outputs), referenced from specs |
Roadmap and the deployment version pin will be added as the build gets underway.
The first-pass reference prototype's content (including the harvested Shopify
BDD corpus) lives separately in
wiggleverse-ecomm-prototype-content.
Description
Languages
JavaScript
94.9%
CSS
3.9%
HTML
1.2%