LedgerOS · Phase 5 · Production Integration Blueprint

Migration Plan

Staged handoff from mock UI to production. Each stage has an entry criterion, an exit criterion, and an owner. LedgerOS runs parallel to Zoho Books before it replaces it.

LedgerOS UI Design Lab · Phase 5 blueprint — no backend is connected. Every endpoint, permission, and event listed here is a design contract, not a live API.
  1. 01
    Mock UI approved
    Phases 1–4 shipped in design lab.
    done
  2. 02
    Component handoff
    Freeze mock props · export Storybook · deliver Phase 5 API map.
    in progress
  3. 03
    Read-only API connection
    Wire GET endpoints from Navy Federal, Zoho CRM, Zoho Books to real screens.
    planned
  4. 04
    Role validation
    Load real roles from ADP + custom mapping. Verify permission matrix.
    planned
  5. 05
    Draft-only mutations
    Turn on writes but everything lands in draft/task state.
    planned
  6. 06
    Approval-gated mutations
    Enable approvals queue with real actors and audit trail.
    planned
  7. 07
    Parallel run vs Zoho Books
    Two systems run side-by-side; nightly variance report.
    planned
  8. 08
    Reconciliation & variance review
    Root-cause every delta > $50 or > 0.5%.
    planned
  9. 09
    Controlled cutover
    Freeze Zoho Books; LedgerOS becomes system of record for one entity.
    planned
  10. 10
    Full production use
    All entities on LedgerOS. Zoho Books moved to archival read-only.
    planned
Rollback plan

Zoho Books stays read-writable until stage 9. At any point through stage 8, rollback = disable LedgerOS mutations, keep read-only reporting, resume Zoho Books as system of record. No data is deleted; all journal proposals remain in draft.