Note

    ROADMAP

    Future development plans and milestones

    Document Metadata

    • title: Development Roadmap
    • description: Future development plans and milestones
    • status: evolving
    • lastUpdated: "2026-03-22 13:07 ET (America/New_York)"
    • owner: Product/Engineering

    Development Roadmap Use checkpoint-driven execution tracking. Avoid today/tomorrow handoff phrasing.

    Development Roadmap

    Use checkpoint-driven execution tracking. Avoid today/tomorrow handoff phrasing. Use node scripts/docs/timestamp-et.mjs --json for any timestamp added in roadmap notes.

    Immediate Priorities

    1. [1010] Ratify the multi-user ownership model and table-by-table data-isolation plan before auth-provider cutover work starts changing principal semantics in production.
    2. [1009] Provision Neon Auth for the new auth-preview Neon branch and retrieve the branch-specific provider contract (auth_url, JWKS URL, optional issuer/audience).
    3. [1009] Decide the non-production backend topology that will point at auth-preview, because the current Render API still has previews disabled and main is the only live lane.
    4. [1008] Continue the strategy-adoption stream: validate the new intervention-first overview on live data, tune attention scoring, and extend actionability deeper into project detail/docs intelligence.
    5. [1006] Continue KPI/dashboard UX/IA cleanup focused on docs-intelligence digestibility and stronger summary-to-evidence drill-down affordances.
    6. [1002] Expand non-mocked/live regression coverage for run-trace failure paths and docs/KPI/dashboard interaction flows while keeping the hosted smoke pack green.
    7. [1001] Close Neon migration operational tail items (hosted env cleanup verification and strict main deploy-source enforcement on Render).
    8. [1006] Keep docs automation in parity with Hyphenomenon (docs-site-sync workflow + manifest/link/build checks) so docs remain the trusted intake/governance source.
    9. [1002] Keep regression bundle scripts (test:regression:*) and docs-regression CI job as required merge hygiene for all PRs.

    Recently Completed

    • [1009] Completed Neon project-scoped access and created the dedicated auth-preview Neon database branch for non-production auth rehearsal work, reducing the remaining blocker to Neon Auth provisioning plus backend preview topology.
    • [1009] Audited the real Vercel/Render provider surface for the next Neon rehearsal step and confirmed the remaining gap is environmental rather than in-repo: Preview still has only Better Auth frontend envs configured, and Render previews are disabled on the active API service.
    • [1009] Added the first provider-aware live smoke lane by capturing the app's real authenticated API request, asserting /auth/status against the expected provider, and allowing Live Smoke to run browser-only for intentional Neon-authenticated rehearsals while keeping the backend live-pack Better-Auth-only.
    • [1009] Added the frontend Neon Auth scaffold behind the shared auth bridge, including VITE_NEON_AUTH_URL support and deterministic provider-selection coverage, while leaving Better Auth as the active hosted default.
    • [1009] Chose direct Neon JWT verification against JWKS as the standalone API cutover strategy and added the first inactive backend scaffold plus deterministic JWT/config test coverage for that path.
    • [1009] Added a provider/principal migration seam across frontend auth, backend auth resolution, and auth posture reporting so the eventual Neon Auth cutover targets explicit adapters/contracts instead of Better Auth-specific assumptions scattered through the app.
    • [1010] Opened a dedicated multi-user authorization and data-isolation stream so ownership modeling, schema changes, leakage prevention, and testing expansion are tracked separately from auth-provider migration.
    • [1009] Opened a dedicated auth modernization stream with Neon Auth as the target recommendation and started by hardening the existing Better Auth deployment against implicit account creation and open signup.
    • [1007] Closed the monorepo/standalone restoration stream after confirming the three-way comparison had already been completed, the legacy Vercel project was retired, and the standalone repo remains the canonical deploy source.
    • [1007] Upgraded CI, docs-site sync, and Live Smoke to current Node 24-compatible actions/* major versions after confirming the standalone live stack still passes hosted smoke verification.
    • [1007] Re-ran hosted Live Smoke successfully on the standalone Vercel alias and merged the deploy-normalization checkpoint with passing browser and backend live-pack jobs.
    • [1007] Fixed backend live-pack Better Auth parity by propagating LIVE_APP_BASE_URL and sending the deployed frontend origin during hosted session bootstrap.
    • [1007] Normalized the standalone Vercel project env sets across Development/Preview/Production, updated Render CORS for the standalone frontend aliases, and switched repo smoke/deploy defaults to project-compass-standalone.vercel.app.
    • [1008] Added structured attention-driver visuals to overview and repo comparison so intervention order is paired with compact “why now” cues instead of summary text alone.
    • [1008] Shifted the live backend smoke/integration pack toward session-first Better Auth by replacing the static live API bearer dependency with smoke-password session bootstrap.
    • [1008] Added snapshot-over-snapshot KPI baseline deltas plus Top KPI Gaps actionability to the overview so strategic progress interpretation is benchmark-aware instead of absolute-only.
    • [1008] Turned current strategy conclusions into an active adoption stream with a first implementation slice covering attention-ranked overview signals, repo-level next actions, 7d-vs-prior-7d trend baselines, and Settings auth posture checks.
    • [1008] Hardened Better Auth production posture with secure hosted URL/origin validation, minimum secret length enforcement, and explicit session-first mode (ALLOW_LEGACY_API_BEARER_AUTH opt-in only).
    • [1007] Verified standalone-vs-monorepo parity and confirmed the monorepo does not contain missing Project Compass product code beyond docs/deploy/source-of-truth drift.
    • [1007] Restored the standalone repo docs posture so this repository is again the canonical working surface instead of a legacy/archival placeholder.
    • [1002] Added standardized regression bundle scripts and CI docs-regression gating; validated core/docs/e2e suites.
    • [1007] Completed local monorepo bootstrap dry-run import with history-preserving subtree adds and cross-app docs guard/manifest/link validation.
    • Added tracked-artifact CI guardrails to docs sync (docs:artifact-guard + workflow step) to prevent generated-output regressions.
    • Added docs sync CI workflow parity and refreshed docs manifest baseline (docs/manifest.json) with successful docs checks/build.
    • [1006] Converted docs-intelligence Repo Compare to cards-first scanning with explicit table fallback and shared details rendering
    • [1002] Live-validated the extended repository-comparison smoke contract on deployed Vercel + Render (npm run test:smoke:live passed)
    • [1002] Expanded hosted live-smoke regression contract for Repository Comparison (cards/table toggle + empty-state fallback assertions) to cover recent 1006 IA changes
    • [1006] Live-verified overview repository-comparison cards/table redesign on project-compass-zeta.vercel.app with authenticated refresh
    • [1006] Reworked overview Repository Comparison into default cards + table fallback with sortable ordering and added ProjectHealthCards component tests
    • [1006] Live-verified KPI hierarchy declutter on project-compass-zeta.vercel.app (advanced control gating + focus cards/table layout + tree advanced controls)
    • [1006] Decluttered KPI hierarchy controls by moving mode-specific controls behind Show advanced controls and added focus-list Cards / Table layout switching (default Cards)
    • [1006] Added KPI hierarchy e2e regression coverage (tests/e2e/kpis.spec.ts) for focus/tree interaction and row-evaluation refresh behavior
    • [1006] Removed repeated AI-assessment helper text from nested compact tree cards to reduce metadata noise in hierarchy scans
    • [1006] Live-verified compact tree-action compression on project-compass-zeta.vercel.app (compact mode keeps only essential inline actions by default)
    • [1006] Reduced compact tree-card action noise by moving Edit from inline primary actions into secondary actions (More actions)
    • [1006] Live-verified KPI hierarchy density controls and clickability fix on project-compass-zeta.vercel.app (Compact/Detailed toggles now switch reliably)
    • [1006] Fixed KPI tree-density toggle clickability on large screens by resolving hierarchy-control overlap (Compact/Detailed vs Expand all)
    • [1006] Added Compact cards / Detailed cards density modes to KPI Tree editor with recursive node rendering support
    • [1006] Added row-level Evaluate actions in KPI focus-list mode so missing-assessment triage can be cleared without switching to tree cards
    • [1006] Added KPI focus-list attention-band triage (high/medium/low) with reason-first table rows and explicit band filtering in hierarchy controls
    • [1006] Added project-detail timeline source model (docs projects vs synthesized goals) with docs-project filtering and explicit execution-status sections (Planned, In Progress, Completed, Needs Attention)
    • [1006] Added docs evidence Confidence floor triage control, aligned filtered metrics to confidence-scoped rows, and added KPI Attention-only focus + progressive focus-row reveal
    • [1006] Added Docs Intelligence signal inspector panel in Evidence Explorer table mode and added KPI tree Expand all / Collapse all controls
    • [1006] Added KPI hierarchy Focus list mode with attention-ranked sorting and summary triage metrics, while preserving full Tree editor workflow
    • [1006] Landed retry-aware AI call resilience + deterministic failure lineage (ai_log_id on partial failures), with partial-warning surfacing in AI Ops > Runs
    • [1006] Fixed production metadata parsing in AI Ops > Runs so JSON-string sync_log.metadata values still activate deterministic ai_log_ids linkage
    • [1006] Shipped deterministic run lineage by persisting ai_log_ids into sync_log.metadata and switching AI Ops runs to metadata-first linking with window fallback
    • [1006] Shipped first AI Ops > Runs timeline + step drill-down and completed cross-tab evidence-control consistency pass
    • [1005] Docs-intelligence content activation completed with deployed strategic provenance contract + hosted smoke evidence
    • [1003] Governance/doc realignment completed after follow-up audit confirmed no remaining ordering or strategy contradictions across non-completed streams

    Mid-term

    • Expand docs-intelligence quality benchmarking and model/workflow tuning now that KPI-aware ranking baseline is in place

    Long-term

    • Item 1

    Documentation

    • Canonical docs root: docs/
    • VitePress home: docs/index.md
    • Source-of-truth index: docs/README.md

    Provenance