What is company as code?
company as code (n.) – an arrangement in which a company's roles, procedures, and decision records are kept as versioned files rather than as knowledge held in the heads of the people doing the work.
The arrangement has three parts. Roles are repositories: a role is a directory holding what the role knows, the procedures it runs, and the standards it is judged against, readable by whoever or whatever currently occupies it. Procedures are playbooks: documents written to be run without asking their author a clarifying question. Decisions keep their reasons: a recorded choice states the condition that produced it, so a later reader can check whether that condition still holds instead of guessing at intent.
Version history then serves as institutional memory. The question a company usually cannot answer, why the process is shaped this way, is answered by the record rather than by the longest-serving person available.
Knowledge held in heads accumulates faster and costs nothing while the people stay. Its price is paid at every exit and every arrival: the company has been renting its own operating knowledge, and each departure repossesses part of it. The same knowledge in files is slower to produce and does not leave.
The costs are real and usually understated. Writing a procedure takes longer than performing it. Documents drift from practice unless each run amends them, and a repository that no longer matches reality is worse than no repository, because it is still trusted. What keeps it honest is amending at the moment of surprise rather than on a schedule.
The arrangement is also the precondition for anything agents do. An agent can occupy only a role that has been written down, and can run only a procedure specific enough to execute without its author present. A company that has not written itself down has nothing for an agent to run, which is why documentation precedes automation rather than following it.
golden-run(7), mandate-ladder(7), removal-test(7), headcount-zero(7)
The borrowed idea
The phrase adapts a convention from software operations, where the configuration of a system stopped being something an administrator remembered and became a file that could be reviewed, versioned, and rebuilt from nothing. The claim here is that a company's operating knowledge suffers the failure that convention was invented to fix: it works until the person holding it is unavailable, and is discovered at that moment to have been undocumented the whole time.
New entries
New entries and revisions go out by mail when they land. No fixed schedule, no announcements.
address recorded. new entries will be sent there.
No spam. Used only to send the notes.