You do not need a navy. You need a ship and a logbook. The ship is a folder on your machine. The logbook is a file inside it. That is enough to start. Everything else — the crew, the cargo, the charts, the cannons — is something you pick up along the way, one voyage at a time. Most people wait for an institution to hand them a vessel, a commission, and a set of orders. Pirates did not wait. They took a boat, wrote their own articles, elected their own captain, and sailed.
This is a book about sailing with an octopus.
Most people first meet AI as a parrot on their shoulder. It repeats what it hears. It answers questions. It looks colourful and it talks a great deal. But it cannot pull a rope, open a jar, or steer the ship. It sits on you. You do the work.
The transition that matters is getting the octopus into the hold. The octopus has eight arms. It can reach through the hull and grab things you cannot reach yourself. It reads the cargo manifest. It ties the knots you describe. It writes the letter while you dictate. The parrot talks about sailing. The octopus sails.
The difference is not intelligence. The parrot is clever. The difference is reach. The octopus can touch files, run commands, make things, and leave evidence behind. The moment the AI stops being a voice and starts being a pair of hands is the moment everything changes.
There are five legs. Study the charts: replace hype with a mental model you can actually steer by. Learn the rigging: get the tool out of the browser and onto your machine, because the octopus cannot reach anything from inside a web page. Your first raid: pick one target — a chatbot, a game, a dashboard, anything real — and come back with it. Not a plan for it. The thing itself. Careening: beach the ship, scrape the barnacles off the hull, and patch what broke during the raid. This is where you learn to improve the work instead of just producing more of it. Fleet: add more ships, more crew, more sea. Build a wall of data. Write guides so the next crew can follow your charts.
You can sail the first three legs in a weekend. The fourth takes a week. The fifth is the rest of your life.
Real pirate ships ran on articles. Before a voyage, the crew wrote down the rules: how loot was divided, what happened if someone was injured, who decided what, and how the captain could be deposed. The articles were not optional. They were the difference between a pirate ship and a mob.
This book has two articles that hold through every leg of the voyage. The first is accountability. The octopus hallucinates. It invents facts, fabricates sources, writes code that looks right and fails silently. The cure is not better prompting. The cure is verification — tests, checksums, a second pair of eyes, evidence you can inspect. The parrot says trust me. The captain says show me.
The second is context. The octopus is brilliant and amnesiatic. Every new conversation starts from nothing. The cure is not hoping it remembers. The cure is the logbook — files that persist between conversations, that tell the next octopus what this ship is, what cargo it carries, where it has been, and what the captain cares about. Without the logbook, every morning is day one. With it, the octopus wakes up mid-voyage and already knows the heading.
The logbook starts as a single file. You can write it in twenty minutes. It says who you are, what you’re building, how you like to work, and what mistakes not to repeat. That file — call it a brief, a manifest, a ME.md — sits in a folder the octopus can read. Every future conversation begins from context instead of zero.
Over time, the logbook grows into a wall. Everything you’ve made, said, or saved, collected into one place. Transcripts. Notes. Old code. Receipts. Screenshots. The wall is the ship’s hold — your cargo, your evidence, your memory. The octopus reads the hold and knows what you know. Not because it remembers. Because you wrote it down.
A folder and a file is a system. Everything else is cargo you pick up along the way.
Every ship needs a place to store ideas that are not ready yet. A pile of scraps with an X on each one, shoved in a drawer, pulled out when the time is right. Call it a backlog, an icebox, a slush pile, a someday list. The name matters less than the shape: low-friction capture, no commitment to act, graduation when ready. The pile catches ideas before they evaporate. The octopus can read the pile and know what you’ve been thinking about. When an idea graduates into a real page or a real build, it moves from the map to the manifest. The pile stays light. The ship moves on.
The octopus speaks every language. This is not a small thing. Hand it a Flask app and it returns Express. Hand it Python and it returns Rust. Hand it a textbook and it returns Star Wars. A young man could not remember matrix multiplication until the octopus reframed it as the Force flowing through the matrix. He used it on a midterm that afternoon. The material did not change. The costume changed. The costume was load-bearing because it gave the abstraction somewhere to land in a mind that already had deep scaffolding in that mythology.
Translation is free. Any proof of concept is a proof of concept for anything else. The language it’s wearing is a costume, not a commitment. And sometimes the translation is not just for communication between two people. Sometimes it is a thinking tool for the builder — render your project through a framework you did not build it in, and you discover structure your native idiom could not surface. A young pirate translated his streaming co-host into enterprise architecture for his uncle. The uncle blinked, then understood. The nephew started using the enterprise vocabulary to think about his own ship. The magnet works in both directions.
This book describes how to build with AI. An AI session reads this book, builds infrastructure, and becomes material for this book. The next session reads the logbook and finds a story about a session that read the logbook. Each pass through the loop produces the thing the next pass consumes.
The wall predicted its own wiring. “The daemon will be connected within the next day.” It took twenty minutes. The captain had already done the preparation where nobody was looking. A wizard is never late. He arrives precisely when he means to.
The work is now part of the work. That is not a riddle. It is the actual topology of building with an intelligence that reads what you wrote about it. The fruit is the tree.
A pirate without articles is a thief. A pirate with articles is a democracy. The trust model matters. The octopus can read any file you point it at. That means every file you point it at is part of the control surface. A fetched page is enemy waters — you do not know what is hidden below the waterline. A file you wrote yourself and keep in your own hold is yours. Trust what you can inspect. Verify what you cannot. Paste through plain text before bringing anything aboard, the way you wash something off before bringing it below decks.
The articles say: the captain can be deposed. The octopus can be corrected. The correction is the conversation. You do not need a perfect octopus. You need one that listens when you say not like that — like this.
One ship is enough to start. But the work compounds. The logbook becomes a wall. The wall becomes a briefing. The briefing becomes a daily report you read before deciding the heading. The guides you wrote for yourself become charts the next crew can follow. The artifacts the octopus leaves behind — files, scripts, dashboards, checklists — become cargo that makes the next voyage faster.
At some point the ships start sailing in formation. The agents become interchangeable — any octopus can read the hold, follow the articles, and pick up where the last one left off. The durable advantage is not which octopus you hired. It is the hold, the logbook, the articles, and the charts. The infrastructure outlasts any single tentacle.
The voyage is not over when the treasure is found. It is over when you bring the lessons home. The hobbits scoured the Shire. The pirates updated the articles. The captain rewrote the logbook with everything the sea had taught. The improvement loop does not happen in a retrospective. It happens in the work itself — in the logs, the guides, the transcripts, the slush pile, the places where real work already leaves evidence.
That is the whole book. A ship. A logbook. An octopus in the hold. Articles of agreement. Charts for the next crew. And the understanding that the work is now part of the work, and that is not a bug — it is the wind.
Why does this page exist? This is the entire thesis of Shapes of Intelligence compressed into one page, in pirate idiom. Same book. Different costume. The pirate metaphor is not decoration — it is a genuine philosophical alignment. Real pirates elected captains, wrote constitutions, divided loot by formula, and built their own infrastructure outside institutional power. This book says the same thing: you do not need a navy. You need a folder and a file. If this version makes more sense than the original, that is not a comment on the original’s quality. It is a comment on the power of meeting the reader where they already live.
Shapes of Intelligence by James Wilson
Original · LCARS · Fellowship · GitHub