MVP progress demo

Walk through the current build

A guided product walkthrough of the foundations that moved from prototypes into verified platform behavior.

Demo scope

  • Visual: design-system routes, dark mode, shape balance, and USWDS comparison.
  • Content: page-tree contracts, revisions, starter-site provisioning, and preview.
  • Operations: document ingestion, search, worker jobs, run history, and proof scripts.

Snapshot

What is demonstrably real now

Local proof suite passing

Core foundations

5

Design, publishing, ingestion, worker ops

Unit checks

60

Current suite after worker-run history

A11y routes

82

Full Playwright and axe run

Cron worker

10m

Protected source-text extraction path

Walkthrough

Select a foundation to review

Phase 3 of 5

Document ingestion and search

The document library now has the durable kernel an MVP needs: tenant storage, import batches, chunks, review governance, search, and accessibility release checks.

Shipped pieces

  • Private upload and review queue
  • Chunked searchable text
  • Manual text-layer correction workflow
  • Structured accessibility remediation

Evidence

Cross-tenant document, chunk, storage, job, and remediation access is denied.

Public search is tenant-scoped and ranks title/body/chunk matches.

Approval blocks unresolved or expired accessibility exceptions.

Guardrails

Why this is an MVP foundation, not a demo shell

Tenant isolation

Documents, chunks, jobs, storage, revisions, and accessibility records are exercised through negative-path proof scripts.

Search quality

Approved public records search over metadata and chunks now returns query-focused snippets and relevance ordering.

Backend continuity

The backend remains Supabase/Postgres with additive tables, RLS, service-role RPCs, and audit trails.

Release checks

Latest local gate passed lint, typecheck, unit, document, audit, site-builder, a11y, build, and whitespace checks.

Next build target

OCR provider evaluation is now the logical next deep slice

The queue, worker route, storage access, chunk writer, job status, per-document warnings, and aggregate run history are now in place. The next provider can plug into a safer contract instead of reshaping the backend.