Overview

One-screen executive summary of the Uploz build — what exists, how far along it is, and what could still move the i4F demo date.

At a glance

Workspace size and the single deadline everything burns down to

Apps

web · dev-admin cockpit

Packages

shared workspace libs

Migrations

schema 0001–0024 applied

612

Tests

Vitest suites green

Days to demo

i4F · 2026-10-12

Each ring is derived from a done / total count — honest at every value

88%

MVP01 sprints

7/8

S0–S5 + S0.5 shipped; S6 in dress-rehearsal

94%

Build waves

17/18

parallel agent bursts complete

91%

RTM coverage

58/64

requirements with code + tests

Highest-impact open items, with the status of each mitigation

No founders’ Linux server yet

High

Self-hosted Supabase + PROD deploy are compose-ready but cannot run the live dress rehearsal until the server lands.

Sprint 6 / devops

Blocked

E2E only proven on native Postgres

Medium

Gate keystone verified without Docker; the full Kong→PostgREST→RLS path still needs one green run on the deployed stack.

Wave E / quality

In Progress

HE / HI translation fill incomplete

Low

EN is complete; Hebrew and Hindi strings are scaffolded but need a native pass before the demo audience.

frontend / i18n

In Progress