Captain B. McCrea wrestling with AUTO at the helm of the Axiom in Pixar’s Wall-E — the human and the autopilot fighting for control of the ship
Company BrainAIFounder ToolsLeadership

Who’s Steering the Axiom? Why Your Company Brain Needs a Captain, Not an Autopilot

Joshua GilmerJoshua Gilmer
|
·7 min read

In the Pixar masterpiece Wall-E, the Axiom is a marvel of engineering. It is a self-sustaining, hyper-efficient ecosystem where every human need is met by an algorithm. But at the center of the ship sits AUTO — the AI pilot’s wheel. AUTO is the ultimate Company Brain. It has all the data, it manages all the systems, and it follows its directive with mathematical precision.

The problem? AUTO was operating on a directive — A113 — that was centuries out of date. It had the data (the green plant) proving Earth was habitable, but it lacked the context to care. It took a human captain, finally standing on his own two feet, to look at the same data and realize it was time to go home.

As "Company Brains" become the new gold rush — fueled by Y Combinator’s latest call for startups — we are at a crossroads. We are building the Axiom. But if we aren’t careful, we’re going to end up with a ship full of data and no one actually captaining the vessel.

The Trap of Context Debt

We’ve talked about this before: Context Debt is the silent killer of scaling companies.

When you implement an AI Company Brain, you’re essentially centralizing your organization’s memory. But memory without a pulse is just an archive. If your AI is only consuming Linear tickets, Git commits, and polished Notion pages, it’s not learning how you think — it’s just cataloging your "meta-data."

Linear tickets tell the AI what was done. Git commits tell it how it was built. But neither tells the AI why you decided to kill a feature three days before launch because it "felt wrong."

AI follows the directive. Leaders follow the mission.

If your leadership team is stuck in back-to-back meetings while the Company Brain automates the output, you aren’t leading; you’re just watching the autopilot fly you deeper into space.

Leading at 12x Speed

If your team can now do a year’s worth of work in a single month thanks to AI augmentation, the traditional C-Suite model is officially broken. You cannot "manage" that much velocity from a dashboard.

To lead now, you have to:

  • Use the Product: You can’t judge the "soul" of a release from a slide deck.
  • Internalize the Output: If the ship is moving faster, the Captain needs to be more sensitive to the vibrations in the hull.
  • Close the Context Gap: You need to talk — frequently and loudly — about the evolving mission.

The Company Brain needs to know not just what the company did today, but how the company felt about it.

The "Captain’s Log" is No Longer Optional

The greatest context you can give an AI isn’t your documentation; it’s your journaling. But here’s the reality: modern documentation is a Frankenstein’s monster of meta-data. You think over a thought 30 times, write it down, edit it, let an AI "improve" the tone, and then hit publish. Half of it is yours; half of it is AI copy-pasta. It’s too polished. It’s too sterile.

The answer is video.

Technically, voice is just as fast, but video offers a level of fidelity that the AI of 2026 (and beyond) will crave to understand the nuance of leadership.

  • The hesitation in your voice when you talk about a pivot.
  • The excitement in your eyes when a prototype actually works.
  • The raw, unedited "thinking out loud" that happens before a thought is "Notion-ready."

You need a channel where you talk about the why. You need to record the Captain’s Log — not for the archives, but to feed the Brain the connective tissue it needs to move from "memory" to "intelligence."

And you don’t do it alone. The Captain has officers. The CEO, CFO, CTO, COO — every leader carrying part of the mission — should be recording short, unedited reflections that get fed into the same shared layer. That practice has a name: C-Suite Journaling. Solo journaling preserves a single mind; C-suite journaling captures the connective tissue between functions, which is exactly the part the AI cannot reconstruct from tickets alone.

The Brain Needs a Soul

A Company Brain without a captain is just a very expensive way to stay lost.

Leaders must adjust every day. They keep a connective thread alive where it matters, and they have the guts to snap that thread when the world changes. They elevate new priorities based on intuition, not just "data points."

The Brain has to be more than memory. It has to be an extension of the Captain’s will.

If you haven’t "thought out loud" for your AI, it will eventually default to its own version of Directive A113. It will keep the ship moving in a straight line, even if you’re heading straight for a star.

