Skip to main content

Migration Plan

This document outlines the full migration path from traditional RABS to the FABRABS architecture.

1. Goals of Migration

  • Introduce modular architecture
  • Introduce module agents
  • Introduce orchestrator governance
  • Establish linkmaps + newsletters
  • Enable self-healing pipeline
  • Preserve existing functionality
  • Ensure minimal downtime

2. Migration Phases

Phase A — Prepare RABS Clone​

  1. Duplicate current RABS repo → FABRABS/
  2. Assign separate local ports (backend + frontend)
  3. Freeze original RABS (development continues separately)

Phase B — Establish FABRABS Scaffold​

  1. Create /modules
  2. Create /globals
  3. Create /orchestrator
  4. Create /frontends/admin + frobals
  5. Install new folder tree structure

Phase C — Build Orchestrator Core​

  • routing injection
  • versioning engine
  • sandbox runner
  • risk engine
  • contract management
  • linkmap_active.json
  • orchestrator APIs

Phase D — Module Extraction (Pilot)​

  1. Select test module (Messenger recommended)
  2. Extract backend logic into /modules/messenger/content/backend
  3. Extract frontend into /modules/messenger/content/frontend
  4. Build manifest.json
  5. Write module’s agent rules + startup script
  6. Configure sharepoints

Phase E — Validate Module Build​

  • Run Vite build
  • Run backend
  • Validate routing
  • Validate API paths
  • Validate module boundaries

Phase F — Enable Devmode​

  • Add Dev Button
  • Enable orchestrator request flow
  • Test sandbox creation
  • Test vNext version

Phase G — Expand Module-by-Module​

  • For each module:
    • extract backend
    • extract frontend
    • build manifest
    • generate agent rules
    • configure sharepoints
    • update linkmap
    • validate via orchestrator

Phase H — System-Wide Validation​

  • All modules build independently
  • All agents respond correctly
  • All linkmaps accurate
  • All newsletters generated
  • All risk levels correct
  • Devmode works for all modules

Phase I — Completion Checklist​

  • All modules extracted
  • RABS replaced by FABRABS
  • All agents sandbox-tested
  • All orchestrator functions validated
  • Migration logs stored
  • Go-live ready

3. Time Estimates

PhaseEstimated Time
A1 day
B1–2 days
C7–10 days
D2–4 days
E1–3 days
F3–5 days
GVariable (depends on module count)
H2–5 days
I1 day

4. Success Criteria

FABRABS is considered successfully migrated when:

  • Vite builds all modules
  • Backend routes load all module content
  • Devmode works platform-wide
  • Agents are isolated + safe
  • Orchestrator intercepts schema changes
  • Linkmaps maintain dependency logic
  • Self-healing pipeline fully operational