Uploz · Export Board
Overview · Coverage · Risks
Generated 30 September 2026 at 11:43 · 12 days to demo target
Overview
Where the build stands at a glance.
2
Apps
web · dev-admin cockpit
9
Packages
shared workspace libs
24
Migrations
schema 0001–0024 applied
612
Tests
Vitest suites green
MVP01 sprints
7 of 8 · S0–S5 + S0.5 shipped; S6 in dress-rehearsal
Build waves
17 of 18 · parallel agent bursts complete
RTM coverage
58 of 64 · requirements with code + tests
Coverage growth
Automated-test surface added wave by wave (cumulative).
| Wave | Added | Cumulative | Share |
|---|---|---|---|
| Foundation | +12 | 12 | 3% |
| Wave A — validation-engine + ui kit | +38 | 50 | 12% |
| Wave B — web app + BE migrations | +64 | 114 | 27% |
| Wave C — write-path APIs + UX | +47 | 161 | 38% |
| Wave D — cockpit live-data + drift + E2E | +53 | 214 | 51% |
| Wave E — MVP02 backend depth | +41 | 255 | 61% |
| Wave F — frontend completeness | +36 | 291 | 69% |
| Wave G — i18n/auth + quality | +72 | 363 | 86% |
| Wave H — security (RLS) + E2E + design | +58 | 421 | 100% |
Risk register
Most severe first. Mitigation status tracks the fix, not the risk.
The whole stack — web, worker, Postgres, Redis — rides one VPS. A host outage, disk failure, or noisy-neighbour stall takes the entire product down with no automatic failover.
Mitigation: Nightly off-host backups with restore drills, a documented one-command rebuild, and a costed warm-standby plan to lift before the first paid event.
India's DPDP Act constrains where personal data may live and how it is processed. A VPS or backup region outside the permitted boundary, or an unreviewed sub-processor, is a regulatory exposure.
Mitigation: Pin compute and backups to an approved region, maintain a sub-processor register, and gate any new vendor behind a residency review before integration.
Core flows are exercised by automated tests, but the live event-day path (compressed clocks, realtime fan-out, web push) has thin end-to-end coverage against real infrastructure, so regressions can reach a live event.
Mitigation: A scheduled live-verification run against a production-shaped environment, with a go/no-go gate before each event window and alerting on the verification job itself.
Running our own outbound mail means a cold IP and domain reputation. Without a staged warmup, transactional mail (verification, invites, receipts) lands in spam or is throttled by major providers.
Mitigation: Staged volume warmup with SPF/DKIM/DMARC aligned, seed-list monitoring, and an ESP fallback ready to switch the transactional stream if reputation degrades.
iOS only delivers web push to home-screen-installed PWAs and silently drops permission edge cases. Users who never add to home screen get no live event alerts, undermining the realtime promise.
Mitigation: Detect install state, prompt add-to-home-screen at the right moment, and fall back to email/SMS for critical event alerts when web push is unavailable.
Top risks to the demo
The executive shortlist that could move the demo date.
Self-hosted Supabase + PROD deploy are compose-ready but cannot run the live dress rehearsal until the server lands.
Sprint 6 / devops
Gate keystone verified without Docker; the full Kong→PostgREST→RLS path still needs one green run on the deployed stack.
Wave E / quality
EN is complete; Hebrew and Hindi strings are scaffolded but need a native pass before the demo audience.
frontend / i18n
Uploz Dev-Admin · illustrative project-tracking state · generated 30 September 2026 at 11:43