State
Engine Room
Records, documents, instrument docs, nudges, diffs, and decisions live in the hub.
Philip OS
The Engine Room
Private studio console
Where development work leaves residue.
The Engine Room is not a CRM and not a chatbot. It is the shared hub where Philip's reads, meetings, decisions, edits, deck work, and weekly reviews become calibrated instruments.
Engine Room hub
State lives here. Agents are just clients.
Agents
2 clients
Mildred/OpenClaw and Cowork should read/write through MCP or REST.
Boundary
Tagged
Personal and Hawco records can cross over now, but provenance stays attached.
Exit
Reversible
Workspace export/delete proof is an early build requirement.
Vertical slice
Nudge to journal loop
Hub health
- Store
- ...
- Entries
- ...
- Pending
- ...
Loading local hub...
No nudge selected.
syntheticLatest journal entries
Instrument library
One craft, one instrument, one calibration loop.
Instrument 1
Coverage
AI extracts descriptive fields. Philip writes live wire, main problem, engine, defense, risk, bucket, and next action.
Correction rate becomes calibration
Instrument 2
Decks
Deck skeletons, design kits, drafts, finals, and edit diffs accumulate in the hub instead of staying stranded.
Draft to final deltas captured
Instrument 3
Writer Notes
Relationship-aware notes stay Philip's until the corpus earns trust. AI can organize and polish, not replace judgment.
Tone and framing memory
Habit layer
Weekly Review
A delivered memo pulls Philip back into the system: what changed, what is stuck, what needs a decision.
4-week open/use streak
Coverage workbench v1
AI describes. Philip decides. The instrument learns.
This keeps the boundary clean: extraction first, judgment only from Philip until the coverage corpus earns the right to draft evaluative work.
Descriptive extraction
Logline, synopsis, format, genre, comps, character list, submitted material facts.
Philip writes judgment
Live wire, main problem, TV engine, primary defense, kill risk, bucket, next action.
Residue compounds
Decision why, edit diff, outcome, and similar past cases become the instrument memory.
Relationship context
Writer, rep, buyer, obligation, and history stay visible without turning into CRM clutter.
Instrument 1 detail
Coverage starts as structured human judgment.
AI descriptive
Logline
Extracted from material and editable before anything becomes part of the record.
AI descriptive
Synopsis
Neutral summary with citations to pages/scenes once parser support exists.
Philip evaluative
Live wire
The thing worth protecting. Philip writes it, the system learns from it.
Philip evaluative
Main problem
Blunt internal decision support, not writer-facing diplomacy.
Philip evaluative
TV engine
Strong, maybe, unclear, or N/A, with the one-line reason.
Philip evaluative
Next action
Pass, read more, develop, clarify rights, meet writer, take to buyer, or hold.
Instrument 2 preview
Decks become assets, not stranded files.
The deck instrument should migrate Cowork's existing deck work into the hub, then capture draft-to-final deltas so the system learns Philip's pitch language and visual standards.
Import from Cowork
Skeleton
Reusable deck structure, page roles, and narrative sequence.
Per project
Design kit
Tone, references, typography, palette, image rules, and layout constraints.
The Vig
Reference deck
Known benchmark, treated as asset and taste reference, not a final template.
Calibration
Edit diffs
Every draft-to-final change becomes deck-instrument memory.
Nudge flow
Capture should be lighter than opening the app.
Reply capture
Philip answers a message with two sentences. The hub files and links it.
Calendar trigger
Meeting ends, debrief nudge appears before relationship detail evaporates.
Source link
A CRM project, material, person, or deck asset stays attached to the note.
Resolved
Nudges have status, owner, and result, so both agents know what happened.
Recent residue
The valuable data is the trace Philip leaves while working.
personal
JournalEntry
Debrief: buyer call
Unstructured note classified after capture; linked to people and projects later.
hawco
CoverageRecord
Creol Murders read structure
Descriptive extraction stays separate from Philip's evaluative fields.
personal
EditDiff
Writer-note revision
Before/after correction becomes signal, stronger than a feedback button.
hawco
Nudge
Follow-up owed
A relationship obligation captured without becoming another CRM row.
What changed
Only surface signals that change a decision.
Hawco CRM sync
Three records changed since last review
Surface only if a decision, follow-up, or rights risk changed.
Canada-first radar
Funding and broadcaster signals waiting
Market news should become project-specific implications, not a news feed.
Instrument library
Coverage corpus needs Philip-written examples
No evaluative AI coverage until the instrument has real correction history.