IFO4

CFO-R Course/Chapter 4 , Ownership & Attribution/§4.2

§4.2 , 20 min read

Universal tagging standards

The 14-label schema that every resource must carry.

IFO4 requires fourteen labels on every billable resource. The schema is deliberately wider than the minimum most teams would propose, because each label serves a different downstream consumer: Finance needs cost-center, Security needs classification, Engineering needs component, Sustainability needs carbon-track. Narrowing the schema to satisfy the laziest consumer undermines the needs of all the others.

The 14 labels

Label	Example	Consumer
platform	ifo4	All
environment	production / staging / dev	Policy
managed-by	terraform / cloud-build / manual	Provenance
lifecycle	active / deprecated / legacy	Governance
migration-status	migrated / new / existing	Historical
owner	derris-taylor	Accountability
team	platform / certs / community	Org chart
cost-center	cc-ifo4-0001-engineering	Finance
application	ifo4-launch	Identity
component	web / api / db / ai	Architecture
region	us-central1	Geography
data-classification	public / internal / confidential / restricted	Security
cost-allocation	shared / dedicated	FinOps
carbon-track	compute / storage / database	Sustainability

Ring 4 mandates that deployment pipelines reject any resource missing any of these fourteen labels. The rejection is not a warning; it is a build failure.

Study questions

Confirm your comprehension.

Question 1

How many labels does the Ring 4 tagging schema contain?

Question 2

A resource missing a required label at deploy time should:

Question 3

Which label serves the Sustainability consumer?

 Previous

§4.1 , Doctrine , the unowned resource is a waiting incident

Next 

§4.3 , Ownership assignment & SLA

IFO4