wiggleverse/wiggleverse-ecomm
2
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

SD-0001: Solution Design — MVP sign up and create a single storefront (Feature #1) #2

Merged
ben.stull merged 12 commits from claude/optimistic-lumiere-ef8b1e into main 2026-06-10 14:12:57 +00:00
Conversation 0 Commits 12 Files Changed 1
+1059
ben.stull commented 2026-06-10 14:12:44 +00:00
Owner
Copy Link
Copy Source

Solution-Design spec for Feature #1 (#1), authored section-by-section in brainstorming session ecomm-0020 (one commit per section for targeted review).

Decides the clean-rebuild architecture: 4-layer modular monolith carried forward from the prototype, open email+OTC sign-up (no admission gate), no seeded tenant (empty persistence is a working state), many-capable membership schema with a service-level one-storefront rule, REST-only BFF, and the localhost/PPE/Prod bootstrap story. Delivery cut into SLICE-1..4.

Submitted to wiggleverse-ecomm-content/specs/ at session finalize.

Solution-Design spec for Feature #1 (#1), authored section-by-section in brainstorming session ecomm-0020 (one commit per section for targeted review). Decides the clean-rebuild architecture: 4-layer modular monolith carried forward from the prototype, open email+OTC sign-up (no admission gate), no seeded tenant (empty persistence is a working state), many-capable membership schema with a service-level one-storefront rule, REST-only BFF, and the localhost/PPE/Prod bootstrap story. Delivery cut into SLICE-1..4. Submitted to wiggleverse-ecomm-content/specs/ at session finalize.
ben.stull added 12 commits 2026-06-10 14:12:44 +00:00
spec(skeleton): SD-0001 front matter + section skeleton from solution-design TEMPLATE c7b288a81b 
Anchors wiggleverse-ecomm#1; authored in session ecomm-0020.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§1.1–1.5): business context — summary, background, actors, problem, pains 42dbc5048a 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§1.6–1.9): outcomes, business scope, assumptions, business use cases BUC-1..5 a68f59ac85 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§2): solution proposal — carry forward prototype shape, invert seed/gate, defer GraphQL+OAuth 7147e740a1 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§3–4): product personas + product use cases PUC-1..11, grounded in corpus 14.01.* / 01.01.0008 a32061ac54 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§5): UX layout — landing, sign-in (2-step), create-storefront, admin shell e68692840f 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§6.1–6.4): invariants INV-1..9, architecture, data model, API contracts d8abd5c1d5 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§6.5): per-PUC design — entry routing spine, auth + storefront sequences, bootstrap 0881a4cdf0 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§6.6–6.9): NFRs, key decisions table, testing strategy, failure modes b2e1f11a85 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§7): delivery plan — SLICE-1..4 (skeleton, identity, storefront, deployed envs), rollout, risks 3120349fc5 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(§8–10): traceability matrix, open questions + decisions log, glossary & references a6d9bdf135 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spec(self-review): declare storefronts participant, fix §1.8 cross-ref, status → approved (v0.2.0) 45f6ef8b58 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ben.stull merged commit 23afcf95ce into main 2026-06-10 14:12:57 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
priority/P0
Priority: highest — drop everything
 priority/P1
Priority: high
 priority/P2
Priority: medium
 priority/P3
Priority: low / someday
 type/bug
Type: a defect in shipped behaviour — small leaf work, straight to a plan
 type/epic
Type: a large body of work spanning many features
 type/feature
Type: a deliverable capability under an epic
 type/story
Type: a user story — the smallest valuable increment
 type/task
Type: a concrete unit of work under a story
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ben.stull (Ben Stull) ohm-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiggleverse/wiggleverse-ecomm#2
Delete Branch "claude/optimistic-lumiere-ef8b1e"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?