The single source of truth for Nameplate backend architecture and implementation status. Statuses distinguish the 28-model NestJS/Prisma foundation, usable API workflows, and planned work so a modeled table is never mistaken for a production-ready feature.
This page is grounded in the checked-in repository, not the target architecture. The production direction is NestJS + Prisma + Supabase Postgres; the currently connected local demo path is FastAPI + SQLAlchemy + SQLite.
28 Prisma models, three forward migrations, tenant transaction/RLS support, Supabase JWT verification, membership/RBAC/property-scope guards, user invitations, and a clean build.
HQ, Portal, and Field default to http://localhost:8080/api. The bridge has 14 SQLAlchemy models/tables, seeded demo data, QR routes, CRUD workflows, Supabase upsert helpers, and is the path used for the local interactive demo.
python3 -m backend_py.runbackend/README.md · backend/prisma/schema.prisma · backend_py/main.py · hq/src/api/client.ts · tests run 2026-09-05.The backend has one job: turn field facts into a permanent, explainable asset record without blocking technicians when connectivity or data quality is imperfect.
A scan, move, inspection, repair, part swap, or turn finding happens offline or online.
Flutter + DriftNestJS validates identity, role, property scope, payload, and operation identity.
REST / OpenAPI 3.1Prisma opens a transaction; facts, state mirrors, ledger entries, and audit rows commit together.
PostgreSQL 16Workers reconcile rollups, shrinkage signals, SLA state, exports, and daily metrics.
Jobs + read replicaEvery tile drills back to source rows. No number exists without lineage and a definition.
React HQ ConsoleService, location, part usage, scans, turns, and audits are corrected by adding evidence—not deleting history.
Current asset location, status, cost, and service counts are fast mirrors derived from ledgers.
Every customer-owned row carries org_id; application guards and RLS both enforce it.
UUIDv7 IDs, operation idempotency, dual timestamps, and monotonic change cursors are schema requirements.
The model stays relational because the valuable questions cross properties, assets, events, parts, people, and time. Domain boundaries organize ownership without breaking referential integrity.
Each card states ownership, essential columns, integrity rules, and current repository maturity. API built means the principal guarded workflow exists; API partial means a wired endpoint or transaction exists but domain rules remain; DB foundation means the table is modeled, migrated, secured, and seeded without a complete API; Deferred means it is not modeled in the current 28-table V0 schema.
The fastest architecture test is to trace a real field action through its transaction and verify the resulting rows can answer the future reporting question.
A repair must never exist without its costs, part lineage, asset state, work-order outcome, and audit evidence.
service_event + part_usage[] + part state + asset projection + work_order + audit_logClose the previous custody interval, append the new interval, update current location, and record who confirmed it.
asset_location close + asset_location insert + asset current_* + audit_logFreeze findings, generate work, update occupancy and missing state, start grace windows, and queue reconciliation work.
turn + turn_item[] + work_order[] + asset status + reconciliation_flag + audit_logSupabase is the intended PostgreSQL/Auth/Storage infrastructure for the NestJS API. The repository also contains a working FastAPI + SQLite development bridge currently used by HQ, Portal, and Field defaults; it is not the long-term system-of-record architecture.
Use local PostgreSQL for the backend loop. Prisma migrations and the seed script remain the schema authority.
Use separate Supabase projects for staging and production. Apply reviewed migrations through CI; do not hand-edit production tables in the dashboard.
user_accountHQ and Field do not directly mutate core tables. The API owns custody, cost rollups, corrections, approvals, and cross-row transactions.
Supabase owns auth and storage. Nameplate owns public application tables and never duplicates passwords or file blobs.
auth.users → user_account.idstorage.objects ← media.storage_keyRepository badges show what exists in this checkout as of 2026-09-05; they are maintained from code, migrations, and tests. Checkboxes are a separate, browser-local verification record and do not change implementation status. Each phase ends with an evidence gate.