Skip to main content
A candid, current snapshot of where the platform stands. Use this before planning a release or onboarding someone new.
Not launch-ready from the current working tree yet. The codebase is feature-complete through Phase 10, but an in-flight refactor must land and be verified before promotion to production. Details below.

Build at a glance

Codebase

Feature-complete through Phase 10 — all 38 tables, both apps, CMS, docs, jobs, CI.

Branch

Active development on dev. Promotion flow: dev → test → pprd → prod.

Blocker

web → admin background-job relocation is mid-refactor and uncommitted.

Payments

Phase 1 = cash / UPI / card at the counter. No online gateway by design.

What’s built

1

Data & domain

All 38 tables across 13 domains in packages/db — schema, relations, and a full typed query layer.
2

Customer app (apps/web)

Homepage, services, the 4-step booking dialog, bookings, profile, membership, gems, offers, blog, gallery, legal pages, auth/onboarding, PWA, SEO, and consent.
3

Admin app (apps/admin)

Dashboard, bookings, billing, customers, leads, staff, schedule, leave, memberships, offers, services, branches, users, reports, logs, integrations — plus the full admin API surface.
4

Platform

CMS (apps/cms), this docs site, the invoicing service, 19 background jobs, CI + deploy workflows, and a large unit/property test suite.

What blocks production right now

These are sequenced — finish them in order before promoting to prod.
The web-admin-separation-cleanup work relocates all 19 background-job routes from apps/web to apps/admin. In the working tree, the web routes are deleted (uncommitted) and the new admin copies are untracked, alongside modified deploy workflows, package.json, and env.ts. Nothing is committed, so the build is in an indeterminate state until this lands.
In that spec’s tasks.md, tasks through 3.8 are complete, but task 4 — the final checkpoint — is still open. Task 4 requires: typecheck + build BOTH apps green (no dangling @/lib/* imports) and both apps’ health checks pass. That confirmation has not happened.
There is a single baseline migration. Some schema files were edited after it was generated. The CI Drift Gate rejects schema changes without a matching committed migration. Run bun run generate + drizzle-kit check; migrate any emitted SQL before prod.

Before you can launch (ops checklist)

None of this is code-blocked — every integration no-ops without a key. This is provisioning + verification. See the full Launch Runbook and Deployment.

Path to launch

1

Land the refactor

Commit the web → admin job relocation; confirm both apps typecheck and build green (closes task 4).
2

Clear schema drift

bun run generate + drizzle-kit check; commit any new migration.
3

Provision

Keys, DNS, email-domain verification, Google OAuth approval; seed prod.
4

Pass the gates & promote

Green CI at the T-24h gate, then promote dev → test → pprd → prod following the Launch Runbook.
Last modified on September 1, 2026