Every screen, every state, every click defined. This is the spec the real product will be built against. Nothing here is a promise, everything here is a hypothesis being validated.
v16 shipped a working Studio shell but used a rainbow of per-app colours (indigo / amber / green / pink / sky for icons, blue / purple / pink for feedback tags). v17 collapses that to the locked Floom palette: single green accent (#047857), soft red for danger only, everything else neutral ink / muted / line. App icons become monochrome letter chips. Feedback tags become neutral pills with one accent for FEATURE. Same content, same layout, one design language.
v15.3 tried to put consumers and creators on the same shell. Result: /me was doing six jobs, /p/:slug had Edit buttons next to Run buttons, everyone felt lost. v16 splits it. Store (consumer, light #FAFAF7, marketing chrome) lives at the root. Studio (creator, workspace #F5F5F1, 240px sidebar, dense tabs) lives at /studio. Same login, same identity, different surface. Six-tab per-app drill-down (Overview · Runs · Secrets · Access · Renderer · Analytics). New landing H1: "Production infrastructure for AI apps that do real work."
Phase 1 landing + waitlist. Phase 2 Docker OSS core. Phase 3 Cloud multi-tenant wrap. Phase 4 Composio integration. Phase 5 public v1.0 launch. Per-phase objective, deliverables, tech stack decisions, week-by-week build steps, testing protocol, ICP walkthroughs, risks.
Source of truth for implementation. 200+ interactive elements enumerated with their behavior: navigate, toast, toggle, open modal, submit form, filter, or display-only. Zero uncertainty before coding.
Verification of what the current floom-monorepo v0.1.0 actually ships. Input/output contracts per app, rendering pipeline, where the wireframe assumptions match reality and where they diverge.
Every assumption the wireframe and roadmap depend on, tracked with validation status. Unvalidated, in flight, validated, or invalidated. Gets updated as validation agents land.