116 lines
7.2 KiB
Markdown
116 lines
7.2 KiB
Markdown
# Session 0012.0 — Transcript
|
||
|
||
> App: ecomm
|
||
> Start: 2026-06-03T19-45 (PST) · End: 2026-06-03T20-25 (PST)
|
||
> Goal: Cluster the full ecomm BDD corpus into dependency-ordered, parallelizable releases.
|
||
> Outcome: `ROADMAP.md` (60 releases, 5 waves) generated + merged to main; generator committed to meta.
|
||
|
||
_(Start time is an estimate — this session was not run through `wgl-coding-session-init`,
|
||
so no claim happened at the real start; the ID 0012 was claimed during finalize.)_
|
||
|
||
## Plan
|
||
|
||
Operator had a large BDD corpus and wanted it clustered into ordered work units (releases),
|
||
parallelizable where domains don't intersect. Plan that emerged:
|
||
|
||
1. Locate the corpus, understand the domain/feature/dependency structure.
|
||
2. React to the operator's "non-intersecting domains → parallel" heuristic; refine it to
|
||
"dependency DAG over scenarios" (non-intersection governs merge-safety; the DAG governs order).
|
||
3. Decide unit grain (feature-level), gated scope (park `credits`), output location (`ecomm/ROADMAP.md`).
|
||
4. Build a feature-level dependency graph, topo-level it into waves, group by domain into parallel tracks.
|
||
5. Generate `ROADMAP.md` deterministically from `scenarios.json` + the graph (no hand-typed numbers).
|
||
6. Commit (branches), then on finalize: merge both to main, update memory, publish this transcript.
|
||
|
||
## Pre-session state
|
||
|
||
- `wiggleverse-ecomm` on `main`, clean. R01–R03 shipped (store/settings, staff, locations core),
|
||
layered backend (`app/platform | domains | api`) with import-linter. CI workflow present but
|
||
inert (no Gitea runner registered).
|
||
- The BDD corpus was **not** in the ecomm repo — it lives in
|
||
`wiggleverse-ecomm-meta/research/shopify/` as 68 `.md` feature files plus a machine-readable
|
||
`scenarios.json` (1,238 scenarios, 15 domains) and `shopify-domain-map.md` (carries an explicit
|
||
per-domain `Depends On` column).
|
||
- Key reconciliation discovered: the ecomm `13.NN.*` mechanic IDs = the **`settings`** domain.
|
||
R01 = `settings/general` (13.06), R02 = `settings/users-and-permissions` (13.15),
|
||
R03 = `settings/locations` (13.07, 4 of 9 scenarios). So the real release cadence has been
|
||
**per-feature**, not per-domain.
|
||
|
||
## Turn-by-turn arc
|
||
|
||
1. **Framing.** Operator proposed: a release = stories from ≥1 feature in a domain; parallelize
|
||
while domains don't intersect. Invoked the brainstorming skill (process-first). Read SPEC.md +
|
||
MAP.md to ground the reaction.
|
||
2. **Refinement delivered.** Argued the binding constraint is the **dependency DAG**, not mere
|
||
non-intersection: two disjoint domains can still be force-ordered (checkout→orders→products).
|
||
Noted the SPEC already does the sophisticated version — R03 shipped only the dependency-free
|
||
subset of locations and deferred the rest. Flagged migrations as a serialization point and the
|
||
shared §7–§8 auth gate as a non-disjoint substrate.
|
||
3. **Corpus located.** Operator pointed at `wiggleverse-ecomm-meta/research/shopify`. Explored:
|
||
no `.feature` files — instead structured `scenarios.json`. Mapped the 15-domain / 68-feature
|
||
distribution; read the domain map's dependency column and the id-registry feature numbering.
|
||
4. **Three decisions (AskUserQuestion).** Unit grain = **feature-level**; gated scope = **park
|
||
credits only** (59 scenarios, SPEC §6 money-transmission gate); output = **`ecomm/ROADMAP.md`**.
|
||
5. **DAG + leveling.** Hand-authored a feature-level dependency graph (commerce domain knowledge +
|
||
the domain map), encoded it in Python, topo-leveled into 5 waves, grouped by domain into parallel
|
||
tracks. Result: 60 releases R04–R63. Wave widths 5/8/12/8/2; critical path 5 deep
|
||
(`products → orders → shipping+taxes → international-markets → localized-pricing`).
|
||
6. **Design approved.** Presented wave structure + six load-bearing judgment calls (orders-depends-
|
||
on-products-only; customer-list as foundation; broke the payments↔checkout cycle; gift-cards vs
|
||
the parked credits gate; onboarding placed late; the 5 deferred R03 location scenarios ride along
|
||
later releases). Operator: "That's fine. We'll revisit after the first several releases."
|
||
7. **Generated + committed.** Wrote `gen_roadmap.py` (after a first heredoc attempt hit a bash/Python
|
||
quote-escaping `SyntaxError` — fixed by writing the script to a file). Generated `ROADMAP.md`.
|
||
Self-review: totals reconcile (1151 sequenced + 59 parked + 28 shipped = 1238); no forward refs.
|
||
Committed each on a branch (ecomm + meta).
|
||
8. **Finalize.** Operator chose: push + **merge both to main now**; **create + publish** a transcript.
|
||
Fast-forward merged both, pushed, deleted branches; updated memory; drafted next-session prompt;
|
||
claimed session 0012 and published this transcript.
|
||
|
||
### Wrong turns / corrections (no curation)
|
||
|
||
- **Miscounted sequenced scenarios as "1,179"** in the verbal summary; the generator's correct
|
||
**1151** revealed the error (I'd forgotten to subtract the 28 already-shipped R01–R03 scenarios).
|
||
1151 + 59 parked + 28 shipped = 1238. ✓
|
||
- **Heredoc generator failed** first try: `<< 'PY'` passed `\"` literally into Python f-strings →
|
||
`SyntaxError`. Switched to writing `gen_roadmap.py` as a file (also made it rerunnable — the right
|
||
call anyway).
|
||
|
||
## Cut state (end of session)
|
||
|
||
| Repo | Branch | Commit | Change | Remote |
|
||
|------|--------|--------|--------|--------|
|
||
| `wiggleverse/wiggleverse-ecomm` | `main` | `c426600` | add `ROADMAP.md` (60 releases, 5 waves) | pushed (ff `933733d..c426600`) |
|
||
| `wiggleverse/wiggleverse-ecomm-meta` | `main` | `6758b80` | add `research/shopify/gen_roadmap.py` | pushed (ff `c4c4f4e..6758b80`) |
|
||
|
||
Both feature branches (`docs/roadmap-release-clustering`, `docs/roadmap-generator`) merged
|
||
fast-forward and deleted. Both working trees clean. No code written — planning artifact only.
|
||
|
||
## What lands on the operator's plate
|
||
|
||
- **Review `ROADMAP.md`** at leisure; it's explicitly a living doc to revisit after the first few
|
||
releases. The six judgment calls (esp. #1 orders-timing, #5 onboarding placement) are the likely
|
||
edges to move.
|
||
- **Standing infra gap (unchanged):** no Gitea Actions runner → `ci.yml` inert; no branch protection
|
||
on `main`. Not addressed this session.
|
||
- Nothing broken, nothing blocked.
|
||
|
||
## Prompt the operator can paste into the next session
|
||
|
||
```
|
||
Start the next wiggleverse-ecomm release. First run /wgl-coding-session-init to claim a
|
||
session ID and confirm a clean main baseline.
|
||
|
||
Context: R01–R03 are shipped/merged. The full 1,238-scenario BDD corpus is now sequenced in
|
||
wiggleverse-ecomm/ROADMAP.md into 60 feature-level releases (R04–R63, 5 dependency waves).
|
||
Read that file + the memory project_ecomm_build.md for state.
|
||
|
||
Build a Wave-1 opener (both fully unblocked, no deps):
|
||
• R07 products — foundation / critical-path root, 37 scenarios 11.05.0001–0037 (unblocks the
|
||
most downstream work); scenarios in wiggleverse-ecomm-meta/research/shopify/products/products.md
|
||
• R04 content/files — smaller start, 21 scenarios 03.02.0001–0021
|
||
|
||
Follow the SPEC/CONTRIBUTING discipline: new domain package under app/domains/, both API
|
||
projections + shared auth gates, cite the OHM concept per mechanic, one BDD scenario → one test,
|
||
keep scripts/check.sh green. Branch off main; push before PR review (operator merges).
|
||
```
|