Authenticated upload surface for documents and images
Private household memory reboot
Winston is starting over around the one loop that matters.
Reboot underway
Ingest-first rebuild
The active Winston app is intentionally reduced to auth, branding, and a clean reboot shell.
The next Winston is not beginning with modules, dashboards, and feature breadth. It is beginning with trustworthy household memory.
The live app keeps family-only sign-in and a protected reboot shell while the active build target narrows to upload, extract, classify, review, persist, embed, and retrieve.
First build slice
Winston only earns broader UI once the ingest loop is strong.
Durable extraction pipeline with explicit failure states
Classification and heavy labeling with multimodal AI
Human review and correction before finalization
Finalized memory persisted for embeddings and retrieval
Search and chat grounded only in finalized memory
Trustworthy memory before broad UI
Winston will not rebuild dashboards and modules ahead of the ingest loop that creates reliable household knowledge.
Vertical slices over giant phase plans
Only the next small set of proven slices should steer implementation. Breadth returns after the product earns it.
Direct code until patterns are earned
The reboot should prefer simple explicit flows over premature registries, abstraction layers, and module machinery.