Skip to content

Vectis_Project_Transition_Plan.md

Latest commit

 

History

History
47 lines (30 loc) · 1.17 KB

Vectis_Project_Transition_Plan.md

File metadata and controls

47 lines (30 loc) · 1.17 KB
Raw

Vectis Project Transition Plan

Decision

Recommendation: Defer structural refactoring until after tomorrow's demo unless today's work is limited to documentation and creating a vectis-core repository skeleton. Avoid moving files or changing paths before a customer demo.

Phase 0 -- Baseline

  • Create a git tag and backup SQLite/data.
  • Capture a successful demo run.
  • Record startup time and smoke tests.

Exit criteria: App runs unchanged.

Phase 1 -- Introduce Configuration

  • Add .env with DATA_ROOT.
  • Replace hard-coded paths with a central paths.py.
  • No file moves.

Tests: Backend starts, SQLite loads, DuckDB builds, UI matches baseline.

Phase 2 -- Create Shared Data Layout

  • Create Data/Power/....
  • Copy (don't move) datasets.
  • Point one branch to new layout.

Tests: Compare row counts and key queries.

Phase 3 -- Introduce vectis-core

  • Create shared package.
  • Move path/config/logging utilities only.

Tests: Import from package; all integration tests pass.

Phase 4 -- Clean Up

  • Remove legacy paths.
  • Document bootstrap process.

Exit: Demo-quality application with identical behavior.