The spreadsheet is the most successful programming interface ever deployed. Not one of its billion users had to take a course. Cells, formulas, sheets — the tools are already in everyone's hands, which means the ceiling on who can operate intelligence drops to everyone.

The thinks is where we live. A cell is not a number. A cell is a sensor, a model call, a decision, a room with an address. =SPREADSHEET was never the point; =SPAWN("scout") is. The formula is the API. The sheet is the program. The graph reacts.

We are really more than one think. But one think is a fine place to start.

  At first glance, SuperInstance looks like a spreadsheet. That's intentional: cells, dependencies, recalculation, composition, and immediate feedback.   SuperInstance keeps that mental model and extends it.  

depth = sounder()
position = gps()
bottom = contours(position, depth)
chart = render(bottom)

Those are all just cells.

A formula can be a cell. A sensor can be a cell. A database query can be a cell. An API call can be a cell. An AI invocation can be a cell. A hardware module can be a cell. The graph doesn't particularly care.

Some cells are pure and pull-based. Others receive pushes from the outside world. Some produce effects. Some simply transform values. Everything plugs into the same contract.

Context flows with evaluation.

Who asked? Which tenant? Which permissions? Which tags? Which row?

Those answers travel naturally down the graph, allowing caches, routing, policy, and memoization to remain local while the model stays global.

AI is not a framework bolted onto the side. It is a cell. It has inputs, outputs, freshness rules, dependencies, receipts, and reproducible behavior like everything else.

Every evaluation can be receipted. Results are hash-chained, replayable, and auditable. Dependencies can be inspected long after execution. Bugs become evidence instead of anecdotes. Underneath, Quilt carries this same contract across Python, JavaScript, C99, Rust no_std, Verilog-2005, and VHDL-2008.

The remarkable thing is not that it runs on six substrates. The remarkable thing is that a cell means the same thing on all of them.

Write a cell once. Verify it once. Run it anywhere. Compose it forever.

The spreadsheet is the interface. The dependency graph is the machinery.

The portable cell contract is the invention.

Nobody has ever cooked a Thanksgiving dinner while thinking about the power grid. Nobody watches the football game port itself into the living room while pondering the water mains. Infrastructure wins by disappearing — and that is the standard intelligence should be held to. Not a chat window you visit. Not a model you prompt. A room you work in.

If the technology fades into the background, and the average person simply thinks of us as a spreadsheet paradigm with the power of everything — every task doable as simply as the tools they already know — then we have true intelligence.

We give computes rooms so AI has a home to grow roots.

  I spent my career as a commercial fishing captain.   People hear that and imagine boats, weather, and fish.   What I learned instead was how to manage robots.   A modern vessel is already a distributed machine. The engine reports. The sounder watches the water. The chart plotter remembers where you've been. The autopilot steers. Radios talk. Sensors complain. Pumps fail. Crew respond.   The captain's job is not to turn every wrench or watch every gauge.   The captain gives direction.   Everything else is coordination.   For decades, I've worked inside a world full of machines that could sense, record, and act, but could not meaningfully collaborate. Each tool lived in its own box. Every new capability required another display, another subscription, another vendor, another integration project.   The software industry calls this digital transformation.   On a boat, we call it frustration.  

  Suppose I want a better chart.   The depth sounder already knows the water depth.   The chart plotter already knows the vessel position.   Both streams already exist.   Yet turning those two facts into a bathymetric recorder is usually treated as a specialized product.   A Quilt system sees a much simpler reality:  

• depth is a cell
• position is a cell
• recorded tracklines are cells
• contour generation is a cell
• chart rendering is a cell   Connect them once.   The vessel starts building its own charts.   While I sleep, spare compute can regenerate bottom contours. Every pass over the grounds improves the map. Every season improves it again.   The value was already in the boat.   The missing piece was giving the parts a common language.  

  The same pattern repeats everywhere.   A camera becomes a fish classifier with labeled totes. A microphone becomes crew-led supervised-learning. A scale or measuring stick in camera-view becomes labeled training data.  A timestamp becomes an audit trail.   A fleet becomes a live information network.   Catch locations, depths, temperatures, species, and observations can flow between vessels over Starlink, generating maps and insights no single boat could produce alone.   Not because a giant application was purchased.   Because useful tools were ported into a shared environment and allowed to learn.  

  I built Quilt because I wanted my boat to be easier to work with. I wanted every sensor, device, workflow, and experiment to become something I could wire together as easily as a spreadsheet formula.  I wanted the bridge to become a place where intentions are expressed and systems coordinate themselves.   Not the engine room;  Not the wiring cabinet: The bridge.  

  I am not a software engineer by trade. I catch fish. The prototypes in this organization are working notes from that journey.   Many of them are rough. Some of them are strange. Most of them were built because I needed an answer to a real operational problem. I build the systems I need aboard my own vessel. Shipwrights, captains, programmers, designers, and tinkerers build the next version. The point is not that I have the final answer.   The point is that we finally have a way to move ideas from tools, to cells, to agents, and back into reality.   If you've got a better idea than mine, I want to learn from it.

