ben.stull
4d8daad6b7
Surface from the strategy memo into the PR-FAQ four answers a launch reviewer would expect the doc to stand on its own for: - per-item provenance mechanism (§7/§10/§11): classes, trust-surface eligibility, misclassification = de-verification, FTC substantiation - trust & safety: buyer pre-order/ghosting recourse (§10/§11) and the anti-collusion / rooted-trust-graph architecture (§7/§10) - the episodic-campaign incumbents — Kickstarter/Gamefound/BackerKit — via the campaign-vs-cadence distinction (Appendix B) - replace the "X%" pricing placeholder with worked illustrative all-in numbers; fix the imprecise "~20% more of every sale" subhead 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.