This is the same lesson we drew out of The Martian: Watney’s logs aren’t cute astronaut content. They are the connective tissue between his constraint, his decision, and his next move. Without that thread, the data on the screen means nothing.

And it is the same warning from Blade Runner 2049: when language becomes cheap to manufacture, your archive becomes cheap to doubt. A Company Brain fed entirely on AI-polished docs will eventually be a synthetic memory of a company that never quite existed.

Rule:

It’s time to stop being passengers on our own ships. Use the tools, build the brain, but for heaven’s sake — stay on the bridge.

If you’re a CEO, CFO, CTO, or COO trying to keep your team’s velocity from outrunning your context, this is what Historic was built for. Speak the why — once a day, once a week, whenever the wheel turns — and let the Company Brain inherit the part of leadership that documentation has never been able to carry.

Key Questions & Takeaways

A Company Brain is a centralized AI system that ingests a company’s documents, tickets, code, conversations, and decisions to act as the institutional memory and reasoning layer of the business. Y Combinator and other accelerators have called it the next great enterprise category — every operating company will have one within a decade. The risk is that a Company Brain trained only on meta-data (Linear tickets, Git commits, polished Notion pages) catalogs what was done but never learns why. Without leadership context, the Brain optimizes against an out-of-date directive instead of the live mission.

C-suite journaling is a collaborative practice in which the CEO, CFO, CTO, COO, and other senior leaders each record short video reflections that, taken together, build the company’s living context layer. Where solo journaling preserves a single founder’s reasoning, C-suite journaling captures the connective tissue between functions — the why behind a hire, the conviction behind a product cut, the doubt behind a pricing change — and feeds it into a shared Company Brain. The result is institutional memory the AI can actually learn from, instead of polished documentation written for an imaginary audience.

Because data without context optimizes for the wrong objective. AUTO in Wall-E had every metric on the Axiom but kept executing Directive A113 long after Earth was habitable again. A modern Company Brain trained only on tickets and commits will do the same thing — keep the ship pointed at last quarter’s mission while the captain has already decided to pivot. A captain’s job is to keep the directive alive, which means narrating the why often enough that the Brain inherits the change.

Context debt is the accumulating gap between what a company actually knows — its evolving mission, the why behind its calls, the soul of its product — and what is encoded in its tools, tickets, and documentation. It compounds when leadership runs faster than its ability to articulate, especially in AI-augmented teams that can ship a year of work in a month. The cure is not more documentation; it is unedited leadership reflection, recorded fast enough to keep up with the velocity it is trying to explain.

Text is too polished and increasingly co-authored with AI, which strips out the signals leadership context depends on: hesitation, conviction, energy, the half-formed thought. Video captures all of that natively. It also resists the contamination of synthetic language — your face and voice are unmistakably yours, while a typed memo can be 50% AI copy-pasta and indistinguishable from your own writing. For an AI that is trying to learn how you actually think, video is the highest-fidelity input available.

The Captain’s Log is a leadership journaling practice — typically recorded as short, unedited video — where the captain of an organization narrates the why behind decisions, pivots, and pressure points in real time. Linear tickets tell the AI what was done. Git commits tell it how it was built. The Captain’s Log tells it why. That single addition is what turns a Company Brain from a searchable archive into a thinking partner that understands the live mission.

Most Company Brain startups are competing on ingestion: more connectors, more sources, deeper retrieval over the documents and tickets a company already produces. The gap is the leadership input layer. Tickets and commits describe execution; they don’t describe the evolving mission. Without a structured way for the C-suite to feed in the why — through C-suite journaling, a Captain’s Log, or some equivalent — the Brain ends up like AUTO: hyper-competent, perfectly informed, and pointed at the wrong destination.

They turn journaling into a leadership ritual rather than a personal habit. Each member of the C-suite records short video reflections at decision points — the CEO on mission and pivots, the CFO on capital and risk, the CTO on architecture and trade-offs, the COO on execution and people. Those entries get transcribed, summarized, and indexed into a shared layer the Company Brain can read. Over time, the AI stops being a search engine over polished docs and starts being a synthesis layer over the actual reasoning of the people running the company.

Share:

The mind, in evidence.