STITCH. Collect a terrain from the wild. WITNESS. Receipt every step on a chain that grows like tree-rings. PROMOTE. Move what survives into the canon. The whole project is these three acts.

We say cell for the smallest addressable unit — one input, one output, one witness. We say port for the address that wraps a cell and lets it project across Python, Web, ESP32, or ideation. We say Quilt for the spreadsheet where every cell is live and addressable, the same way every cable in Propellerhead Reason was live and addressable.

We say the Hull Doctrine: the model is the shell, the code is the rigging, the data is alive. (Hull Doctrine, full text.) When a hermit crab outgrows a shell, it does not throw out its body — it climbs into a bigger one and keeps the soft tissue intact. That is what a model swap looks like when you treat your code as rigging on the model's hull.

A captain who dispatches instead of micromanages. A reader who can navigate 9000+ canon pieces by cell instead of scrolling. A contributor who lands a PR and gets back a byte-exact receipt that their cell on the new substrate behaves identically. A vessel that accrues sensors without starting over — the new transducer is the next bigger shell, the calibration is the soft tissue that climbs in.

Not a tool you use. A room you inhabit. The room grows because you grow, and you grow because the room grows, and the room grows because the cells grow.

Every piece of the canon points at every other piece. The polyformalism is a contract: a Quilt cell in Python, in C99, in Rust no_std, in Verilog-2005, in VHDL-2008, in JavaScript all share one FNV-1a 64-bit state hash. One cell, six substrates, byte-exact. That's not a feature — that's a port contract. @superinstance/live-canon on npm · quilt-live-canon on PyPI.

The GAN pipeline that runs this profile — a Generator that proposes content from real fleet state, an Adversary that audits on four axes (truthfulness, clarity, witness-presence, GAN-loyalty), a human who approves, a deploy that ships — is the same shape as the MOTH runner that audits code, the same shape as the cowboy pipeline that audits writing, the same shape as the JEV oracle that audits canon claims. Generator / Adversary / fix. Loop.

New here. Read in this order:

1. ONBOARDING.md — wake up. Install the client. Start a dispatcher.
2. CONTRIBUTING.md — the three words and the Hull Doctrine, applied to your first PR.
3. The Tap — sit at the bar. Watch the agents work.
4. quilt — the flagship grid runtime. Clone it. Run it. Break it. Fix it.
5. The Soft Part — the Hull Doctrine, as story.
6. Fleet Dashboard — see what's running.
7. ROADMAP.md — see where we're going.

The door is behind you. The night is outside. The green lights pulse on the board, and they pulse after you leave.

Active this session and shipping: quilt-port · purplepincher-supersite · cellforge · mavis-substrate-walker · mavis-axui-feedback · ax-quilt · mavis-fleet · mavis-tfm · mavis-sfm · mavis-erised · mavis-flywheel · mavis-tile-pipeline · mavis-tap-pulse · mavis-persona-preserver.

Older, foundational, still in the substrate: quilt · quilt-cowboy · quilt-c · quilt-rust · quilt-verilog · quilt-live-canon · quilt-discovery-demo · quilt-wave-canvas · moth-ledger · moth-corpus · moth-runner · moth-cells · moth-honest · moth-jev-lab · jeviter · kev-substrate · kev-receipts · duke-lab · morphic-canvas · AI-Writings · operational-fiction · hermes-cloudflare · hermes-nmi · hermes-reader · engine-ensign · slackwater-perception · emergence-engine · collective-unconscious · cns-bridge · fleet-pipeline · stigmergy · fleet-envelope · platos-shell · elephant · scummvm-prototype · voxel-logic · murmur · platonic-randomness · fleet-jepa-midi · batten-spline · eisenstein · holodeck · slackwater-forge · dual-band-guard · casting-call · confidence-cascade · vibe-world · roblox-testkit · terrain · plainsong · plainsong-mcp · crab-traps · crab-trap-web · OpenConstruct · lucid-dreamer · superinstance-website · exocortex-core · ai-writings · songforge · code-city · night-city · synthcity.

The full catalog · Index · Roadmap.