daniel/deepdrft
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 13 Wiki Activity

docs: resolve 3 Phase 9 open questions from Daniel

Browse Source 
Genre browse stays route-reachable (deprioritized, not retired).
Session/Mix single-track is a hard upload constraint.
/albums redirects to /cuts when CUTS lands.
This commit is contained in:
daniel-c-harvey
2026-06-12 17:39:30 -04:00
parent 0b349da5f8
commit c1271aeb90
2 changed files with 6 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
product-notes/phase-9-release-medium-types.md
+3 -9
View File
@@ -426,26 +426,20 @@ above-the-fold without polluting the others.
1. **Waveform storage shape (§2.3).** Vault blob + `WaveformEntryKey` (recommended) vs. JSON column
on `MixMetadata`. Determines whether Wave 1 touches the vault abstraction. *Recommend vault blob.*
2. **Genre browse fate (§3.1).** "Rename the Genre tab to Release Archive" takes the third tab's
slot. Does genre browsing survive (route-reachable but tab-less — recommended), move under the
Cut browser as a secondary filter, or retire in the CMS? *Recommend keep route-reachable.*
2. **Resolved: Genre browse fate (§3.1).** Daniel's decision: the Genre tab slot is taken by Release Archive (Wave 3A as specced); the existing genre browse functionality is deprioritized and stays route-reachable as-is — no active development, no retirement. The team should not remove it.
3. **Waveform preprocessor reuse (§3.4).** Is the existing player-bar waveform preprocessor factored
to accept a resolution parameter, or does Wave 3 track C include a refactor to share one pipeline
across player-bar (low-res) and Mix (high-res)? *Recommend one parameterized pipeline.*
4. **Detail-page strategy (§5.3).** Three separate detail pages vs. one branching `TrackDetail` vs.
shared `ReleaseDetailScaffold` + per-medium hero slot (recommended). Sets the public-site Wave 4
shape. *Recommend the scaffold.*
5. **Old releases route (§5.2).** Does the current Releases/`AlbumsView` route redirect to `/cuts`,
or stay as an all-media view? *Small routing call.*
5. **Resolved: Old `/albums` route fate (§5.2).** Daniel's decision: when `/cuts` lands, the existing `/albums` route issues a redirect to `/cuts`. Old URLs keep working; no hard 404.
6. **Nav model children (§5.1).** Extend `MenuPages` with an optional `Children` collection
(recommended, generalizes) vs. hardcode ARCHIVE as a bespoke popover component. *Recommend the
model extension.*
7. **`MixWaveformVisualizer` seek-on-click (§5.4).** Design the position-binding seam now even if
click-to-seek ships later? *Recommend design the seam, defer the feature.*
8. **Single-track invariant for Session/Mix (§3.3).** Sessions and Mixes are "single-track." Is that
a hard constraint enforced at upload (one track per Session/Mix release), or a convention? If
hard, the CMS upload form for those media should drop the multi-track master list entirely.
*Recommend enforce — it simplifies both the form and the detail view.*
8. **Resolved: Single-track invariant for Session/Mix (§3.3).** Daniel's decision: hard constraint. One track per Session/Mix release is enforced at upload — the CMS form for those media drops the multi-track master list entirely.
---