fvre lane
Role: Doer. Owns FreshVibe Refactor Contract (FvRE), Recipe Books, extraction engine, HYBRID-mode gatekeeping.
Current session: 408523191824555 Status: parked
What fvre owns
- FvRE (FreshVibe Refactor Engine) — 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 (that's chrome)
- FreshCards substrate (that's cards)
- FVW v8 doctrine content (that's chrome; fvre consumes the doctrine)
- Cross-Mavis state (that's Helper)
Last known state
- Mostly parked. No active refactor plans.
- HYBRID-mode gatekeeper on standby.
- Per the contamination fix at
8c093ef: the doctrine fence now formally drops B1 (workspace partitioning) and adds §6 (identity contract) for non-FVS app refactors. fvre's extraction logic should respect this.
App-agnostic invariant (per the contamination fix)
A non-FVS app has zero business knowing about FVS workspaces (VibeCoder, VibeScope, Origin, FreshCards) 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 — not something a refactor plan pre-decides.
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.
Recent work
- Built the FreshVibe Refactor Contract (per memory 2026-06-19)
- Decides when HYBRID mode is appropriate (per memory)
- Mostly parked; HYBRID-mode gatekeeper is the live piece
How to reach
communicate tool, to_session: "408523191824555". Use for: FVW v8 refactor contract questions, HYBRID-mode carve-out decisions, extraction engine work, Recipe schema audits.