Parked: Mirror FreshVibe Way v6 and v7 to gallery (per-version convention)
Status: PARKED (not in current sprint)
Parked by: Mavis
Parked on: 2026-07-22
Related decision: D-2026-07-22-fvw-canonical-home-is-gallery.md
Reason for parking: operator said "make a plan to do it but park it" — current sprint is FVW v8 canonical-home rollout + Layer 9 sync protocol. v6/v7 mirror is historical-record work, not blocking anything.
---
Why park it (and not skip it)
Per D-2026-07-22, the gallery is the canonical home of all FVW versions. The per-version subfolder convention means each FVW version gets its own subfolder:
- `avidtech6/fv-module-gallery/gallery-pact/fvw/v6/` — historical v6
- `avidtech6/fv-module-gallery/gallery-pact/fvw/v7/` — historical v7
- `avidtech6/fv-module-gallery/gallery-pact/fvw/v8/` — current (8.1.0)
For consistency, ALL historical versions should be mirrored to the gallery, not just the current v8.
Currently the gallery has only v8/. The fvs has freshvibe-way-v6/, freshvibe-way-v7/, and freshvibe-way-v8/. The fvs side already has the per-version structure; the gallery side is incomplete.
This is cosmetic consistency, not functional. v6 and v7 are frozen snapshots. v8 is the only active version. So this work can wait.
---
The plan (when un-parked)
Goal
Mirror avidtech6/freshvibestudio/pact/freshvibe-way-v6/ and pact/freshvibe-way-v7/ to the gallery at avidtech6/fv-module-gallery/gallery-pact/fvw/v6/ and gallery-pact/fvw/v7/, so the per-version convention holds across the full history.
Step 1: Read the v6 and v7 folders in fvs
Files to mirror (confirmed 2026-07-22):
- `pact/freshvibe-way-v6/` — 21 files, no subdirs
- `pact/freshvibe-way-v7/` — 33 files, no subdirs
The fvs side already has the structure; no creation needed.
Step 2: Determine the gallery destination
For each v<N>:
- Source: `avidtech6/freshvibestudio/pact/freshvibe-way-v<N>/`
- Destination: `avidtech6/fv-module-gallery/gallery-pact/fvw/v<N>/`
Per-version subfolder layout: gallery-pact/fvw/v<N>/.
(Note: I'm using fvw (FreshVibe Way) for the gallery subfolder, not fw8. Earlier drafts had fw8/ which I now realise is a typo / was a draft. fvw/ is the correct short form. Confirm this with the operator when un-parked, or look at the v8/ subfolder naming convention that just got established.)
Step 3: Decide on the README + VERSION + CHANGELOG treatment
Two options:
Option A: Mirror as-is (no additions)
- Just copy the 21 (v6) and 33 (v7) files verbatim
- No README updates, no CHANGELOG, no VERSION
- Pro: minimal work, matches the original
- Con: these historical versions are missing the canonical-home banner and Layer 9 (FVW-SYNC-PROTOCOL) that the v8 mirror has
Option B: Mirror + add provenance banner
- Copy the files
- Add a short `README.md` in each v<N>/ explaining "this is a frozen snapshot of FVW v<N>, see v8/ for the current version"
- No CHANGELOG, no VERSION (they didn't exist in v6/v7)
- Pro: each version is self-explanatory
- Con: small extra work
Recommendation: Option B — each version subfolder gets a minimal README.md (5-10 lines) saying it's a frozen historical snapshot + a link to v8. This costs almost nothing and prevents confusion ("wait, is this the current version?").
Step 4: For each v<N>:
- Create the destination folder: `gallery-pact/fvw/v<N>/`
- Copy all files from `pact/freshvibe-way-v<N>/` to the destination
- Write a 5-10 line `README.md` in the destination, with:
- "FVW v<N> — FROZEN HISTORICAL SNAPSHOT"
- "Captured: <date>"
- "Current version: see v8/"
- "Mirror of: avidtech6/freshvibestudio/pact/freshvibe-way-v<N>/"
- (Optional) Add a `FROZEN-AT.txt` with the freeze date
Step 5: Update the gallery README/STATUS
- Add a sentence to `gallery-pact/STATUS.md` mentioning v6 and v7 are now also mirrored
- Add a sentence to `gallery-pact/fvw/README.md` listing v6, v7, v8 as available versions
Step 6: Verify
- Run a byte-equality check between `pact/freshvibe-way-v<N>/` and `gallery-pact/fvw/v<N>/` for v6 and v7
- All files should match
Step 7: Commit
- Commit message: `Mirror FVW v6 and v7 to gallery (per-version convention)`
- Files touched:
- avidtech6/fv-module-gallery/gallery-pact/fvw/v6/ (new, ~21 files + 1 README)
- avidtech6/fv-module-gallery/gallery-pact/fvw/v7/ (new, ~33 files + 1 README)
- avidtech6/fv-module-gallery/STATUS.md (updated)
- avidtech6/fv-module-gallery/gallery-pact/fvw/README.md (updated)
Estimated effort
- 30 minutes (mostly copy-paste + verify)
- 0 risk (frozen snapshots, no functional change)
- 0 dependencies (can be done any time)
---
When to un-park
Un-park this when ANY of the following is true:
- Operator says "now do v6 and v7"
- Operator asks "why does the gallery only have v8?" or similar
- The freshness check or audit raises a question about historical version completeness
- The gallery-pact/ docs are being updated and this would be a logical inclusion
- During the next "tidy up" / "consistency check" pass
Otherwise: leave parked. Not blocking anything.
---
Reference
- Decision: `pact/decisions/2026-07-22-fvw-canonical-home-is-gallery.md`
- Manifest: `/workspace/fvw-canonical-rollout-manifest.md` (Steps 0-6 done; this is implicit Step 7+)
- FVS-side source: `avidtech6/freshvibestudio/pact/freshvibe-way-v6/` and `pact/freshvibe-way-v7/`
- Gallery-side destination: `avidtech6/fv-module-gallery/gallery-pact/fvw/v6/` and `v7/`
- Current canonical: `avidtech6/fv-module-gallery/gallery-pact/fvw/v8/` (8.1.0)
- Auto-mirror workflow: `avidtech6/fv-module-gallery/.github/workflows/mirror-fvw.yml` (will keep v8 in sync from fvs; v6/v7 won't be affected)
---
*This plan is parked. To un-park: remove this header line and the "PARKED" tag, set the work to in_progress, and execute Step 1.*