Chapter 4 . Ownership & Attribution
A line item without an owner is waste.
Nothing exists without an owner. Every dollar has a name.
Ring 4 of RING:1000:2026
Edition v0.1 . Draft for working group review Lead author: Derris Taylor . Working group masthead pending ratification
1 . The Opening Forensic
In April 2018, Tesla's public-cloud Kubernetes console was discovered exposed to the open internet, running a cryptocurrency miner inside an abandoned compute pod. The miner had been operating for an estimated several weeks before researchers from RedLock filed the public disclosure. Tesla's incident response was professional. The remediation was complete in days. The press cycle moved on. The federation includes the case in the Ring 4 corpus because the operational forensics tell a sharper story than the press did.
The compute pod existed. It was running. It had a billing line in the Tesla cloud invoice. It had a Kubernetes namespace with a pod identifier and a service account. It had a project that funded it and a workload that was scheduled on it. None of these surfaces named the owner. The pod was technically attributed to no one inside Tesla. The cluster was provisioned by a team that had since reorganized. The original namespace owner had moved on. The pod's lifecycle had drifted from active to abandoned to forgotten without anyone receiving a hand-off. By the time the miner appeared, the pod was an orphan resource with a positive billing line and no human carrying its accountability.
The federation reads the Tesla case as the canonical Ring 4 forensic because it shows that an absent owner is not a neutral state. An absent owner is a positive risk. Resources without owners drift. Resources that drift are exploited. The dollar that runs through an unattributed pod is the dollar that ends up funding the next attacker's compute.
Ring 4 is the work of ensuring that no resource, no cost, no workload, and no commitment exists in the institution without a name attached to it. The reader who finishes this chapter will look at their own cloud invoice and find at least one line they cannot trace to a specific human. That line is the chapter's homework.
2 . The Doctrine
The doctrine of Ring 4 is anchored in a phrase the working group ratified in v0.6 and the federation has not let drift since.
Every dollar has a name. Every resource has an owner. Every workload has a steward. The institution does not buy what it cannot name.
The phrase reads as moral. The federation treats it as operational. A dollar without a name is a dollar the institution cannot govern. Governance is the act of holding a named human accountable for a defined surface. Governance dissolves the moment the surface is unnamed.
The reading order of the rings places Ownership & Attribution after Signal & Exposure for a reason that practitioners often miss on first encounter. Ring 5 surfaces every signal. Ring 4 turns each signal into an accountable line in the institution's ledger. A signal without an owner is intelligence without consequence. Ring 4 is the consequence layer.
Three principles run through this chapter.
Attribution is upstream of optimization. You cannot optimize what you cannot attribute. Every optimization conversation that bypasses attribution is a conversation that will produce theatre, not change.
Ownership is a person, not a team. Teams cannot be paged. Teams cannot be held in a one-on-one. The federation's standard is named individuals with named back-ups, not collective ownership.
An orphan resource is a positive risk, not a neutral one. The dollar still spends. The exposure still compounds. The institution still pays. Ownership is not about who pays the bill. Ownership is about who can be summoned to defend the line item.
3 . The Standard
Ten controls. Seven mandatory. Two recommended. One adaptive.
3.1 Universal Tagging Standards
Category: Attribution. Enforcement: Mandatory.
Enforced tagging taxonomy across all platforms with mandatory fields for owner, cost-center, environment, and project. The control is the foundation of Ring 4 because attribution at any layer depends on the institution having a shared vocabulary for who owns what.
The federation's reference taxonomy is fourteen labels. Five are mandatory at provisioning: owner (the named human accountable), cost-center (the budget the resource debits), environment (production, staging, development), application (the named system the resource serves), component (the role the resource plays inside the application). Nine are recommended, including business-unit, customer-tier, data-classification, retention-tier, and lifecycle-stage. The recommended labels become mandatory in higher-maturity Ring 4 implementations.
The label is wired into the provisioning system at the request layer. A request that does not carry the mandatory five labels is structurally rejected. The label is not metadata that gets cleaned up later. The label is the ticket of admission to the estate. Resources without labels do not enter the estate because the provisioning gate refuses them.
KPI. Tag compliance rate. Target: 98 percent of mandatory fields populated correctly across all environments.
3.2 Ownership Assignment and SLA
Category: Accountability. Enforcement: Mandatory.
Every detected resource must have an assigned owner within a defined service-level agreement. Unassigned resources escalate automatically. The control is the operating expression of the doctrine that no resource exists without a name.
The federation's reference SLA is four hours from detection to assignment for production-tier resources, twenty-four hours for non-production, and three days for ephemeral or test environments. A resource that exceeds the SLA without an assignment escalates to the resource's hosting team, then to the team's director, then to the federation's published exception process. The escalation is automated. No human has to remember to escalate. The control is wired into the discovery layer that Ring 5 produces.
A practitioner satisfying 4.2 has a discovery feed wired to an assignment queue, an assignment workflow with named SLAs, an escalation tree that is named and current, and a published exception process. The practitioner can answer the question "how long does an unowned resource live in our estate before it has a name attached" with a single number. The number is at or below the federation's SLA target.
KPI. Ownership assignment time. Target: under four hours for production-tier.
3.3 Cost Allocation Rules
Category: Allocation. Enforcement: Mandatory.
Shared costs are allocated using a defined methodology: direct attribution where possible, proportional split where direct is not feasible, fixed allocation as a last resort. The control is the operating expression of the doctrine that every dollar has a name, applied to the costs that resist single-owner attribution.
Shared costs are inevitable. A platform team's reserved-instance pool serves multiple application teams. A cloud network egress charge crosses many cost-centers. A licensed software contract covers the whole institution. The federation's standard is that shared costs are not allowed to remain undistributed in a "shared services" bucket. They must be allocated to the consuming cost-centers using a published methodology that the consuming teams can read and challenge.
The three methodologies in priority order are direct attribution (the cost is metered to the consumer), proportional split (the cost is divided in proportion to a measurable usage signal), and fixed allocation (the cost is divided by a published formula such as headcount or revenue share). Each methodology carries its own audit standard. Direct is auditable per transaction. Proportional is auditable against the underlying usage signal. Fixed is auditable against the published formula.
KPI. Cost allocation coverage. Target: 100 percent of all costs carry a defined allocation methodology.
3.4 Orphan Cost Detection and Escalation
Category: Detection. Enforcement: Mandatory.
Automated detection and escalation of costs without clear ownership. The control is the safety net that catches failures of 4.1 and 4.2 before they compound.
An orphan cost in the federation's standard is any cost line that, after the daily attribution run, does not resolve to a named owner with current accountability. Orphan costs are produced by tag drift, ownership transfer gaps, lifecycle gaps, and platform-API failures. The control identifies orphans within hours, not weeks, and routes each orphan to the resource's hosting team for re-attribution.
The federation's reference threshold is that any orphan cost exceeding $5,000 per month escalates to Ring 1 (Execution Governance) within the hour. The dollar threshold is calibrated to the institution's spend; the cadence is fixed. The escalation is a Ring 4 backstop, not a Ring 4 routine.
KPI. Orphan cost ratio. Target: under 2 percent of total spend at any point in time.
3.5 Tag Compliance Enforcement
Category: Compliance. Enforcement: Mandatory.
Real-time monitoring and enforcement of tagging compliance across all environments. The control is the operating layer that keeps 4.1 from drifting after the initial provisioning gate.
Tags drift. Resources that were tagged correctly at provisioning lose their tags through copy operations, console edits, automation that does not preserve metadata, and platform-API quirks. The control runs continuously against the estate, identifies drift, and remediates within hours. Remediation paths include automatic re-tagging from the discovery layer, escalation to the hosting team for ambiguous cases, and quarantining of resources that cannot be re-tagged within the SLA.
A practitioner satisfying 4.5 has a continuous compliance scanner, a remediation workflow with cadence and ownership, and a quarantine policy for non-remediable drift. The practitioner can produce the institution's tag drift rate per quarter as a single metric.
KPI. Tag drift rate. Target: under 0.5 percent of resources experience drift between provisioning and the next compliance scan.
3.6 Ownership Transfer Protocol
Category: Governance. Enforcement: Mandatory.
A formal process for transferring ownership when teams reorganize or personnel change. The control prevents the orphaned-pod failure mode that produced the Tesla forensic and dozens of equivalents the federation has reviewed.
A transfer protocol is mandatory because organizational change is constant. Teams reorganize quarterly. Personnel turnover happens monthly. Ownership transitions are routine. Without a protocol, every transition is an opportunity for resources to drift into orphan status. The protocol is the institution's commitment that ownership does not silently lapse.
The federation's reference protocol has four steps. The departing owner produces an inventory of every resource they hold. The inventory is reconciled against the discovery feed to surface omissions. The receiving owner accepts each resource explicitly. The transfer is logged with timestamps, signatures, and the federation's audit trail. Resources that lack a receiving owner enter the orphan queue immediately rather than after discovery latency.
KPI. Transfer latency and completeness. Target: zero resources orphaned by transfer events.
3.7 Lifecycle Ownership
Category: Lifecycle. Enforcement: Mandatory.
Ownership is tracked from resource creation through decommission with continuous accountability. The control closes the loop that 4.6 opens by ensuring that ownership is a continuous attribute of the resource, not a property that exists at provisioning and degrades over time.
Lifecycle ownership produces a chain of custody for every resource. The chain begins at provisioning with the named owner. The chain advances through every transfer, every reassignment, every team reorganization. The chain terminates only when the resource is decommissioned and the decommission is logged. A resource that has lost its chain is a resource that has not satisfied 4.7.
In practice, this means the institution maintains an ownership ledger that is queryable as a time series. A practitioner can ask "who owned this resource on April 12 of last year" and receive a defensible answer. Ownership is not a current snapshot. It is a defended history.
KPI. Lifecycle continuity. Target: 100 percent of resources carry an unbroken chain of custody from provisioning to current state.
3.8 Shared Cost Showback
Category: Transparency. Enforcement: Recommended.
Transparent reporting of shared infrastructure costs allocated to consuming teams. The control is the Ring 4 partner to 4.3 that publishes the allocation back to the consuming teams so they can read, challenge, and act on their share.
Showback is recommended rather than mandatory because some institutions operate under a chargeback model that subsumes showback, and others do not yet have the data primitives to support showback at the team level. The principle is that consuming teams should be able to read what they consume from shared services. The implementation varies with the institution's financial model.
The federation publishes a reference showback report format. The report breaks each consuming team's share of every shared cost into the methodology used (direct, proportional, fixed), the underlying usage signal where applicable, and the trend over the last four quarters.
KPI. Showback report cadence and coverage. Target: monthly cadence, 100 percent of shared costs covered.
3.9 Attribution Hierarchy Mapping
Category: Structure. Enforcement: Recommended.
Multi-level attribution from individual resource to team, department, and business unit. The control extends single-level ownership into a hierarchical view that supports executive reporting and rolled-up exposure analysis.
A resource owner answers "who owns this." The hierarchy answers "what business unit does this dollar support." Practitioners building Ring 4 at scale need both. The hierarchy is the bridge between Ring 4 (Ownership) and Ring 0 (Outcome). A dollar with an owner but no business-unit attribution is a dollar that cannot be tied to a measurable business outcome.
KPI. Hierarchy depth and accuracy. Target: three levels of hierarchy with 95 percent attribution accuracy at each level.
3.10 Financial Accountability Scoring
Category: Measurement. Enforcement: Adaptive.
Scoring teams on ownership practices: tagging compliance, cost awareness, optimization participation. Adaptive because the scoring model varies with institutional culture and the federation has not converged on a single canonical scoring rubric.
The principle is that ownership without accountability is performance theatre. A team that owns resources but does not act on its cost signal is a team that has tagged correctly and governed nothing. Financial Accountability Scoring is the operating layer that converts ownership into behavior.
The federation publishes a calibration table with three rubric versions. Practitioners pick the rubric that matches their institutional model and document the choice for federation review.
KPI. Scoring coverage and movement. Target: every resource-owning team scored quarterly with measurable movement on the rubric over four-quarter windows.
4 . The Pattern Library
Ring 4 across the five canonical stacks.
| Stack | Ring 4 Pattern | |---|---| | Public Cloud | Fourteen-label tagging schema enforced at provisioning. Orphan costs over the published threshold escalate within hours. Cross-account resource ownership reconciled to the central registry. | | SaaS Portfolio | Every subscription has a named owner. Seats reclaimed on offboarding. License waste attributed to the hiring manager. Renewal accountability follows the original owner regardless of role change. | | On-Prem and Hybrid | Rack space, ports, storage LUNs assigned to cost-centers. Asset register synced to HR for role-change reattribution. Decommission events logged in the same ledger as cloud terminations. | | AI and ML | Every model, prompt template, and dataset has a data-product owner. Fine-tuning jobs tied to the engineer who ran them. Inference endpoints attributed to the consuming application. | | Data Platform | Every table has a data steward. Every schema change is attributed. Lineage tracked end-to-end for regulatory defense. Dataset access logs reconcile to the consuming team. |
5 . Industry Applications
Cloud Infrastructure. Tagging governance enforced at the provisioning layer. Orphan-cost escalation wired to the discovery feed. Cross-account ownership reconciled continuously. The federation's Cloud Conformance Pack publishes the reference tagging schema per provider.
Software Development. Every code-owning entity (repository, branch, deployment target) carries an owner. Build artifacts attributed to the merging engineer. Library dependencies attributed to the maintaining team.
SaaS Portfolio. Per-seat ownership tied to the hiring manager. Seat reclamation on offboarding within the published SLA. License waste attribution at the team level for budget conversations.
Government. Asset register reconciled to authorization-to-operate (ATO) ownership. Every resource carries the program-element-code (PEC) and the responsible accountable official. The Public Sector Conformance Pack adds the federal-program-grant attribution layer.
Supply Chain. Vendor relationship ownership at the buyer level. Contract surface markers attributed to the legal team that signed. Tier-one supplier ownership extended to tier-two through pass-through attribution clauses.
AI and ML Operations. Model ownership at the data-product level. Prompt template ownership tied to the prompt engineer. Inference endpoint attribution at the consuming application layer.
6 . The Adversarial Audit
Five vectors.
Vector 1: "Show me a resource in your estate that has no named human owner."
The practitioner runs the orphan query against the discovery feed and produces zero unowned resources or, if any exist, the time-to-remediation contract for each. If the practitioner cannot run the query, Ring 4 has not been claimed.
Vector 2: "Walk me through an ownership transfer event from the last quarter."
The practitioner picks any team reorganization or personnel change from the last quarter and walks the chain of custody for at least three resources affected by the change. The auditor verifies that no resource entered orphan status during the transition. If gaps exist, 4.6 was not enforced.
Vector 3: "Demonstrate that your tagging compliance is enforced at provisioning, not at audit."
The practitioner attempts to provision a resource without the mandatory five labels. The auditor takes the same action. Both attempts fail at the provisioning gate. If either succeeds, 4.1 has not been enforced; the institution is doing audit-time tagging which is failure mode M3.
Vector 4: "Reconcile this shared-cost line to the consuming teams."
The auditor picks an arbitrary shared-cost line from the institution's invoice. The practitioner produces the allocation methodology, the underlying usage signal where applicable, and the consuming team's share. The auditor verifies that the consuming team can read its own share in a published report. If the consuming team has not seen the allocation, 4.8 has not been enforced.
Vector 5: "Who owned this specific resource on this specific date last year?"
The auditor names a resource and a date. The practitioner queries the ownership ledger as a time series and produces the answer. If the ledger does not support time-series queries, 4.7 has not been enforced. The institution holds current ownership but has not built lifecycle ownership.
7 . The Working Capital Math
Ring 4's quantitative spine is the relationship between attribution coverage and recoverable waste.
The federation's calibration is that institutions in Phase 1 typically carry 18 to 25 percent orphan or mis-attributed cost. The orphan-and-mis-attributed band is the recoverable waste pool because it is the spend the institution cannot defend in front of an audit. Moving from Phase 1 to Phase 4 compresses the band into the 1 to 3 percent range.
For an institution with annualized cloud-and-vendor spend $S$, the recoverable Ring 4 waste is approximately:
Recoverable waste ≈ S × (orphan-rate-current minus orphan-rate-target)
A practitioner whose institution carries $200M in annualized spend at a 12 percent orphan rate is sitting on roughly $20M of recoverable waste at a 2 percent target. The math is the federation's calibration anchor for Ring 4 investment.
| Ring 4 Maturity | Orphan Cost Ratio | Tag Compliance Rate | Practical Posture | |---|---|---|---| | Phase 1 (Blind) | 18 to 25 percent | Below 60 percent | Tags exist as policy, not enforcement. Most resources untraceable. | | Phase 2 (Reactive) | 10 to 18 percent | 60 to 80 percent | Tagging campaign at audit time. Drift between campaigns. | | Phase 3 (Coordinated) | 4 to 10 percent | 80 to 92 percent | Provisioning gate active. Discovery feed wired. SLA on assignment. | | Phase 4 (Proactive) | 1 to 4 percent | 92 to 98 percent | Continuous enforcement. Lifecycle ownership ledger live. Orphan escalation automated. | | Phase 5 (Adaptive) | Under 1 percent | Above 98 percent | Hierarchical attribution wired to outcomes. Financial Accountability Scoring producing measurable team movement. |
8 . The 13 Modes of Failure
M1. Tags applied as documentation rather than enforcement. Remedy: provisioning-time gate that rejects unlabeled resources.
M2. Ownership recorded as a team rather than a named human. Remedy: ownership taxonomy upgraded to named individuals with named back-ups.
M3. Tagging campaigns at audit time rather than continuous enforcement. Remedy: continuous compliance scanner with hours-cadence remediation.
M4. Orphan-cost detection running monthly rather than daily. Remedy: daily run with hours-cadence escalation on threshold breach.
M5. Ownership transfers via informal hand-off without formal protocol. Remedy: 4.6 enforced as the only valid path for transfer events.
M6. Shared-cost buckets that never resolve to consuming teams. Remedy: 4.3 enforced with the three-methodology hierarchy.
M7. Lifecycle ownership treated as current snapshot. Remedy: ledger upgraded to a queryable time series with cradle-to-grave continuity.
M8. Hierarchical attribution stopping at one level. Remedy: three-level hierarchy with explicit cost-center-to-business-unit-to-revenue-line mapping.
M9. Tag drift accepted as a fact of operations. Remedy: drift treated as a signal for re-architecting the provisioning system.
M10. Showback reports produced for finance only, not for consuming teams. Remedy: report distributed to the consuming teams who can act on the signal.
M11. Orphan escalation routed to a queue with no SLA. Remedy: federation-published SLA wired to the on-call rotation.
M12. Decommission events not logged in the ownership ledger. Remedy: decommission treated as a first-class event with the same audit standard as provisioning.
M13. Financial Accountability Scoring missing because the rubric was never adopted. Remedy: federation calibration table reviewed and a rubric chosen.
9 . Sidebars
>
Sidebar 4.A . Ownership is a person, not a team. Co-authored, signed at ratification. The federation has reviewed dozens of ownership taxonomies submitted by working group candidates. The most common failure mode is collective ownership: assigning resources to "the platform team" or "the SRE org" or "engineering." Collective ownership is functionally equivalent to no ownership. A team cannot be paged. A team cannot be held in a one-on-one. A team cannot defend a line item in front of a board. Ring 4 is the institution's commitment to named individuals. The named individual carries a named back-up. The back-up is also a named individual. The chain ends at a person, not at a noun.
>
Sidebar 4.B . The orphan cost is the audit cost. Co-authored, signed at ratification. An orphan cost is not a small thing waiting to be cleaned up. An orphan cost is the audit cost the institution will eventually face. Auditors do not accept "we have not yet attributed this line" as an answer. Auditors accept current attribution or they accept reasoned exception. Practitioners building Ring 4 should treat the orphan ratio as the institution's audit-readiness metric. Below 2 percent, the institution can defend its attribution. Above 5 percent, the institution will face a finding.
>
Sidebar 4.C . Why attribution is upstream of optimization. Co-authored, signed at ratification. A practitioner who attempts to optimize an estate that is not yet attributed is a practitioner who will produce changes that look efficient on paper and prove untraceable in practice. Right-sizing a workload that has no owner produces savings that no team can defend. The federation's reading order places Ring 4 (Ownership) before Ring 2 (Optimization) because optimization without attribution is optimization theatre. The savings appear in the ledger. The accountability does not.
10 . The Founder's Annotation Track
>
I want the reader to know that Section 3.2 (Ownership Assignment and SLA) was the most-revised section across the working group review. The first draft had a 24-hour SLA across all environments. The working group's dissent was that production-tier deserves a sharper SLA because the exposure window is larger. The current four-hour figure for production is the working group's calibration, and I held the line on three days for ephemeral environments because the federation should not pretend that test-pod ownership is the same problem as production-pod ownership. The dissent is on the public record at vot.ifo4.org/RING-1000-2026/Ring-4/3.2. I also want to flag that the Tesla forensic in Section 1 was suggested by a working group reviewer who had run Ring 4 implementations at three Fortune 500 firms. I had originally drafted the chapter with the Capital One AWS event as the opener. The reviewer was right that the Tesla case is structurally cleaner because there was no malicious intent: the resource simply drifted into orphan status through normal organizational change. The doctrine reads sharper against a clean drift case than against a dramatic breach.
11 . The Capstone Artifact
The Ring 4 capstone is the Attribution Manifest for the candidate's organization.
The manifest contains, at minimum:
- The tagging schema. The institution's complete label taxonomy with mandatory and recommended fields, validation rules, and the provisioning-gate enforcement evidence.
- The ownership ledger. A queryable time-series record of every resource the institution holds, with current owner, back-up, and chain of custody back to provisioning.
- The orphan report. Current orphan cost ratio with the per-line breakdown and remediation timestamps.
- The shared-cost allocation methodology. The institution's reference document covering direct, proportional, and fixed allocation per shared-cost class.
- The transfer protocol. The institution's documented process for ownership transitions during reorganization or personnel change.
- The hierarchy map. Three-level attribution from resource to team to business unit, with accuracy measurement at each level.
- The accountability scoring rubric. The institution's chosen rubric and current scoring outputs per resource-owning team.
- The named gaps under remediation.
Submitted, signed, and dated. Federation Standards Council reviews. Accepted manifests are filed against the candidate's CFO-R credential and contribute to the federation's public corpus of Ring 4 reference implementations.
12 . Doctrine Q&A
Fifteen calibrated questions. Forty-eight in the proctored examination.
Q1. A team owns a Kubernetes namespace. The namespace owner is listed as "the platform team." Has 4.2 been satisfied?
A. No. 4.2 requires named individuals. Collective ownership is failure mode M2.
Q2. A resource was provisioned eight months ago with correct tags. A subsequent console edit removed the owner tag. The resource is currently orphaned. Which controls failed?
A. Primarily 4.5 (Tag Compliance Enforcement) failed because drift was not detected. Secondary failure in 4.4 (Orphan Cost Detection) if the orphan was not escalated within the published SLA.
Q3. A team reorganization moved twelve resources from team A to team B. Three resources are not currently attributable to either team. What happened?
A. 4.6 (Ownership Transfer Protocol) was not enforced. The transition produced orphans because the protocol's reconciliation step was either skipped or failed.
Q4. Shared cloud-network egress costs are allocated to "shared services" in the institution's monthly invoice. Has 4.3 been satisfied?
A. No. 4.3 prohibits indefinite shared-services buckets. The egress costs must be allocated to consuming teams using direct, proportional, or fixed methodology.
Q5. A practitioner can produce current ownership but cannot answer "who owned this resource on a specific date last year." Which control is missing?
A. 4.7 (Lifecycle Ownership) is missing the time-series query capability. Ownership is being held as a current snapshot rather than a defended history.
Q6. Tag compliance is reported at 87 percent. What phase is the institution operating at?
A. Phase 3 (Coordinated). The federation's Phase 4 target is 92 to 98 percent compliance.
Q7. A SaaS subscription does not have a named owner because the original purchaser left the company two years ago. What is the remediation?
A. 4.6 was not applied at the original departure. Remediation is to assign a current owner immediately, log the transition with the historical gap noted, and reconcile against the SaaS portfolio audit.
Q8. The orphan cost ratio is 9 percent. Is the institution audit-ready?
A. No. The federation's audit-readiness band is below 2 percent. A 9 percent ratio will produce a finding under the standard's audit protocol.
Q9. A consuming team disputes its allocated share of a shared infrastructure cost. What is the federation's standard response?
A. The team is correct to dispute if 4.3 has not been enforced with a published methodology. The remediation is publishing the methodology, the underlying usage signal, and the team's share so the team can read and challenge with evidence.
Q10. Tagging is enforced at provisioning. Drift is detected weekly with quarterly remediation. Is 4.5 satisfied?
A. Partially. 4.5 requires hours-cadence remediation, not quarterly. Weekly detection is acceptable; quarterly remediation is failure mode M3.
Q11. An institution has a rubric for Financial Accountability Scoring but produces no team-level scores. Has 4.10 been claimed?
A. No. The rubric without scoring is documentation, not implementation. 4.10 is adaptive but it requires actual scoring outputs.
Q12. A workload has been running for three years. Its current owner is the third person to hold the role. The chain of custody shows two transfers logged. Has 4.7 been satisfied?
A. Yes, if both transfers were logged with timestamps, signatures, and reconciliation. The federation's standard accepts continuous chains regardless of length.
Q13. An auditor asks "what is your tag drift rate per quarter." The practitioner cannot answer with a single number. What is failing?
A. 4.5 (Tag Compliance Enforcement) is being run but its outputs are not aggregated into a measurable institutional metric. Remediation is publishing the drift rate as a Ring 4 KPI.
Q14. Two resources in different cost-centers have the same owner. The owner left the company yesterday. What happens at midnight tonight?
A. Both resources enter the assignment queue per 4.2's SLA. The escalation tree triggers if the four-hour production window or twenty-four-hour non-production window is breached. The transfer protocol per 4.6 is invoked retrospectively to log the departure and assign a successor.
Q15. What is the canonical Ring 4 forensic the federation uses to ground the chapter?
A. The Tesla cryptocurrency miner discovery of April 2018. The pod's drift into orphan status through normal organizational change is the federation's reference case.
End of Chapter 4 . Edition v0.1 draft . Working group review pending . Ratification target Q3 2026 . Public comment window opens at vot.ifo4.org on the chapter publication date.