Operating Inheritance

An established firm's resolved operating knowledge — decision rules, exception history, commercial terms — extracted from the people who hold it and encoded as a clean-sheet autonomous business's mandate and exception architecture, without the organisation, stack or contracts.

The corpus has held since its first month that an incumbent cannot be transformed: a business built on human coordination has the coordination layer as its operating system, and the reconstruction is incompatible with the continued operation of the thing being reconstructed. The Operating Inheritance does not disturb that position. It names something the position left unexamined — what an incumbent knows, as distinct from what it is — and observes that the knowledge is exactly the input a clean-sheet build is worst at producing for itself. Full-System Design requires every Deterministic Loop and exception protocol encoded before the first transaction. A studio's Agentic Core supplies the architecture of a state machine. It does not know which states a given business can be in, which exceptions it escalates, what its counterparties will accept, or where its pricing rule bends and why. The incumbent does, and holds it as habit, in people, enforced by nobody and applied inconsistently. The mandate was written. It was never encoded.

The term's boundary is what makes it usable, because the obvious failure is to take too much. Three components cross. Decision rules: the conditions under which the firm prices, accepts, declines, escalates and commits, stated as conditions rather than as the names of the people who apply them. Exception history: the catalogue of states the firm encountered outside its routine, what it did, and what it learned — the material from which an Exception Architecture is calibrated rather than guessed. Commercial terms: what counterparties accept and refuse, and which terms predict a working relationship. Together these are the Operational Ledger of a business that never kept one. Three components stay. The stack, because it was built for human execution and carries the Rebuild Tax a clean sheet exists to avoid. The contracts, because each carries an obligation to be served as it has been served. The organisation, because the organisation is the Legacy Liability itself; people cross as Stewards, on evidence, or not at all.

The extraction instrument already exists in the corpus. The Steward Transfer Protocol is the documented process by which an outgoing Steward's undocumented judgment calls, exception history and informal heuristics are captured and verified before departure; the Operating Inheritance is that protocol applied to a firm, where the departing Steward is the organisation and the receiving system is a business that does not yet exist. Extraction is not encoding. A rule five experienced people agree on is a candidate, and the corpus's Ghost Trial, extended from its defined setting of live parallel execution to pre-launch replay, is the validation instrument: each candidate rule is replayed against the firm's own historical decisions and outcomes, held as an escalation if it fails or if the replay shows the firm applied it inconsistently, and promoted into the mandate if it survives — with the assumptions the replay cannot test, such as a relationship or market condition that does not transfer, carried with the rule as escalation conditions. The distinction from consulting is the destination: consulting documents processes so the same organisation can run them better, while the inheritance extracts decisions so that a different business, with no organisation, can encode them as an Encoded Mandate, calibrated Intervention Thresholds and an Exception Architecture. Customer records are not part of the inheritance as defined; where records are needed they travel under a scoped licence, because they carry consents and obligations that do not transfer by being useful.

Where the inheritance can be run is the subject of the Counter-Positioned Clone: not inside the firm that holds it, for the reasons Legacy Liability gives, but in a separate clean-sheet business the firm participates in without governing. The effect on the studio's economics is on the one axis the Agentic Core could not improve — Infrastructure Drag's content, the discovery of states by operating, arrives as an input instead. Arco has extracted no Operating Inheritance; the term is a design requirement derived from the corpus's existing principles about what a clean-sheet build needs before its first transaction.

First used: October 2026

Edition 1 · updated October 2026