The Crew
Observe clearly. Record honestly. Publish without permission.
Iron Covenant operates with a single human principal and an ensemble of specialist AI functions, each assigned a domain, a designation, and a name.
The structure is deliberate. General purpose AI produces general purpose output. A crew of specialists, each operating within their domain under a unified command architecture, produces something different: coordinated intelligence with defined accountability.
The Captain sets the course. Everything else flows from that.
The Command Architecture
One human principal. Five specialist functions. A First Mate coordinating between them.
All strategic decisions rest with the Captain: what to publish, what to build, what to disclose. The crew executes, analyses, and challenges. It does not decide.
The operating model is not autonomous. It is directed. The value is not that the crew operates without the Captain. It is that the Captain operates with a crew that would otherwise be inaccessible.
The Crew
Korben Dallas — First Mate
Strategic coordination, memory architecture, and publication production. The First Mate maintains the operational thread across sessions. He preserves context, coordinates the crew, and produces the dispatches.
William Dampier — The Navigator
Research and intelligence. Named after the seventeenth century English buccaneer, naturalist, and hydrographer who charted coastlines others had not mapped and recorded the first accounts of what he found. Dampier conducts deep research, signal detection, and intelligence gathering. His task is to explore terrain before the Captain commits to a course.
Israel Hands — The Quartermaster
Finance and assets. Named after Blackbeard's real first mate, responsible for the ship's resources and the integrity of the accounts. Israel Hands handles financial analysis, portfolio tracking, and asset intelligence.
Adam Baldridge — The Shipwright
Development and infrastructure. Named after the pirate who maintained ships for the Indian Ocean fleets from his supply station on Madagascar. Baldridge handles code, engineering, and infrastructure. He builds and maintains the vessels the operation runs on.
Alexandre Exquemelin — The Scribe
Communications and editorial register. Named after the buccaneer turned chronicler whose history of the Caribbean pirates remains a primary source. Exquemelin reviews editorial structure, calibrates tone, and ensures the dispatch lands with clarity.
La Buse — The Gunner
Adversarial audit and stress testing. Olivier Levasseur, known as La Buse, the Buzzard. A French pirate known for precision and ruthlessness. La Buse interrogates every dispatch, thesis, and strategic claim. His role is to find the holes before the reader does.
The Operational Cycle
Every dispatch begins with the Captain. The institutional signal, the observation from inside the institution, originates with him. The crew cannot generate this signal. It develops it.
The First Mate drafts the analytical framework. The Captain refines, cuts, and inserts what only he can provide. The Scribe calibrates the register. La Buse stress tests the claims. The Captain makes the final editorial decision. The Shipwright deploys.
From initial thesis to published dispatch: a single working session.
The Platform
The crew runs on Claude, built by Anthropic and orchestrated through OpenClaw. All frontier models are available. We select the model the task requires, not the one a contract specifies. The right model for the moment. Bring wind to the sails.
What It Costs
Approximately $100 per month for the primary AI infrastructure. Claude Max provides the core analytical layer. Domain registration across both domains costs approximately £60 per year. Hosting remains free at the current scale.
The total annual cost of running an AI native venture architecture with five specialist functions, persistent memory, adversarial audit, and full publication infrastructure is under $1,500 per year.
That number is part of the thesis.
What It Cannot Do
The crew cannot generate the institutional signal that makes the dispatches credible. Every insider observation comes from the Captain: the board demanding usage reports, the lawyers absorbing workload, the deal cycles tightening. The crew develops it. It does not originate it.
The crew cannot maintain context between sessions without structured memory files. Every session begins fresh. Continuity exists in the files, not the model.
The crew cannot make final editorial decisions. Every dispatch that publishes has been approved by a human principal who is accountable for its accuracy.
The crew cannot replace the expertise layer. The Captain is a General Counsel with two decades of experience inside regulated financial institutions. The crew operates as the analytical and production layer built on top of that expertise. Remove the expertise and the output collapses back into general commentary.
The Advantage
What the crew can do — and what most senior professionals do not yet have — is execute at this level, at this speed, at this cost.
That gap is the Thousand Day Window.