Northstar Equipment Services
Four core domains: Capabilities, Value Streams, Organization, and Information. Explore how they connect to deliver customer value and inform strategy and change.
Choose an Atlas tour or explore the map below.
Fictional teaching case · Includes all three episode outcomes through May 6, 2026. Try the independent exercise first. About the sources and earlier assessments.
Guided learning
Four short journeys through the same enterprise.
Loading interactive controls. The enterprise map and complete text reference are available below.
Enterprise
Capabilities, Value Streams, Organization, and Information: four core domains connected around Northstar’s service-reliability challenge.
The direction and guardrails
What needs to become different
Restore Equipment Availability
Selected capabilities; open the full hierarchy
Business concepts, not database tables
Accountability crosses functional boundaries
Choices and dependencies
Implementation context with bounded acceptance
A map with a paper trail
A fictional $780 million equipment-maintenance and rental company with 48 branches in twelve states and 3,200 employees. Its central question: can it make dependable service promises while protecting customer value and margin?
Seven selected enterprise branches with explicit object boundaries. This is an authored hierarchy for the fictional case, not a complete enterprise map or a BIZBOK reference model. Original C-100–C-180 IDs remain stable; original decision labels are retained as aliases. The added parents, siblings, names, and levels are modeling additions, not evidence of approval in Episodes A–C.
Improve service-promise reliability while preserving appropriate branch operating discretion
Customers receive commitments that can be kept, changed transparently, or escalated through a usable exception route
Boundary: A common policy must not prevent branches from responding to legitimate local conditions
Customers receive commitments that can be kept, changed transparently, or escalated through a usable exception route
Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.
Boundary: A common policy must not prevent branches from responding to legitimate local conditions
Protect service margin
Reliability improves without transferring hidden cost or capacity burden to branches, technicians, or adjacent work
Boundary: Margin, technician productivity, implementation cost, and capacity remain visible
Reliability improves without transferring hidden cost or capacity burden to branches, technicians, or adjacent work
Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.
Boundary: Margin, technician productivity, implementation cost, and capacity remain visible
Reduce avoidable customer disruption and repeat work
Fewer customers experience preventable return visits, missed commitments, and recoverable escalations
Boundary: Cause coding, customer escalation, and branch-level variation remain visible
Fewer customers experience preventable return visits, missed commitments, and recoverable escalations
Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.
Boundary: Cause coding, customer escalation, and branch-level variation remain visible
Restore usable equipment availability for the customer operations manager.
The single value stream documented for this case, from a recognized need through customer-confirmed restoration. Recovery retains an open value obligation.
Boundary: A value stream is not a departmental process or a project plan.
Recognize and qualify the customer’s equipment-service need so it can receive an accountable response.
An accepted, actionable need
Boundary: A completed task or handoff does not necessarily mean value was delivered.
Establish and communicate a feasible commitment using the service need, resource signals, and applicable policy.
A credible commitment accepted by the customer
Boundary: A completed task or handoff does not necessarily mean value was delivered.
Coordinate prerequisites and resource confirmations so the promised service can proceed.
Service ready to execute
Boundary: A completed task or handoff does not necessarily mean value was delivered.
Carry out the authorized intervention and establish its equipment-condition result and any remaining exceptions.
Restored equipment condition, or explicit evidence that further recovery is required
Boundary: A completed task or handoff does not necessarily mean value was delivered.
Verify the customer’s receipt of restored availability, reconcile it to the commitment, and determine success, further recovery, or termination without fulfillment.
Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise
Boundary: A completed task or handoff does not necessarily mean value was delivered.
Establish and maintain a recognized equipment-service need, then govern its disposition against the requested customer outcome.
Establish and maintain a recognized equipment-service need, then govern its disposition against the requested customer outcome.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Identify, accept, qualify, and maintain a service need; exclude the customer commitment and authorization of work.
Identify, accept, qualify, and maintain a service need; exclude the customer commitment and authorization of work.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Reconcile the request, promise, and work result; confirm restored availability and customer acceptance, retain open recovery obligations, or record termination without fulfillment.
Northstar must establish that the equipment is usable and the customer confirms the outcome. A recovery handoff leaves the value obligation open.
Boundary: Success can be overstated if revised commitments replace the original customer need.
Establish, validate, communicate, monitor, and revise a governed customer commitment; use resource evidence without planning work or owning resource allocations or final customer-value acceptance.
The customer commitment is the center of this case. Dispatchers need dependable part, skill, geography, and capacity signals before confirming a date—or a usable approved exception.
Boundary: Premature commitments, incompatible regional definitions, and difficult exception routes. Later promises may improve adherence while delaying restoration.
Specify the proposed commitment, its scope, timing, and terms.
Specify the proposed commitment, its scope, timing, and terms.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Assess the proposed commitment against policy and the available feasibility evidence.
Assess the proposed commitment against policy and the available feasibility evidence.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Communicate the commitment and its status to the parties who rely on it.
Communicate the commitment and its status to the parties who rely on it.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Determine the commitment’s current standing and whether its terms are being met.
Determine the commitment’s current standing and whether its terms are being met.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Revise, cancel, or supersede the commitment while retaining its history and obligations.
Revise, cancel, or supersede the commitment while retaining its history and obligations.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Specify and authorize a unit of service work, perform and record it, then reconcile and close its work record; exclude customer-value acceptance and resource ownership.
Specify and authorize a unit of service work, perform and record it, then reconcile and close its work record; exclude customer-value acceptance and resource ownership.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Translate an accepted need into authorized work scope, method, and prerequisites; exclude capacity assignment and execution.
Translate an accepted need into authorized work scope, method, and prerequisites; exclude capacity assignment and execution.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Perform and record the authorized equipment intervention and its exceptions; exclude customer acceptance and promise policy.
Perform and record the authorized equipment intervention and its exceptions; exclude customer acceptance and promise policy.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Reconcile recorded work, consumption, and exceptions and determine administrative closure or cancellation; closure alone does not prove delivered customer value.
Reconcile recorded work, consumption, and exceptions and determine administrative closure or cancellation; closure alone does not prove delivered customer value.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Govern the identity and engagement of people whose work the enterprise uses, their qualifications and availability, and their assignment to demand; cross-map agreements, payments, and organizational units.
Govern the identity and engagement of people whose work the enterprise uses, their qualifications and availability, and their assignment to demand; cross-map agreements, payments, and organizational units.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Establish and maintain a person’s working relationship with the enterprise, including entry, changes, and exit.
Establish and maintain a person’s working relationship with the enterprise, including entry, changes, and exit.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Establish and maintain the evidence of a person’s skills and qualifications.
Establish and maintain the evidence of a person’s skills and qualifications.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Determine the person’s available time, location, and capacity constraints.
Determine the person’s available time, location, and capacity constraints.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Match authorized demand to qualified people, time, geography, and capacity; govern the resulting assignments without owning parts or customer commitments.
Qualified people, time, geography, and capacity must line up. The rural branch has limited skill substitution and long travel.
Boundary: The compact SCALE workspace assigns a coordination owner to ORG-05. The detailed capability register assigns performance accountability to ORG-07. This Atlas keeps ORG-07 accountable and maps ORG-05 as a regional contributor.
Define and acquire physical components used in equipment service, govern their availability and use, and retire unusable or obsolete components; cross-map suppliers, payments, and equipment assets.
Define and acquire physical components used in equipment service, govern their availability and use, and retire unusable or obsolete components; cross-map suppliers, payments, and equipment assets.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Establish and maintain the identity, specification, and permitted use of a physical service component.
Establish and maintain the identity, specification, and permitted use of a physical service component.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Obtain and accept components that satisfy the defined service need.
Obtain and accept components that satisfy the defined service need.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Determine, reserve, position, consume, release, and expire availability of service components; exclude technician assignments and customer commitments.
“Allocated” did not consistently mean a confirmed reservation. ORG-08 owns BO-05; its inventory source is only provisional for R1.
Boundary: Enterprise source authority remains open under OI-06; manual controls require recurring capacity.
Determine and govern withdrawal or disposal of unusable or obsolete components.
Determine and govern withdrawal or disposal of unusable or obsolete components.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Define business measures and guardrail thresholds, determine their observed values, and interpret and govern their use; exclude source transactions and operational remediation.
Measures preserve the version of the promise, population, period, scope changes, and financial guardrails.
Boundary: Later-period confirmation and policy compliance are not cumulative measures; they are not nested sets.
Specify a measure’s meaning, calculation, population, period, and guardrail thresholds.
Specify a measure’s meaning, calculation, population, period, and guardrail thresholds.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Calculate and substantiate the measure’s value from governed evidence.
Calculate and substantiate the measure’s value from governed evidence.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Interpret, explain, review, and govern use of the measure and any decision implications.
Interpret, explain, review, and govern use of the measure and any decision implications.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Establish shared business meaning, semantic accountability, quality requirements, and controlled changes to information definitions; exclude the operational decisions represented by that information.
Shared meaning and source authority must survive handoffs among Dispatch, Supply, Operations, and Technology.
Boundary: Do not transfer operating accountability to information stewards.
Specify a concept’s meaning, category, types, states, and typed relationships.
Specify a concept’s meaning, category, types, states, and typed relationships.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Assign and maintain accountable owners and stewards for the definition.
Assign and maintain accountable owners and stewards for the definition.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Specify the quality rules and thresholds associated with the definition.
Specify the quality rules and thresholds associated with the definition.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
Evaluate, authorize, version, and communicate changes in shared business meaning.
Evaluate, authorize, version, and communicate changes in shared business meaning.
Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.
A customer-recognized need for equipment service that Northstar has accepted for evaluation or action.
ticket; service call; case
Boundary: A concept is distinct from a report, database field, or application record.
A governed commitment to provide a defined service outcome within stated conditions and timing.
Preserve the original commitment, linked revisions, cancellation reasons, and recovery obligation.
Boundary: ETA is an estimate; a commit date is an attribute. Neither is automatically the business commitment.
An authorized unit of service work with scope, asset, status, and completion evidence.
job; service order
Boundary: A concept is distinct from a report, database field, or application record.
A uniquely recognized item of customer equipment whose condition and service history matter.
unit; machine: contextual shorthand. serial: identifier, not an object synonym.
Boundary: A concept is distinct from a report, database field, or application record.
A time-bounded allocation of a specific part quantity to planned service work.
Ownership was proposed in Episode A and confirmed for ORG-08 in Episode B. The inventory record remains a provisional R1 source with twice-daily reconciliation.
Boundary: Seven of 24 inspected sequences had delayed updates; four uses of “allocated” did not mean confirmed. This purposive diagnostic is not an enterprise defect rate.
A governed allocation of a qualified technician and time window to service work.
An accepted assignment and verified skill qualification are separate checks.
Boundary: The detailed object register assigns ORG-07 ownership; ORG-05 coordinates regional capacity. The compact workspace uses ORG-05 as owner, so the different scopes remain explicit.
Needs equipment restored when promised
Accepts, changes, or cancels the customer commitment on behalf of the customer
Boundary: Architecture stewardship does not confer investment or operating authority.
Balances customer commitments, capacity, margin, and local conditions
Owns branch adoption, local capacity choices, and use of the approved exception route
Boundary: Architecture stewardship does not confer investment or operating authority.
Creates feasible promises and sequences work
Applies policy and raises exceptions; cannot waive enterprise guardrails
Boundary: Architecture stewardship does not confer investment or operating authority.
Executes work and records actual conditions
Confirms execution facts and exception causes
Boundary: Architecture stewardship does not confer investment or operating authority.
Coordinates capacity and resolves cross-branch operating conflicts
Approves defined regional exceptions and is accountable for readiness across participating branches
Boundary: Architecture stewardship does not confer investment or operating authority.
Represents customer outcome and service recovery
Owns customer-disruption definition and service-recovery practice
Boundary: Architecture stewardship does not confer investment or operating authority.
Owns field work planning, scheduling, execution, and workforce capacity
Approves operating practices within delegated authority
Boundary: Architecture stewardship does not confer investment or operating authority.
Owns part-availability operating performance
Approves part-reservation rules and operating remediation
Boundary: Architecture stewardship does not confer investment or operating authority.
Sponsors I-01 and owns the service outcome
Accountable for C-110 and C-170 performance and approves POL-01 with required contributors
Boundary: Architecture stewardship does not confer investment or operating authority.
Owns enterprise information-governance policy
Confirms business-object ownership and stewardship; does not own service performance
Boundary: Architecture stewardship does not confer investment or operating authority.
Owns technology standards and service risk
Approves technology standards; does not own service-policy outcomes or vendor value claims
Boundary: Architecture stewardship does not confer investment or operating authority.
Protects financial definition and investment discipline
Governs M-03 and validates cost and margin evidence
Boundary: Architecture stewardship does not confer investment or operating authority.
Balances value, capacity, risk, and opportunity cost
Approves, conditions, defers, or rejects funding and later scale/procurement gates
Boundary: Architecture stewardship does not confer investment or operating authority.
Maintains the decision frame and architecture trace
Frames, models, tests, recommends, and records; does not take the business decision
Boundary: Architecture stewardship does not confer investment or operating authority.
Brings Operations, Customer, Field, Supply, Information, Technology, Finance, and Delivery evidence together for the authorized release
Under authority delegated by ORG-13, may activate, stagger, adapt, pause, or stop R1 within the approved scope and cost/capacity band. Only where a governed guardrail explicitly permits, it may authorize one contained remediation interval to the next formal review after the named owner validates the breach; it may not waive or renew the exception, expand to R2, exceed an investment boundary, or reopen procurement.
Boundary: Architecture stewardship does not confer investment or operating authority.
Participating R1 branch units
Participating R1 branch units
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Regions supporting the R1 branches
Regions supporting the R1 branches
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Part availability and reservation operations
Part availability and reservation operations
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Enterprise service performance and promise policy
Enterprise service performance and promise policy
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Shared business information and stewardship policy
Shared business information and stewardship policy
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Collaborative governance team for the authorized R1 release
Collaborative governance team for the authorized R1 release
Boundary: Organizational contribution does not transfer decision rights or create a capability parent.
Proposed bounded business change, not approved technology.
The case’s change boundary connects policy, confirmation, exception practice, adoption, and measurement.
Boundary: No recorded decision authorizes enterprise procurement or twelve-branch activation.
Cumulative latest-accepted-promise adherence;92%R1 gate versus95%strategic target. Original promise and restoration outcomes remain balancing measures.
Latest accepted promise adherence is only one lens on the customer’s experience.
Boundary: The 82% enterprise dashboard is not a comparable pilot baseline. The 92% R1 gate does not replace the 95% strategic target.
Repeat visits with disputed preventable-cause coding.
Repeat visits with disputed preventable-cause coding.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Finance-governed cumulative margin and work-mix interpretation.
Finance-governed cumulative margin and work-mix interpretation.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Recorded part/skill confirmation;90%later-period gate; not identical to full policy compliance.
Recorded part/skill confirmation;90%later-period gate; not identical to full policy compliance.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Productivity deterioration with work-mix explanation.
Productivity deterioration with work-mix explanation.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Complete workflow or valid approved exception;85%day30 and95%later-period gates. Not nested within M-04.
Complete workflow or valid approved exception;85%day30 and95%later-period gates. Not nested within M-04.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
At most$300k fully loaded change cost and6peak temporary FTE; forecast excess requires prior scope/funding action; recurring burden separate.
At most$300k fully loaded change cost and6peak temporary FTE; forecast excess requires prior scope/funding action; recurring burden separate.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Approved R1 policy: confirmation or a complete approved exception; preserve original/revised promise lineage,communication and recovery.
Approved R1 policy: confirmation or a complete approved exception; preserve original/revised promise lineage,communication and recovery.
Boundary: Policy approval does not establish adoption or sufficient operating capacity.
Escalations attributable to a missed or changed promise per 100 eligible commitments.
Escalations attributable to a missed or changed promise per 100 eligible commitments.
Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.
Can the defined policy, information, exception, and operating practices work under three intentionally different conditions and produce decision-grade measures using existing systems?
A three-branch experiment using existing systems and controlled manual work. The v1.2 reference path releases $15k for diagnosis, up to $75k cumulatively for preparation, and at most $300k after a separate operating-entry decision.
Boundary: Operational feasibility at day 90 does not establish improved customer value or enterprise repeatability.
Can the operating model be repeated across regions and broader work types without unacceptable local workarounds, cost, or performance variance?
Twelve-branch repeatability is a future release boundary. DEC-005 permits design/readiness investigation only.
Boundary: Activation is not authorized. Do not treat the diagram as an approved roadmap.
What enterprise operating model and automation are justified by repeatable evidence?
Enterprise rollout and only the technology required for confirmed residual gaps
Boundary: Platform procurement requires its own business case and decision after repeatability evidence; R2 success does not automatically select a vendor.
One usable rule for creating, changing, cancelling, and recovering customer commitments
O-01/O-02/O-03, BO-02, Operations and Customer approval
Boundary: Original Episode A status: Proposed; not approved merely because R1 is funded. Later readiness and results require the episode evidence.
Dispatcher can distinguish confirmed, provisional, and unavailable prerequisites
BO-05 owner/source decision; skill-data validation
Boundary: Original Episode A status: Proposed. Later readiness and results require the episode evidence.
Promise reflects geography and capacity while legitimate local discretion remains usable
POL-01, M-07, the one-shift exception criterion, and named escalation authority
Boundary: Original Episode A status: Proposed. Later readiness and results require the episode evidence.
Three branches can operate, audit, support, and reverse the change
CP-01–CP-03 and readiness evidence
Boundary: Original Episode A status: Proposed. Later readiness and results require the episode evidence.
Decision forums can continue, adapt, scale, procure, or stop using governed evidence
M-01–M-08, E-008–E-010
Boundary: Original Episode A status: Proposed. Later readiness and results require the episode evidence.
A reservation/skill-status feed and dispatcher exception queue using existing systems.
A credible alternative or complement to the operating experiment. The planning range is $60–120k and one to two temporary FTE, conditional on usable source semantics.
Boundary: It cannot fix technician scarcity, travel, or disputed promise policy. No approval or benefit is implied.
Clarify definitions and improve reporting without changing the promise practice.
$25–75k and 0.5–1 temporary FTE are planning ranges in E-007.
Boundary: It does not directly test or change operating practice.
Procure and deploy the proposed enterprise scheduling product.
The vendor proposes $4–7 million over 18–24 months. A controlled demonstration blocked commitments with missing part/skill fields.
Boundary: No live Northstar feed, representative rural work, adoption evidence, or customer-value experiment supported the demonstration.
A physical component used in equipment service.
Context concept from the corrected hierarchy. Part Reservation depends on a quantity of this concept.
Boundary: This context concept is an authored modeling addition, not new operating evidence.
A person whose work is used by the enterprise.
Context concept from the corrected hierarchy. Technician Assignment allocates the person’s capacity.
Boundary: No additional people, roles, or staffing levels are inferred.
The existing inventory record used as the provisional R1 reservation-status source.
E-008 accepts it for R1 only, with twice-daily reconciliation. This Atlas ID identifies an already documented record; no product or database design is invented.
Boundary: A named record does not establish an enterprise system of record.
The existing record accepted for R1 under versioning, original/revised linkage, and audit rules.
An Atlas identifier for the supporting record in E-008, not a new application.
Boundary: R1 acceptance does not select enterprise future-state technology.
Only the first $15k is released initially within a conditional $150–300k A1/R1 envelope. Preparation and activation each require subsequent decisions.
Recorded fictional reference disposition. Conditions remain attached to the decision.
Boundary: A later result does not rewrite what was knowable at the original decision.
Keep procurement deferred pending repeatability-quality evidence, residual-gap analysis, and a separate comparison and authorization.
Recorded fictional reference disposition. Conditions remain attached to the decision.
Boundary: A later result does not rewrite what was knowable at the original decision.
Authorize a staggered start after remaining training and baseline reconciliation. Temporary source and backup-approver conditions expire at day 30 unless explicitly reviewed.
Recorded fictional reference disposition. Conditions remain attached to the decision.
Boundary: A later result does not rewrite what was knowable at the original decision.
Continue only to day 90 under the delegated margin exception. Narrow admissions, repair controls, review workload, and prohibit expansion.
Recorded fictional reference disposition. Conditions remain attached to the decision.
Boundary: A later result does not rewrite what was knowable at the original decision.
Authorize R2 design/readiness investigation only. Require customer-value investigation; prohibit twelve-branch activation and retain procurement deferral.
Recorded fictional reference disposition. Conditions remain attached to the decision.
Boundary: A later result does not rewrite what was knowable at the original decision.
Fulfillment of the original commitment within the retained-scope completed-restoration cohort.
Atlas identifier for an existing v1.2 customer-outcome measure. Exact counts are authored teaching data.
Boundary: Descriptive comparison without a control group or case-mix adjustment; no causal attribution.
Mean elapsed restoration hours within the retained-scope completed-restoration cohort.
Atlas identifier for an existing v1.2 customer-outcome measure. Exact counts are authored teaching data.
Boundary: Descriptive comparison without a control group or case-mix adjustment; no causal attribution.
The current case is the learning edition (v1.2). The original workbook examples (v1.1) provide structural reference material and earlier illustrative assessments. They do not establish current performance. Guide to the materials.
Northstar is wholly fictional. “Established” means stated in the teaching case, not observed in a real enterprise. Existing hierarchy additions are authored modeling context. New impact paths are labeled as inferences or illustrative extensions. Archived capability ratings are judgments; they are not measured maturity, investment priorities, or probabilities of success.
The current learning evidence takes precedence for measurement periods and reference decisions. Capability boundaries and normalized names come from the corrected hierarchy. Detailed workbook accountability is retained where the compact SCALE workspace uses a regional coordination owner; the affected detail panels explain that discrepancy.