docHub

Phase 4 — FWV v8 doctrine cleanup (contamination fix)

Status: ✅ complete (per D-062) Lane: chrome Started: 2026-06-22 Completed: 2026-06-22 18:37 UTC Commit: 8c093ef


TL;DR

Strip FVS-specific names (VibeCoder, VibeScope, Origin, FreshCards, FreshVibe Studio) from generic examples in FWV v8 doctrine. 24 files, 169 swaps. Plus a plan-correction addendum for non-FVS app refactors.


What changed

OldNewWhere
VibeCoderWorkspace Atier examples
VibeScopeWorkspace Btier examples
OriginWorkspace Ctier examples only; historical-comment meaning preserved in §18
FreshCardsSample Apptier examples
FreshVibe StudioSample Apptier examples

Files modified (10 of 24 in the diff; full list in commit)

(Plus 14 more; full list in the commit.)


Plan-correction addendum

studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md was added. Any FVW v8 alignment plan for a non-FVS app must reference it:


Why this matters

Before the fix, an AI reading only the FVW v8 repo with no FVS context would treat FVS-specific names as doctrine rules. That led to refactor plans that proposed FVS workspace partitioning for non-FVS apps — which is exactly the contamination the doctrine fence is supposed to prevent.

After the fix, FWV v8 reads as truly app-agnostic.


Cross-references


← back to Mavis workshop