FWV v8 — FreshVibe Way

Acronym: FreshVibe Way = FVW. (Local /FWV-v8/ directory is a typo; canonical is pact/freshvibe-way-v8/.) Path: avidtech6/freshvibestudio/pact/freshvibe-way-v8/ Status: active, with contamination cleanup shipped at 8c093ef (D-062)

What FWV v8 is

App-agnostic doctrine stream. Helps any app align with FVS patterns. Does NOT turn a non-FVS app into FVS.

A non-FVS app has zero business knowing about FVS workspaces (VibeCoder, VibeScope, Origin, FreshCards) as part of an FWV v8 alignment. If a non-FVS module ever needs to become an FVS workspace, that's an explicit ask to FVS Mavis later — not something a refactor plan pre-decides.

Sections (29+)

See doctrine/fvw-v8.md for the full list. Highlights:

• §00 philosophy
• §02 folder layout
• §04 trace-atlas schema
• §06 refactor procedure
• §10 modules-as-clusters
• §17 modules-and-tiers
• §18 revibe-pattern
• §22 behaviour-first-codex
• §23 two-view-substrate
• §30 hard cap (200L/.tsx)
• §00.2 reconstructability invariant

Recent work

• Phase 4 (FWV v8 contamination cleanup) shipped at 8c093ef (2026-06-22 18:37)
• 24 files, 169 swaps
• Replaced VibeCoder/VibeScope/Origin/FreshCards/FreshVibe Studio with Workspace A/B/C/Sample App
• Plan-correction addendum at studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md
• Decision: D-062

App-agnostic invariant (post-contamination-fix)

Where FVS names are appropriate

• FreshVibe Refactor Contract HYBRID mode (FvS-specific)
• FreshVibe Runtime Subsystem Catalogue (audits FVS's own capabilities)
• Master Plan (FvS-specific build target)

Where FVS names are NOT appropriate

• Recipe Book schema (must be app-agnostic)
• Generic examples in doctrine docs
• AST walker source code
• Clean-room check logic

Cross-references

• Lane: chrome (currently owns FWV v8)
• Topic: freshvibe-governance
• Decisions: D-062
• Plan: phase-4-fvw-cleanup
• Doctrine file: doctrine/fvw-v8.md (more detail)