ben.stull
c5f9f11591
Break the partner-compensation model out of the "Business model" subsection into a dedicated §7 "Partner / consultant network: onboarding the high-touch tail" subsection. Add the money-flow clarification: the referral-income split is the only leg the network settles (principal-on-both-sides, out of flow); any upfront cash, setup fee, retainer, milestone, or other agreement is a direct off-platform deal between maker and partner — the network never takes custody (custody is the line). Tooling may record an off-network term (coordination) but never moves it. 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.