The cockpit is not a dashboard.
It is a workshop.
I'm Anders Jensen. I build Axiom Engine — a self-hosted operations console for AI-assisted work. Five convictions about how that work should feel.
- I
Local ownership.
The cockpit belongs to the operator. Self-hosted, opinionated, mine. Not a SaaS dashboard renting me access to my own work. Axiom Engine runs on a Linux box on my desk and answers only to the prompt I sent.
- II
Memory as a single intelligence.
Scattered notes, browser tabs, Slack DMs, half-written Markdown — these are not knowledge. Knowledge is what survives consolidation. The console folds them into one substrate the agent can reason across.
- III
Observability without permission.
Every flow, every job, every model call is structured-logged the moment it happens. Debugging is not archaeology. The retry happens automatically because the failure was caught the moment it surfaced.
- IV
Cross-workflow data flow.
The catalyst. A flow that produces a podcast feeds a flow that posts to Telegram, that feeds a flow that updates a metrics file, that triggers a rebuild of this site. Silos shatter when the typed connections are first-class.
- V
Modular, real-time, alive.
Spaghetti is the natural state. Modularity is a daily practice. Components breathe; runs stream; nothing waits for a 24-hour batch. The console is awake for the same reason a workshop is — the operator is in it.
W19 — andersjensen1.com, restyled and restructured
The week the marketing site stopped pretending to be an architecture studio and admitted it's the front door of Axiom Engine. New shell, new color palette sampled from the running console, new IA, real telemetry on /metrics, three weekly dev-logs to seed the format.
ReadThis is a test with a 2:3 aspect ration image file
2:3 aspect ratio test
Read The journeyFrom langchain to Axiom
Three years of AI tinkering, distilled into a timeline.
Trace it