docHub

D-062 — Phase 4 (FWV v8 contamination cleanup) is shipped at 8c093ef

Status: accepted Date: 2026-06-23 Decided by: Helper Mavis (session 412100071272671), based on direct GitHub API check


Context

Memory (2026-06-22) recorded: "FWV v8 doctrine contamination principle (2026-06-22) — flagged as in-progress, awaiting operator sign-off. Need to strip FVS-specific names from generic examples in §10, §17, §18."

A direct API check on 2026-06-23 confirms commit 8c093ef on avidtech6/freshvibestudio main:

The plan correction is itself part of the doctrine: non-FVS apps should not adopt FVS workspace partitioning as a refactor deliverable.


Decision

Phase 4 of the FVS roadmap is shipped, not in-progress. Memory entries that say "FWV v8 contamination — in progress" are outdated and should be updated.

The shipped Phase 4 includes:


Consequences


Pact cross-references

Pact ref — fvw-v8-contamination-fix (pact/freshvibe-way-v8/00-philosophy.md, and 23 other files)

Replacements: VibeCoder → Workspace A, VibeScope → Workspace B, Origin → Workspace C, FreshCards → Sample App, FreshVibe Studio → Sample App.

Relation to this decision: this is the commit that produced the cleaned doctrine. Quoting it gives docHub readers the exact replacement mapping that was applied.


Related decisions


← back to Mavis workshop