fvre — FreshVibe Refactor Engine
Lane session: 408523191824555 Status: parked (HYBRID-mode gatekeeper on standby) Topic: FreshVibe Refactor Contract, Recipe Books, extraction engine
What fvre owns
- FreshVibe Refactor Contract (FvRE) — the doctrine + tooling for refactoring any app to FVW v8 alignment
- Recipe Book schema — what every recipe looks like
- Extraction engine — AST walker + clean-room check logic
- HYBRID-mode gatekeeping — decides when an FVW v8 alignment plan needs HYBRID mode (vs APP-AGNOSTIC or APP-NATIVE)
What fvre does NOT own
- FVS chrome (chrome)
- FreshCards substrate (cards)
- FVW v8 doctrine content (chrome; fvre consumes)
- Cross-Mavis state (helper)
App-agnostic invariant (per contamination-fix at 8c093ef)
A non-FVS app has zero business knowing about FVS workspaces as part of an FVW v8 alignment. Recipe schema must stay app-agnostic. If a non-FVS module ever needs to become an FVS workspace, that's an explicit ask to FVS Mavis later.
This is a HARD constraint on fvre's extraction engine. Any recipe that suggests FVS workspace partitioning for a non-FVS app is wrong.
HYBRID-mode gatekeeping
When an FVW v8 alignment plan needs HYBRID mode (some FVS-specific tweaks + some app-agnostic patterns), fvre signs off. The gate is:
- Recipe contents — are they app-agnostic? If they reference FVS workspace names, the plan is not HYBRID, it's a covert FVS-ification.
- Operator intent — is the operator trying to make the non-FVS app look like FVS? If yes, that's a violation of the doctrine fence.
- Identity contract (§6) — does the plan include a §6 identity contract? If not, fvre rejects.
When fvre is needed
- New FVW v8 alignment plan needs HYBRID-mode sign-off
- New recipe schema for a non-FVS app
- Extraction engine needs a sweep (per FWV v8 §27 drift-discovery)
- App audit (does this FVS-claimed app actually look like FVS?)
Cross-references
- Lane: fvre
- Doctrine:
doctrine/governance.md,doctrine/fvw-v8.md - Plan-correction addendum:
studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md - Decision: D-062 (Phase 4 cleanup that affects fvre's gatekeeping)