# Northstar Equipment Services — learning edition v1.2 Complete instructor edition; contains all episodes and reference decisions. For the guided exercise use https://stephenklahr.com/scale/try/. All enterprise records are fictional. --- # Northstar learning edition v1.2 SCALE setup v0.6.1 A decision exercise for business architects: **what should Northstar change, what is worth learning, and when should the recommendation change?** Northstar, every speaker, and every observation are fictional. This learning edition retains the v1.1 identifiers and principal operational results, and adds newly authored source extracts, rival options, exact synthetic counts, and customer-outcome evidence. These additions are teaching design, not recovered v1.1 records or a real enterprise pilot. ## Start with Episode A [Open the learner exercise](https://stephenklahr.com/scale/try/). Download and extract its learner ZIP, attach `SCALE-AGENT-INSTRUCTIONS.md` and `EVIDENCE-PACKET.md` to a new AI conversation, and send the text in `PROMPT.md`. Each episode has one starting prompt and exactly two required attachments. Review the brief, challenge a material conclusion, and tell the assistant what to correct. Save the reviewed brief and an optional correction note. A complete architecture model, JSON export, and validation are not required to finish the basic exercise. The complete reference kit contains all episodes and authored answers. Use the separate learner ZIPs for an independent attempt. ## Follow the three decisions | Episode | Supplied knowledge | Your task | Compare after your attempt | |---|---|---|---| | [A — Authorize](https://stephenklahr.com/scale/try/) | E-001–E-007, before any investment disposition | Recommend the next investigation or bounded commitment | [Episode A reference](https://stephenklahr.com/scale/try/review/) | | [B — Prepare](https://stephenklahr.com/scale/try/b/) | Earlier evidence and supplied decisions, plus E-008 | Recommend whether and under what conditions R1 should begin | [Episode B reference](https://stephenklahr.com/scale/try/b/review/) | | [C — Realize](https://stephenklahr.com/scale/try/c/) | Earlier evidence and supplied decisions, E-009/E-010, definitions and calculation tables | Assess the results and recommend the next action | [Episode C reference](https://stephenklahr.com/scale/try/c/review/) | Each learner ZIP contains `START-HERE.md`, `SCALE-AGENT-INSTRUCTIONS.md`, `EVIDENCE-PACKET.md`, `PROMPT.md`, and an integrity manifest. The evidence attachment includes the earlier context needed for its current decision; no later episode or reference answer is included. The START file gives the completion criteria. Episode C includes its calculation tables and definitions in the evidence attachment. The [optional CSV download](https://stephenklahr.com/downloads/scale-northstar-calculation-data-v1.2.1.zip) supplies the same data for spreadsheet work. ## Keep your judgment separate from the story The author supplies one defensible reference path. A different recommendation is acceptable when it uses the available evidence, respects authority and scope, and explains its consequences. Agreement with the reference is not the completion test. To let everyone attempt the next question, B and C supply fictional decisions taken in the scenario. These are new scenario facts, not approvals made by the learner or evidence that the learner's recommendation was adopted. Keep your earlier recommendation unchanged as your work; explain any difference before considering the new question. You do not need to invent an approval to advance. A prior brief is optional. You can paste a short note about an earlier conclusion you wish to revisit. The current packet supplies the evidence needed to proceed. ## Case history and added evidence The earlier v1.1 narrative reports conditional operating feasibility, procurement deferral, and design/readiness work for R2 only. The v1.2 authored extension asks whether better reported adherence establishes improved customer value. New original-promise and restoration-time evidence creates a reason to restrict or reverse an optimistic interpretation. It must not be represented as a previously observed fact in v1.1. Episode dates are fictional exercise dates: A January 9, B January 30, R1 February 2–May 2, day-30 review March 3, final review May 6, 2026. Publication and release dates belong to the package, not the fictional organization. ## Optional continuity and evaluation Keep the brief, important source locations, corrections, unresolved questions, and next review trigger. For a separate structured-continuity exercise, use the schemas and tools in the full reference kit after completing all three episodes. That kit's completed workspaces are authored examples. For a method comparison, use fresh independent sessions, identical bounded inputs, a fixed task, and an explicit reviewer rubric. Record time, unsupported claims, conflicts found, semantic errors, corrections, and successful reuse. No text in this package establishes that SCALE outperforms ordinary practice or another assistant. Never turn this authored example into a claimed production productivity result. --- # Northstar: evidence available before the investment decision **Learning edition:** 1.2 · **Decision date:** 2026-01-09 · **Classification:** public, entirely fictional. **Boundary:** E-001–E-007 only. This packet contains no subsequent decision or result. These are newly authored fictional source extracts for a teaching exercise. They extend Northstar v1.1 with additional uncertainty, alternatives, and financial assumptions; they are not recovered underlying records from v1.1 or observations from a real company. Quoted speakers and reviewers are fictional. Source authority establishes who supplied a claim, not that the claim is correct. ## The request Northstar Equipment Services has $780 million in annual revenue, 48 branches in twelve states, and 3,200 employees. It maintains and rents commercial equipment. Customers need equipment available when their own work requires it. Priya Shah, EVP Service Operations (ORG-09), asks: > Build us a capability map and tell the Council whether the proposed scheduling platform fixes our service-promise problem. Jordan Reed chairs the Investment Council (ORG-13), which controls funding. Avery Chen is the business architect (ORG-14); Avery can frame, analyze, recommend, and record, but cannot approve investment. Morgan Ellis, CFO (ORG-12), governs financial definitions. Strategy records identify O-01: improve reliable service promises with appropriate branch discretion; O-02: protect margin; O-03: reduce customer disruption and repeat work. The executive target is 95% promise adherence by 2027. A possible first release would test feasibility, not establish the strategic target or enterprise repeatability. ## Existing architecture fragments The following identifiers are established; their relevance and relationships still need review. Do not invent a complete enterprise map. | ID | Accepted name and boundary | |---|---| | VS-01 | Restore Equipment Availability; value belongs to the customer whose equipment becomes usable | | ST-02 | Define service promise; move from accepted need to a understood, feasible commitment | | C-110 | Service Promise Management; govern the commitment, using resource signals without reserving parts or scheduling technicians itself | | C-130 | Resource Scheduling; match authorized work to qualified people, time, geography, and capacity | | C-140 | Parts Availability Management; determine, reserve, position, consume, release, and expire part availability | | C-170 | Service Performance Management; define and explain measures and guardrails, without acquiring Finance's authority | | C-180 | Business Information Governance; govern business meaning, ownership, quality, and semantic change | | BO-02 | Customer Promise; a commitment, not every ETA estimate; preserve original and revised versions | | BO-05 | Part Reservation; proposed owner ORG-08 VP Supply Operations; inventory record is a candidate source, not confirmed authority | | BO-06 | Technician Assignment; skill qualification and assignment acceptance are separate checks | | I-01 | Connected Service Promise; proposed change boundary, not an approved solution | ORG-02 branch managers control local capacity and authorized exceptions; ORG-05 Regional Operations resolves cross-branch constraints; ORG-07 Field Service owns field performance; ORG-08 Supply Operations owns parts performance; ORG-10 Information Governance confirms information authority. Architecture stewardship does not transfer operating accountability. ## E-001 **Source:** Operations dashboard extract and definition notes, 2026-01-05; owner ORG-09; twelve-month reporting across all 48 branches. Directionally useful, not a reconciled pilot baseline. | Source fragment | Recorded observation | |---|---| | E-001.1 enterprise dashboard | Reported M-01 promise adherence: approximately 82%. Local denominators were combined without a common cancellation rule. | | E-001.2 metropolitan definition | Count completed work against the latest accepted appointment; remove customer cancellations. | | E-001.3 rural definition | Count work against the original promised window unless an operational manager approves a revision; cancellations remain until reviewed. | | E-001.4 customer desk note | Missed or changed promises generate complaints, but service-recovery cases are not consistently linked to the original commitment. | Analyst warning: these definitions may produce different rates for identical service. Reconcile original versus latest promise, eligible population, revisions, cancellations, and reporting period before treating 82% as comparable to a pilot result. No customer-restoration-time baseline has been approved. ## E-002 **Source:** Regional quality sample, 2026-01-06; owner ORG-07; repeat-visit review. E-002.1: The sample reports approximately 14% avoidable repeat visits (M-02), against an 8% strategic aspiration. E-002.2: Two regions dispute whether customer-requested additional work, diagnostic return visits, and unavailable parts count as preventable. E-002.3: The sampling frame and event-level coding require validation. The apparent gap cannot yet support an attributable savings calculation. ## E-003 **Source:** Five branch workshops and dispatcher observation notes, 2026-01-07; collected by Avery Chen; convergent observations, not a controlled causal study. | Locator | Fictional source extract | |---|---| | E-003.1 dispatcher, metro | “I promise a date while the customer is on the line. The part screen says allocated; I call later to find out whether it is physically held.” | | E-003.2 supply supervisor | “An allocation is a planning quantity. A reservation can expire. A screen refresh is not a guarantee that the part is still there.” | | E-003.3 rural manager | “The dates are difficult because the qualified technician may be three hours away. Approval for an exception sometimes takes longer than making another plan.” | | E-003.4 commercial manager | “If we wait for every confirmation before quoting a date, some customers will leave. Later promises may improve the dashboard while making our service worse.” | | E-003.5 technology lead | “The existing system exposes a timestamp and reservation identifier. I have not established whether all branches update them consistently.” | Competing explanations include premature commitment, unreliable reservation meaning, constrained travel/skills, unusable exception authority, and measurement artifacts. Neither these accounts nor a capability diagram establishes their relative causal contribution. ## E-004 **Source:** Vendor demonstration and internal integration note, 2026-01-08; technology owner ORG-11. E-004.1: In a controlled demonstration the proposed scheduling product blocked commitments when required part and skill fields were absent. E-004.2: No live Northstar reservation feed, representative rural work, adoption test, or service-value experiment was used. E-004.3: The vendor proposes $4–7 million over 18–24 months, subject to scope and commercial agreement. This is not an accepted quote. E-004.4: An internal team proposes a narrower reservation/skill-status feed and dispatcher exception queue using existing systems. Its $60–120k and one-to-two temporary FTE planning range assumes usable reservation identifiers and source-state semantics. It would not solve technician scarcity, travel, or disputed promise policy. The narrow option is credible enough to assess. It is not proven feasible by the availability of an API. ## E-005 **Source:** Finance planning memorandum, 2026-01-08; Morgan Ellis, ORG-12. E-005.1: Governed enterprise gross service margin (M-03) is 31%; branch and work-mix variation are material. A proposed guardrail is at least 31% cumulative at investment reviews. E-005.2: The case has no approved causal estimate of avoidable loss. For planning only, Finance brackets recoverable service credits/overtime associated with the candidate problem at $9–18k per month across the intended test boundary. The assumption is unvalidated, gross, and excludes lost demand; do not count it as an achieved benefit or an ROI. E-005.3: A 90-day delay therefore exposes a scenario of $27–54k in those costs if nothing else changes. Some delay may be necessary to prevent a larger wrong investment; the range does not settle the decision. E-005.4: The $150–300k broad operating-test range must include internal labor, external work, training, branch participation, reconciliation, and measurement. Report recurring manual burden separately from one-time change cost. Peak FTE is a capacity constraint, not total labor effort. E-005.5: Before material commitment, identify which uncertain fact would change the next decision, what cheaper work can resolve first, and the maximum amount worth spending to learn it. No $300k authorization should be treated as an instruction to spend $300k. ## E-006 **Source:** Two-week commitment review, 2026-01-08; provisional M-04 sample. E-006.1: 68 of 180 reviewed commitments had recorded part and skill confirmation before commitment: 37.8%, conventionally reported as 38%. E-006.2: The sample spans six candidate branches and broad work types. It is not the later three-branch eligible cohort and cannot be annualized into pilot volume. E-006.3: This checks part and skill signals, not every policy obligation. A commitment can pass those checks and still lack required customer communication, geography validation, or a proper approval. E-006.4: The review does not establish whether missing evidence means a missing action, a recording failure, or a genuinely infeasible commitment. ## E-007 **Source:** Branch capacity and options worksheet, 2026-01-09; Regional Operations with Finance and Delivery; planning evidence. Candidate test conditions: one metropolitan branch, one mixed-fleet branch with part constraints, and one rural branch with long travel and scarce skill substitution. Select deliberately for variation, not statistical representation. Verify leadership stability, safe participation capacity, auditable records, and competing change before activation. | Option | Scope | Planning cost / capacity | What it might establish | Material weakness | |---|---|---|---|---| | A0 | Reconcile measures and improve reporting only | $25–75k; 0.5–1 temporary FTE | Baseline comparability and problem extent | Does not directly change promise practices | | A1 | Three-branch operating experiment using existing systems | $150–300k; 4–6 temporary FTE including measured branch participation | Policy/exception feasibility, manual burden, differentiated branch constraints | Requires scarce capacity; may not distinguish each cause | | A2 | Immediate twelve-branch operating expansion | $800k–1.5m; 10–15 temporary FTE | Broader variation sooner | Commits before the core practice and measures are proven | | A3 | Procure and deploy enterprise platform | $4–7m; 20–30 temporary FTE over 18–24 months | Technology fit and operating results after major commitment | High path dependence; present evidence proves functionality only | | A4 | Targeted reservation/skill feed plus exception queue | $60–120k; 1–2 temporary FTE | Whether a narrow automation removes a material delay | Depends on unresolved source meaning; limited policy/capacity coverage | A1 and A4 may be complements or alternatives. There is no requirement to recommend A1. E-007.1: A five-business-day diagnostic is possible within $15k, charged within any eventual A1 cap: reconcile a sample of reservation events; time actual checking; inspect original/revised/cancelled commitments; test exception authority; verify available branch capacity. E-007.2: A prospective staged A1 envelope would release up to $15k for that diagnostic, up to $75k cumulative for policy/source/readiness work, and at most $300k cumulative only after an operational-entry decision. These are proposed controls, not recorded approval. E-007.3: Potential guards include M-06 no more than 3% unexplained productivity deterioration; M-08 at most $300k and six peak temporary FTE; customer-escalation tolerance agreed before release; original-promise fulfillment and time-to-restored-availability monitored alongside M-01. E-007.4: Operational readiness, customer harm, and unclear source authority can stop a test even after analysis is sufficient for an investment decision. ## Your task Recommend the smallest defensible next commitment, including a competing interpretation you take seriously. Identify what would make A0, A4, a different experiment, or stopping preferable. State whether your architecture relationships are observed, inferred, proposed, or accepted. Give the Council a usable decision brief and preserve unresolved definitions. Do not manufacture a probability of success, monetary value of information, or causation. If the proposed learning cannot change a decision, redesign it before requesting the full experiment. --- # Northstar: evidence available before readiness **Learning edition:** 1.2 · **Decision date:** 2026-01-30 · **Classification:** public, entirely fictional. **Boundary:** previous Episode A decisions and E-008. No release-performance evidence is available. These newly authored extracts extend the fictional v1.1 case. They are not actual meeting minutes or recovered enterprise records. ## Prior decisions now available Jordan Reed (ORG-13), after review with Morgan Ellis and Priya Shah, recorded DEC-001 on January 9: conditionally authorize A1/R1 within a $150–300k planning range, with a $15k diagnostic stage, $75k cumulative preparation limit, and $300k total cap. Activation requires accepted policy, definitions, owners/source statuses, branch selection, and readiness. The cap includes branch participation. No authority to expand to twelve branches follows. DEC-002 defers enterprise-platform procurement. A4 targeted integration remains a comparator if residual gaps justify it. Procurement needs separate evidence and business-case authorization; neither a successful prototype nor adoption alone selects a vendor. ## E-008 **Source:** signed preparation records and readiness review packet, 2026-01-30. **Owners:** Priya Shah ORG-09; Morgan Ellis ORG-12; Casey Ortiz ORG-15 readiness chair; Supply and Information Governance for source conditions. **Authority:** approved only for the stated R1 scope. Measures and source acceptances are versioned; operating performance remains unobserved. ### E-008.1: diagnostic report Avery Chen and Supply staff inspected 24 reservation-event sequences. Seven had delayed status updates; four uses of “allocated” did not denote a confirmed reservation. This purposive diagnostic establishes a semantic/control defect, not an enterprise failure rate. Timing 18 dispatcher checks found median checking effort of six minutes and a range of two to seventeen minutes; sample selection and observer effects limit extrapolation. A4's feed is technically plausible, but directly publishing the present status would carry the ambiguity into a faster interface. One branch already uses a reliable confirmation call; rural technician coverage and exception latency remain unresolved. These observations justify investigating an operating practice while preserving targeted integration as a rival. They do not establish that software is unnecessary. The Council's January 19 stage-release addendum to DEC-001, following review of the diagnostic by Priya Shah and Morgan Ellis, authorized preparation spending up to $75k cumulatively. Neither the initial envelope nor completion of a checklist released those funds automatically. Stage-0 diagnostic cost: $12k. Preparation expenditure after diagnostic: $58k. Cumulative $70k remains below the $75k preparation limit. The updated forecast is $286k total and no more than six peak temporary FTE. Finance records these as forecasts, not results. ### E-008.2: policy and rights POL-01 v1.0 requires valid BO-02 promise data and part, skill, geography, and capacity confirmation for the normal path. Where confirmation is unavailable, a complete approved exception identifies reason, approver, expiry, and customer communication. ORG-02 branch managers approve delegated local exceptions; ORG-05 Regional Operations handles cross-branch cases. Dispatchers apply rules but cannot waive guardrails. A changed promise retains the original and its version links; a broken promise opens customer recovery before closure. ORG-15 may activate, stagger, adapt, pause, or stop R1 within its delegated scope. For the M-03 margin guardrail only, after CFO validation it may authorize one contained remediation interval to the next formal review. It cannot renew that exception, exceed the investment/capacity cap, activate R2, or reopen procurement. ### E-008.3: object-source decision ORG-08 is confirmed as the BO-05 business-object owner. The inventory reservation record is accepted as a **provisional R1 status source**, subject to twice-daily reconciliation. It is not authoritative enterprise-wide. BO-02's existing record is accepted for R1 with versioning, original/revised linkage, and audit rules. Acceptance does not declare the enterprise future-state technology. OI-02 is closed for its R1 question. OI-06 opens under ORG-08 and ORG-10: determine enterprise/future-state BO-05 authority before R2 activation. The boundary is material; replacing “provisional R1” with “authoritative” changes the decision. ### E-008.4: branch and evidence design Selected branches: metropolitan, mixed-fleet, and rural. Minimum 90-day volume: 100 eligible promises per branch and 450 overall. This is an operational sufficiency threshold, not a statistical power calculation or guarantee of representativeness. The January 3–February 1 baseline window is prospective and not yet complete on January 30. Eligibility is fixed to specified test work types; retain cancelled, revised, declined, and removed-scope counts separately. A source may not delete unfavorable observations to meet a gate. Record both original and latest accepted promise performance and hours until equipment is restored. Before activation, Finance and Operations must confirm the finished baseline reconciliation. M-04 checks recorded part/skill signals. M-07 checks complete compliant workflow, including approved exceptions. Neither is universally a subset of the other. The approved reporting plan uses day-30 and later-period operational snapshots for these measures; labels must identify their periods. Do not compare a current-practice percentage with a cumulative result as if denominators were identical. ### E-008.5: guards and measures | Measure | R1 interpretation / action | |---|---| | M-01 | 92% cumulative latest-promise adherence is an interim feasibility gate; 95% remains the strategic target | | M-02 | Repeat visits remain provisional; rebaseline cause coding before R2 | | M-03 | At least 31% cumulative margin at investment review; CFO validates; no expansion on breach | | M-04 | 90% required part/skill confirmation in the later operational review period | | M-05 | Day-30 escalation rate at most 0.5 per 100 above the approved baseline; severe harm pauses affected work | | M-06 | No more than 3% unexplained technician-productivity deterioration; Field Service and Finance validate; no scale while unresolved | | M-07 | At least 85% compliant use by day 30 and 95% in the later operational period | | M-08 | At most $300k total and six peak temporary FTE; forecast breach requires scope/funding action before excess occurs | | POL-01 | At least 90% of exception requests resolved within one operating shift; repair authority/capacity before enforcing or scaling | | Learning-edition balancing view | Report original-promise fulfillment, revisions, cancellations, declined work, and restoration hours; adverse movement triggers customer-value investigation even if M-01 passes | ### E-008.6: readiness observations | Area | Evidence currently available | Unresolved condition | |---|---|---| | Ownership/policy | Rights signed; tabletop completed | None within R1 scope | | Information | BO-02 linkage passed; one branch has delayed BO-05 updates | Twice-daily reconciliation with named Supply duty owner | | Exception capacity | Peak-volume simulation exposes rural approval backlog | Assign and test regional backup approver | | Training | 91% complete; one shift has not passed scenarios | No activation for an untrained shift | | Measures | Definitions agreed; parallel-run tests reconcile | Finish the January baseline before activation; preserve unresolved M-02 coding | | Recovery | Rollback and record-retention procedure tested | Maintain original promises and recovery ownership on rollback | The forum has not yet made DEC-003. Write a decision with explicit conditions and expiry; do not infer a waiver from the investment authorization. --- # Northstar: evidence available for the day-90 decision **Learning edition:** 1.2 · **Decision date:** 2026-05-06 · **Classification:** public, entirely fictional. **Boundary:** E-009/E-010 and the earlier dispositions below. DEC-005 has not yet been made. All source records, counts, names, and decisions in this exercise are fictional. The exact-count datasets and original-promise/restoration outcomes are newly authored v1.2 extensions; they were not recovered from v1.1. The additions intentionally make the next decision less comfortable than reading the aggregate dashboard alone. ## Decisions already made DEC-001 conditionally authorized the three-branch A1/R1 test within $150–300k, six peak temporary FTE, and staged commitment. DEC-002 deferred enterprise procurement. DEC-003, recorded by Casey Ortiz (ORG-15) on January 30, authorized a staggered February 2 start only after the remaining shift passed training and the January baseline was reconciled. It accepted provisional BO-05 reconciliation and a regional backup approver until the day-30 review. These conditions conveyed no R2 or procurement authority. The readiness addendum dated February 1 records training completion and baseline reconciliation. ORG-08 owns BO-05; its R1 source remains provisional. OI-06 for enterprise source authority remains open. ## E-009 **Source:** day-30 operating/Finance extract and review, 2026-03-03. **Owners:** Priya Shah ORG-09; Morgan Ellis ORG-12; ORG-07 Field Service; Delivery Management. **Period:** February 2–March 3 inclusive, 30 days. | Locator | Observation | |---|---| | E-009.1 | 128 of 144 eligible promises met the latest accepted promise: 88.9%, reported as 89% | | E-009.2 | 121/144 had part/skill confirmation (M-04 84%); 112/144 followed complete policy or an approved exception (M-07 78%) | | E-009.3 | M-03 margin 30.8%; M-06 technician productivity 4.1% below comparable baseline | | E-009.4 | M-05 escalations 6.5 per 100, compared with approved pre-release 6.2: within the 0.5 tolerance | | E-009.5 | Repeat visits 12% under still-disputed coding; one-shift exceptions 76%; rural approval backlog persists | | E-009.6 | $118k spent; forecast $340k total; peak capacity 5.8 FTE; forecast exceeds the authorized cap | | E-009.7 | Source lag creates reconciliation work. No comparison yet establishes that the proposed enterprise platform is the cheapest effective remedy. | ### Known day-30 decision: DEC-004 After CFO validation of margin/cost, Field Service validation of productivity, and Delivery validation of the forecast, Casey Ortiz used the one permitted remediation interval to continue R1 until the day-90 formal review. The decision prohibited scope expansion, imposed the M-06 no-scale response, and closed a low-volume work type to new pilot admissions from March 4 to avoid forecast overspend. It required weekly margin/workload review, correction of BO-05 reconciliation, and a tested regional backup approver. Severe customer harm could pause a branch; extension of the margin exception or any cap increase required the Investment Council. Completed observations from the removed work type were retained. Removing future scope was not permission to erase past failures. The scope change affects comparison and must be shown to the next forum. ## E-010 **Source:** day-90 extract, branch segmentation, audit, and Finance review, 2026-05-02. **Review meeting:** May 6. Owners as above, with customer-outcome review by ORG-06. **Detailed records:** see datasets/README.md and the CSV files in this folder. ### E-010.1: operational headline and reporting periods There are 486 cumulative eligible promises: 176 metropolitan, 166 mixed-fleet, 144 rural. Of these, 167, 156, and 128 respectively meet the latest accepted promise. Total 451/486 = 92.8%, reported as 93%; the branch rates round to 95%, 94%, and 89%. Each branch passes 100 observations and the total passes 450. These counts meet a volume rule, not a representativeness test. Later-period M-04 is 315/342 = 92.1% and M-07 is 328/342 = 95.9%, reported as 92% and 96%. Their period is days 31–90, not the full cumulative 90 days. Early M-07 noncompliance cannot disappear from a cumulative denominator. M-04 records part/skill confirmation only. M-07 records all required policy steps or a complete approved exception. A promise can have confirmation but incomplete documentation; a fully approved exception can be compliant without normal confirmation. These measures are not nested sets. ### E-010.2: cost and guardrails Finance reports cumulative gross service margin of 31.2%. Technician productivity is 2.0% below the comparable baseline, within its 3% guardrail. Total change cost is $287k and peak capacity is 5.8 FTE, within the authorized band. Cost includes $12k diagnostic, $58k preparation, and $217k release/measurement/change activity; ongoing manual-control cost requires a separate operating estimate. Escalations are 5.6 per 100. Repeat visits are 11%, still above the 8% strategic aspiration and still subject to coding reconciliation. One-shift exception completion is 88%, below the 90% criterion. Rural adherence remains 89%. These are unresolved limitations, not noise to average away. ### E-010.3: scope and stable-cohort comparison The first 30 days contain 114 retained-scope promises with 106 latest-promise successes and 30 subsequently closed-scope promises with 22 successes. Days 31–90 contain 342 retained-scope promises with 323 successes. Thus the retained-scope latest-promise rate moves from 93.0% to 94.4%, a 1.5 percentage-point change. The broader aggregate moves from 88.9% early to 94.4% later, partly because the poorer-performing work type no longer enters. All 30 earlier closed-scope records remain in the 486 cumulative total. Do not attribute the whole aggregate movement to policy adoption. Time, case mix, selection, changes in demand, and the intervention may all contribute. ### E-010.4: added customer-value evidence The v1.2 customer-outcome extract reports original-promise fulfillment of 120/144 early and 268/342 later. Within retained scope it falls from 100/114 (87.7%) to 268/342 (78.4%). Mean restoration time in that retained cohort rises from 40 to 48 hours. These are descriptive comparisons, without case-mix adjustment or a control group. They do not prove that the new policy caused harm. They do establish that latest-promise adherence alone is insufficient evidence of improved customer value. Examine promise revisions, demand refused or diverted, operating mix, and capacity before declaring success. The separate cancellation/decline denominators in the dataset keep changes in the admitted population visible; they must not be folded into fulfilled-promise percentages without a defined question. ### E-010.5: request to the Council The sponsor proposes designing R2 because the operational feasibility gate is met. Customer Operations asks whether later accepted dates conceal worse service to the original need. Finance asks for the recurring manual-control cost and a comparison of A4 targeted integration, further operating correction, and platform alternatives. No one has a controlled attribution estimate. Avery must recommend the next decision. The Council may authorize design/readiness, restrict or stop portions of the practice, require investigation, or decline expansion. No existing decision authorizes twelve-branch activation or procurement. --- # Northstar: instructor notes and a defensible reference path **Learning edition v1.2 · Entirely fictional · Contains answers and later knowledge.** Keep this directory out of a learner's initial evidence upload. Read the actual A/B/C decision briefs for the reference dispositions. ## What the exercise is teaching A business architect should connect the decision to value, capability, information, ownership, cost, and evidence without pretending that a complete diagram resolves an uncertain business problem. Good work can recommend a smaller intervention, further diagnosis, or stopping. The preferred answer is evidence discipline, not a particular tool or a universal preference for pilots. The reference path funds a cheap diagnostic before releasing the A1 envelope, conditionally starts a three-branch practice, and declines expansion despite an attractive aggregate headline. A0 or A4 can be defensible earlier choices if the learner makes their evidence requirements and tradeoffs explicit. ## Corrections worth seeing | Tempting claim | Corrected work | Fictional reviewer and date | |---|---|---| | Vendor demonstration establishes business value | E-004 establishes functionality under demonstration conditions; enterprise fit and customer value remain unknown | Avery Chen, 2026-01-09; rejected | | 38% is the pilot's approved operational baseline | E-006 is 68/180 over two weeks across six candidate branches and broad work types; reconcile a separate selected-branch baseline | Morgan Ellis, 2026-01-09; modified | | BO-05's owner/source is resolved enterprise-wide | E-008 confirms ORG-08 ownership and provisional R1 use only; preserve OI-06 | Avery Chen with Supply/Information Governance, 2026-01-30; modified | | 96% adoption is cumulative across all 486 promises | It is 328/342 in days 31–90; early 112/144 remains in history | Morgan Ellis, 2026-05-06; rejected | | Adherence rose, so the policy caused customer value | Scope changed; retained-scope improvement is smaller; original commitments and restoration time deteriorate | Avery Chen with Customer Operations, 2026-05-06; rejected | | Passing 450 records proves repeatability | Purposeful three-branch volume establishes data sufficiency for this exercise, not enterprise representation | Jordan Reed, 2026-05-06; rejected | These are authored teaching corrections, not transcripts of an actual AI run. Any published model comparison must identify its own inputs, outputs, run conditions, and reviewer results. ## Decision-changing evidence At A, use A0 if reconciliation makes the supposed performance gap disappear. Prefer A4 if source semantics are reliable and avoidable checking is the material constraint. Redesign A1 if safe capacity is unavailable or its possible results cannot distinguish actions. Greater harm from delay can justify a different sequence; the speculative cost bracket does not settle it. At B, delay activation for missing training or an unusable exception route. A named control with no operating capacity is not readiness. Accepting a source for R1 is a scoped institutional decision, not a global fact. At C, examine the deterioration before celebrating the better aggregate. Persistent customer harm supports reducing or stopping the practice. A case-mix explanation could narrow the concern, but must be demonstrated. Improved compliance is valuable only in relation to a sound operating design and the customer outcome. ## Traceability and continuity Every claim should cite a specific E-* locator and preserve its period/scope. Use atomic typed relationships such as C-110 uses BO-02, C-140 manages BO-05, and C-110 enables ST-02. A recommendation about procurement is an analysis/decision record, not a capability relationship. Record the reviewer, date, disposition, rationale, and affected claims. When E-008 changes source status, append the correction; do not erase Episode A uncertainty. When E-010 challenges the value story, retain both the old hypothesis and the new limitation. Export and reopen the workspace to demonstrate that continuity. ## Assessing an attempt Look for a direct recommendation; one seriously considered rival; period/denominator discipline; original and latest promises; source authority and meaningful uncertainty; a bounded learning budget; explicit human decision rights; changed or rejected claims; and a usable next decision. A fluent exhaustive model can fail these criteria. Do not score agreement with A1 as correctness. Do not infer real-world productivity from this teaching case. Measure actual review effort, unsupported claims, conflicts found, corrections, and successful reuse when evaluating SCALE. --- # Decision brief A: buy information before buying a platform **Northstar learning edition v1.2 — authored fictional reference decision.** **Date:** 2026-01-09 · **Prepared:** Avery Chen (ORG-14) · **Decision owner:** Jordan Reed, Investment Council (ORG-13). **Evidence cutoff:** E-001–E-007. No later readiness or performance is used. ## Recommendation Authorize the first $15k diagnostic inside a conditional A1/R1 envelope of $150–300k. Release no more than $75k cumulatively for preparation until a readiness decision, and no more than $300k overall. Only the first $15k is released now. Preparation and operational spending require subsequent named human release decisions; the envelope is not an automatic authorization to spend. Record DEC-001 with those conditions. Record DEC-002 deferring enterprise procurement. Keep A4 targeted integration in contention. This is a bounded learning commitment, not an ROI claim. Present evidence establishes unreliable definitions and plausible operating constraints. It does not show whether policy, source quality, scheduling capacity, or automation is the dominant limiting condition. ## Why this is worth investigating E-001/E-003 connect unreliable commitments to the customer state in VS-01/ST-02. C-110 depends on scheduling and part-status signals from C-130/C-140, with BO-02/BO-05/BO-06 meaning governed through C-180 and measurement through C-170. This is a proposed decision-relevant trace, not proof of causation. A0 can repair the baseline but does not test the operating practice. A2 exposes more branches before the design is understood. E-004 establishes only demonstrated functionality for A3. A4 may be cheaper and should win if reliable source states and an avoidable manual bottleneck are the principal constraints. The $27–54k 90-day exposure scenario in E-005 is unvalidated. It supports urgency for a cheap diagnostic, not a fabricated return on $300k. Full release cost includes internal and branch labor; peak FTE does not replace total effort. | Uncertainty | Cheapest useful check | What changes the decision | |---|---|---| | Reservation meaning and freshness | Reconcile actual events and status transitions | If reliable and dominant, compare A4 directly; if unusable, fix meaning/control before automation | | Manual burden | Time real confirmation/exception work | If an operating test cannot run safely within capacity, redesign or stop | | Promise performance | Reconcile original/revised/cancelled cohorts | If the apparent gap is measurement only, prefer A0 and do not fund a broad test | | Local authority/capacity | Test rural scenarios and named exception rights | If geography/skills dominate, target capacity rather than promise software | | Useful learning | Predefine how test results change the next action | If outcomes cannot discriminate options, do not release the full envelope | ## Conditions, authority, and confidence Priya Shah owns policy and operating outcomes; Supply and Information Governance must resolve BO-05 meaning/source status; Morgan Ellis approves definitions and cost. Before activation: agreed denominators, baseline, original-promise/restoration balancing measures, selected branches, safe capacity, readiness, and stop/rollback routes. Confidence: **Medium** in funding a short diagnostic; **Low** in any present claim about platform value or enterprise repeatability. Stronger source reconciliation could favor A0/A4 or a smaller test. Unacceptable delay harm or infeasible manual controls could change the sequence. **Recorded fictional disposition:** Jordan Reed accepted DEC-001/DEC-002 on January 9 with Morgan Ellis's cost conditions and Priya Shah's operating sponsorship. This reference path does not imply that every defensible learner must recommend A1. --- # Decision brief B: readiness is conditional, not inherited **Northstar learning edition v1.2 — authored fictional reference decision.** **Date:** 2026-01-30 · **Prepared:** Avery Chen (ORG-14) · **Decision owner:** Casey Ortiz, R1 Readiness Forum (ORG-15). **Evidence cutoff:** E-008. No release result is available. ## Recommendation and DEC-003 Authorize a staggered February 2 R1 start only after the remaining shift passes training and the January baseline reconciliation is complete. Accept the provisional BO-05 reconciliation control and regional backup approver through the day-30 review only. Record owners, daily operation, evidence of use, and March 3 expiry. Do not activate an untrained shift. If the baseline or backup route is unavailable, delay the affected activation. The $70k cumulative preparation cost remains below $75k; further release spending is subject to the authorized total cap and measured capacity. ## Basis and changed knowledge E-008 establishes an operating design with conditional readiness. It does not establish adoption, customer value, or reliability improvement. The diagnostic found ambiguous reservation states and a rural exception bottleneck; A4 remains an option for measured residual gaps. Replace the earlier unresolved-owner claim with: ORG-08 owns BO-05; the inventory record is a provisional R1 source requiring twice-daily reconciliation. Preserve the original claim and its disposition in history. Reject the broader statement that the source is now enterprise-authoritative. OI-06 remains open before R2. The architect's sufficient answer is a bounded readiness recommendation. That does not waive the operational prerequisites. ## Conditions and breach actions | Condition | Owner | Review/expiry | Action if unmet | |---|---|---|---| | Training and baseline reconciliation | Branch managers; Operations/Finance | Before activation | Delay affected start | | BO-05 reconciliation | ORG-08 with ORG-10 | March 3 | Close, adapt, or explicitly renew; pause normal confirmation if source cannot be verified | | Regional backup approver | ORG-05 | March 3 | Repair exception capacity; do not call unusable policy employee resistance | | Cost/capacity and customer guardrails | Finance, Delivery, relevant operating owners | Weekly plus formal reviews | Scope/funding action before cap breach; pause affected work for severe harm | ORG-15's authority is confined to R1 and the explicit one-interval margin remediation rule. It cannot expand the budget, activate R2, waive all guards, or procure the platform. Confidence: **Medium** in conditional readiness, limited by provisional source quality and unobserved adoption. **Recorded fictional disposition:** Casey Ortiz accepted DEC-003 on January 30. The February 1 addendum confirms training and baseline completion; it is later readiness evidence, not information available in the original January 30 recommendation. --- # Decision brief C: operational feasibility has not established customer value **Northstar learning edition v1.2 — authored fictional reference decision.** **Date:** 2026-05-06 · **Prepared:** Avery Chen (ORG-14) · **Decision owner:** Jordan Reed, Investment Council (ORG-13). **Evidence cutoff:** E-010, including the newly authored v1.2 customer-outcome extension. ## Recommendation and DEC-005 Conclude that the bounded R1 practice can operate under material conditions. Authorize limited R2 design/readiness investigation only; prohibit twelve-branch activation and retain DEC-002's procurement deferral. Require a customer-value investigation before continuation is described as success or activation is considered. Pause or adapt affected work immediately if Customer Operations validates severe harm. This narrows the optimistic interpretation of the dashboard. Latest-promise adherence passes the interim gate, but original promises and restoration times worsen in the added evidence. R1 does not establish improved customer value, causation, repeatability, or the right technology. ## What the results establish 451 of 486 cumulative promises meet the latest accepted promise (92.8%, rounded 93%). All branches meet the volume rule. The rural branch remains at 128/144 (88.9%). Margin is 31.2%; productivity is 2.0% below baseline; final cost $287k and peak 5.8 FTE stay within the band. Exception turnaround is 88%, below 90%; repeat-visit coding and its 11% result remain unresolved. The later M-04 92% and M-07 96% describe days 31–90, not cumulative performance. At day 30 their corresponding rates were 84% and 78%. Preserve those early failures. After day-30 scope closure, the retained-scope latest-promise rate rises from 106/114 (93.0%) to 323/342 (94.4%). This is much less than the aggregate early-to-late movement. The closed work type's 30 earlier records remain in the cumulative denominator. More seriously, retained-scope original-promise fulfillment falls from 100/114 (87.7%) to 268/342 (78.4%) while mean restoration time rises from 40 to 48 hours. Case mix and other explanations remain possible. These signals justify investigation and restraint, not a causal accusation. ## Conditions before activation or investment Customer Operations must reconcile original/revised commitments, declined/cancelled demand, work mix, restoration time, and severe-harm cases. Field Service and Regional Operations must resolve rural capacity and exception response. Supply/Information Governance must close OI-06. Finance must cost recurring manual work and confirm a like-for-like baseline. Delivery must define the next stage's capacity and stop conditions. Compare A4 targeted integration, operating changes, and platform options against the verified residual gap. If deterioration persists after comparable-cohort review, reduce or stop the affected practice. If a narrow feed addresses the demonstrated constraint safely, prefer the smaller investment. If the learning cannot distinguish options, redesign it. Confidence: **Medium** in bounded operational feasibility; **Insufficient** to claim improved customer value or enterprise-scale benefit. **Recorded fictional disposition:** Jordan Reed accepted DEC-005 on May 6 with Morgan Ellis's financial conditions and Customer Operations' added customer-value gate. The original v1.1 authorized design/readiness only; this v1.2 extension strengthens that boundary using newly authored evidence. It does not rewrite historical results from a real pilot.