liveBook · Manning

Ownership band

As explained in Crack Any Codebase with AI

An ownership band classifies a component by who wrote its code and who operates the machine on which it runs.

An ownership band classifies a component along two questions: who wrote its code and who operates the machine where it runs. Crossing those questions turns a flat service inventory into an incident-response map. section 9.3

Use four bands to identify the control available when a component fails:

  • CLIENT: your code on a machine you do not operate; ship updates, but do not trust client data or access the device. section 9.3
  • RUN: your code on your machine; edit code, configuration, or the server. section 9.3
  • RENT: vendor code on your machine; change configuration, but not the vendor source. section 9.3
  • CALL: vendor code on a vendor machine; retry, cache, or route around failures. section 9.3
Figure 9.5 The four machine-ownership bands dictate your control. CLIENT: Your code on a machine you do not operate, letting you ship updates. RUN: Your code on your machine, where you can edit anything. RENT: Vendor code on your machine, limiting you to config changes. CALL: Vendor code on a vendor machine, where you can only retry, cache, or route around.

Use the four-band visual to compare code ownership, machine ownership, and the resulting control during outages. section 9.3

How Crack Any Codebase with AI covers it

How deep it goes
Defines four ownership categories and their outage controls, stopping before application-code implementation details.
Examples
Uses browsers, backend applications, Postgres, Redis, and external services such as Stripe as banded components.
What it assumes
Assumes configuration files and runtime service calls, while teaching the ownership classification from the inventory stage.
What you can do after
Diagnose failures by identifying whether to edit, configure, update, retry, cache, or route around a component.
How it connects
Connects architecture, runtime dependencies, machine ownership, and incident response.

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.