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
