Command center · Current

The Observatory

A private command center built over a plain markdown vault. The files stay the source of truth; the system around them does the operating, and Alita, the assistant, works inside it.

StatusIn daily use, v3 in build
SubstratePlain markdown, local
Runs onMy own hardware

From this

A plain markdown note open in a text editor

To this

The Observatory dashboard
Plain markdown files in, a command center out. The vault stays the source of truth; the Observatory is the operating layer built on top.

The problem it exists to solve

Note systems are good at capture and terrible at operation. The notes pile up, the structure decays, and the knowledge that should be compounding just sits there. I wanted one pane of glass over my vault that could actually run things: publish what I write, remember what I decide, and keep the structure honest as it grows.

The non-negotiable was sovereignty. The vault is plain markdown files on my own machines. No platform owns it, no export is ever needed, and anything built on top has to treat the files as the truth rather than swallowing them into a database.

What it does

The publishing pipeline takes a draft from idea to scheduled post, and when a piece goes live, a Mark Published step closes the loop: the system diffs my final edits against its drafts and learns my voice from what I changed. The more I publish, the less editing the next draft needs.

Session memory means work survives the gap between sittings. Every working session ends with a structured handoff, so the next one starts current instead of cold. And a reconciliation pass keeps the knowledge base from rotting: new context does not just get appended, it re-reads what exists and surfaces what should change.

Alita, the assistant, surfaces at the chat panel inside it. The Observatory is the room; Alita is who works in it. Keeping the app and the assistant as separate names keeps the architecture honest, the interface that renders the work, and the agent that reasons over it.

The Observatory publishing calendar
The publishing calendar: drafts moving from idea to scheduled, the edit loop closing behind each one.

The principles underneath

I.

Files over databases. Markdown survives every tool that will ever be built on top of it.

II.

Append-only history. Forensic logs never lose the past; reconciliation keeps the present true.

III.

The edit is the signal. Every correction I make teaches the system; fixes land at the source, not the symptom.

IV.

Nothing leaves the building. Local models, local files, local control.