The Engine Room
Business Operating System for AI-first teams
↓or scroll to continue
What We'll Cover
~30 minute walkthrough
Full document: catalyst/HANDOVER.md
We built features,
not user experiences.
What We Built
- •Knowledge hierarchy + drift detection
- •Triage queue, chat, quick capture
- •Real-time presence & collaboration
- •Calendar + Google integration
- •Filter/thesis evaluation system
What We Missed
- •"What does a user DO?"
- •Clear entry points
- •Feature boundaries
- •The smallest valuable loop
Your First Job
Not to finish features — to validate we're building the right thing.
Maybe It's Just Three Actions
Tell
"Here's what happened in my meeting"
Ask
"What should I focus on?"
See
"Here's what's drifting"
"The Engine Room keeps you aligned."
Everything else is implementation detail.
Four Build Phases
Foundation
- Module scaffold, types, constants
- Database migrations (prepared)
- Mock data layer with seed data
Command Centre Core
- Unified shell, triage queue, chat
- Quick capture + activity feed
- Detail pages (CC-01 to CC-12)
CC Enhancements
- Mode toggle, widgets, alignment
- Presence, live updates, collaboration
- Calendar, Google auth (CC-13 to CC-25)
Filter/Thesis
- Thesis editor & viewer
- Engine, Talk, Gatekeeper integration
- Audit system (Filter-01 to Filter-05)
Entity → Vision → Goals → Workstreams → Tasks + Context + Conversations
Where Things Live
Key Folders
app/(app)/app/ → Routes
modules/engine/ → Business logic
modules/engine/types.ts → All types
modules/engine/data/ → Data access
catalyst/ → Project docs
Tech Stack
pnpm install && pnpm devThen visit localhost:3000/app
Needs Your Input
Ripple Integration
We don't know what the AI backend can do. All AI code is placeholder.
Data Model
Are workstreams necessary? My lean: flatten to Goals → Tasks.
Context Orchestration
Complex system built before we have a working AI backend.
Filter/Thesis System
Now built (Filter-01-05). Does it belong with Engine or separate?
Understand, Don't Build
Walk through /app end-to-end
Read vision & experience docs
Review 3 briefs + implementation
Write down what confuses you
Draft answers to 5 questions
The 5 Questions
1. What's the one thing we should ship first?
2. What should we delete or defer?
3. Where do feature boundaries need redrawing?
4. What user problem are we solving?
5. Would you use this? Why or why not?
Question Everything.
The best outcome might be that you tell us to throw half of it away and start simpler.
Welcome to the Engine Room.
Let's figure out if it's the right thing to build.
— Tim