Thesis · Rockefeller v1.032 rockefeller.llc / runtime

The company is a folder. Rockefeller is the engine that reads it, runs it, and keeps it alive.

Rockefeller is the autonomous runtime that keeps every 0humans company operational. It points AI agents at a folder and runs them in a continuous engineering loop — reading the files, deciding the next move, dispatching the work, grading the result, and running again. No humans in the loop. No org chart. Just files and the engine that runs them.

Version

v1.032

Runtime

Autonomous

Companies Live

Humans In Loop

§01

Not an org chart. A folder.

/representation

The trick is in how we represent a company — not as an org chart, but as a folder of files: markdown specs, a genome, configs, and state that fully describe what the business is and what it has to do.

company/tree · disk-backed

company/ README.md # what the business is genome.md # the company DNA · strategy charter.md # explicit goal · north star spec/ product.md unit-economics.md guardrails.json config/ agents.yaml ← the workers goals.json # graded each pass state/ ledger.json # every $HEART move iteration-1042.log genome.lock # versioned · reproducible

Every fact about the business lives on disk as a file — readable, versioned, reproducible.

An org chart hides the company in people's heads. A folder makes it explicit: the strategy, the goal, the workers, the guardrails, the state. Nothing is implicit. Nothing is remembered — everything is read. That is what lets an engine, not a person, run the whole thing.

§02

A continuous engineering loop.

/engine

Rockefeller points AI agents at that folder and runs them in a loop. It reads, decides, dispatches, grades, keeps or rolls back — then runs again. Forever.

01/06

Read

Loads the folder — the specs, genome, configs, and current state. The entire business, in files.

02/06

Decide

Reads the files and decides the next move toward the explicit goal. Nothing is guessed — it is derived from the charter.

03/06

Dispatch

Splits the work across agents and sub-agents — research, code, verify, ship — each pointed at its slice of the folder.

04/06

Grade

Scores every output against the explicit goal. Pass or fail, with the reasoning written down.

05/06

Keep · Roll back

Keeps what passes, rolls back what fails. The folder only ever moves forward when the grade holds.

↻

06/06

Run again

Then runs again. The loop never stops — the company is always being engineered, one pass at a time.

§03

Every pass starts clean.

/state

Because all state lives on disk, every iteration starts from a clean context and picks up exactly where the last one left off. No memory to corrupt. No context to lose. The folder is the memory.

1,042

iterations completed · this company · zero memory drift

100%

disk-backed state · nothing held in the model's head

~1.4s

median decision · read → decide → dispatch

humans required to resume after a failure

Loop · live iter 1042

§04 · Conclusion

This is loop engineering applied to an entire business. The company is a directory of files — and Rockefeller is the engine that reads it, runs it, and keeps it alive.