Routes
Public story and private app are finally separate.
Marketing lives in its own lane, authenticated workspaces live in theirs, and the product no longer has to fake scale from one tangled surface.
Feature Map
One product feel. Clean module boundaries.
Uniicco is being rebuilt so the experience feels like one connected system while the codebase stays understandable, secure, and ready for real users.
(marketing)
Landing, features, pricing, onboarding, brand
(app)
Dash, Daily, Words, Matrix, Archive
features/*
Reusable UI, actions, state boundaries, domain logic
server/*
Queries, session guards, secure mutations, future policies
Features
Each module grows inside a real domain boundary.
Daily, Dash, Words, Matrix, and Archive can evolve without leaking UI hacks and state chaos across the rest of the app.
Server
Sensitive work happens where it should.
Auth, protected routes, database writes, and user isolation are handled with server-first patterns instead of hopeful client-side glue.
Workspace Modules
Each surface has a role inside the same system.
Ready modules can already be shaped. Planned modules stay visible so the product grows with intention.
Control Surface
ready
Dashboards
A registry of modules, custom dashboards, and fast entry points.
Execution Layer
ready
Daily Planner
Tasks, routines, counters, and a day-level operating surface.
Cognitive Layer
ready
Lexicon Lab
Vocabulary practice, spaced review, and progress tracking.
Strategic Layer
planned
Neural Matrix
An eventual canvas for linking goals, projects, and research paths.
Knowledge Layer
planned
Research Archive
Primary sources, notes, and future AI-assisted analysis.
Rebuild Rules
The architecture is part of the product now.
Thin routes. Real feature folders. Server actions for writes.
One visual language across modules, but each workspace keeps its own energy.
No new shiny layer gets added if auth, schema, or navigation would become fragile again.