# EM-STR-01 — Strategy, Business Model and Value Streams ## Verdict Four candidates require **independent model identity** (identifier unassigned): **Strategy**, **BusinessModel**, **ValueStream**, **StrategicScenario**. Two are **contained records / profiles, not roots**: **StrategicTheme** (inside Strategy), **ValueProposition** (inside BusinessModel). Five adjacent models are **reused unchanged, by reference**: WM-KNW-011, WM-KNW-010, WM-ACT-024, WM-REC-010, WM-ACT-030. Capability and value-stream→process realization stay **blocked** (WM-ACT-001, WM-ACT-003 are legacy-only, `migration-boundary-review`). Value realization is **declared-unallocated** to the EM-STR-02 Outcome/Benefit candidate. The project-list case is rejected. `boundary_decision` remains pending pending registry allocation. ## Evidence Only the frozen dossier is used. WM-KNW-011 owns the desired-outcome record, measure binding by reference, horizon, accountability, restatement and supersession, and explicitly excludes planning of means. WM-ACT-030 owns change intent, options, appraisal, mandate and formalization, and explicitly refuses to be a synonym for Strategy. WM-KNW-010 owns question, alternatives, criteria, evaluation rounds, selection and rationale; WM-ACT-024 the approval occurrence; WM-REC-010 the authentic fixed expression. Nothing in the dossier masters market choice, value mechanism, recipient-triggered value flow or scenario space — the gap is real, not a naming artifact. The `candidate_properties_from_v1` fields (STR-01, STR-06) are marked `candidate-not-normative` and are treated as evidence of intent only. ## Identity/mastership Strategy identity survives restatement, theme reshuffling and every initiative it spawns; it is answerable to one decision authority. BusinessModel identity survives strategy versions and outlives individual offers; one group runs several concurrently. ValueStream identity survives process redesign and reorganization; it is named by recipient need, not by organizational unit. StrategicScenario identity is independent because a scenario is cited by many strategies and must not inherit any strategy's authority. StrategicTheme and ValueProposition have revisions but no authority, no mandate and no lifecycle of their own — they are addressable children, mastered by their root. Suggested masters: strategic decisions register (Strategy), business-model register (BusinessModel), value-stream register (ValueStream), planning/analysis register (StrategicScenario). ## Strategy and themes Strategy records a **choice set**: markets and segments selected, those explicitly excluded, the basis of advantage asserted, the assumptions the choice rests on, the horizon, and the review triggers. Exclusions are first-class; a strategy with no rejected alternative is not a strategy. **Mission and policy are not strategic choice**: mission is standing purpose with no horizon and no rejected alternative; policy is a standing constraint on permissible choices. Both are referenced (policy referent unallocated in this dossier), never restated. **Strategy is not plan, initiative or portfolio**: sequencing, resourcing and delivery are WM-ACT-030 and portfolio referents. StrategicTheme groups choices under a stated intent and carries the alignment anchor that objectives and initiatives cite; its horizon and authority are inherited. ## Business model and value proposition BusinessModel records the **value mechanism**: recipient segments, channels, value proposition bindings, revenue and cost logic, key partners and resources by reference. It is **not the organization**: legal entity, unit and role are party referents; one entity may run many business models and one business model may span entities. ValueProposition is the asserted benefit-to-recipient claim (job, pain, gain, alternative displaced) for one segment–channel pair. It is **not the offer**: price, terms, SKU and contract are offer/product referents outside this contour. Where a group reuses one proposition across business models, that is a **citation of a pinned VP revision**, never a second master. ## Value stream versus process A **stage** is a change in the recipient's value state — need recognized, request qualified, value accessible, value realized — triggered by the recipient and validated from the recipient's side. A **process** is the repeatable internal realization of one or more stages, with steps, gateways, roles and states. The test: if renaming or automating the work leaves the recipient's state sequence unchanged, it is process, not stage. ValueStream owns trigger, recipient, stage sequence, stage entry/exit criteria and the value outcome referent. Stage→process and stage→capability bindings are **blocked**: WM-ACT-003 and WM-ACT-001 are `described-previous-version` with no current boundary, so the edges are declared and unenforceable. ## Scenario and hypothesis StrategicScenario holds drivers, varied assumptions, projected states and method, each attributable and uncertainty-bearing. A scenario is a **hypothesis space**, never a source of record. Assumptions carry validity windows and defeat conditions; causal hypotheses (choice → mechanism → outcome → benefit) carry stated attribution limits and competing explanations. Promotion of a hypothesis to confirmed requires an external assessment with pinned criteria and decision rule — the assessment referent is not in this dossier and is therefore blocked. **Forecast is not outcome**: a projected figure remains a forecast until qualified observations in the realization window support it, and the observing referent is the unallocated EM-STR-02 aggregate. **Authoritative actuals and scenarios are separated**: no scenario output may become an observation, a target baseline, or a benefit realization input. ## Objectives/capabilities/initiatives/decisions Objectives, key results and targets are **WM-KNW-011 role-coded records** citing a Strategy or StrategicTheme identity; measures bind by reference, and WM-KNW-011's own measure/metric referent is unassigned. Initiatives are **WM-ACT-030**, linked by a contribution assertion with a stated basis — membership, tag or budget line is not alignment. Capability requirements are **blocked**. Strategy approval cites **WM-KNW-010** (alternatives, exclusion reasons, criteria, rationale, dissent), **WM-ACT-024** (approval occurrence, authority, quorum) and **WM-REC-010** (fixed expression, issuance, finality). Strategy must not restate any of these; it carries references and the resulting authority basis only. ## Time/version/review Four axes stay separate: **horizon** (the interval the choice reaches), **effective window** (when the version governs), **event vs. knowledge time**, and **review cadence**. A released Strategy version is immutable; substantive change produces a successor with a restatement note, retained prior choices and a supersession link. Review triggers are declared, not inferred: assumption defeat, scenario divergence past a stated threshold, measure breach, **segment or channel change**, authority change, horizon expiry. A BusinessModel revision is triggered by change to a named mechanism element; a ValueStream revision by change to trigger, recipient or stage sequence. ## Acceptance scenario **Startup.** Strategy: serve segment X through direct channel, excluding marketplace; assumptions: acquisition cost and willingness to pay. One BusinessModel, one VP, one value stream (need → activated → first value). Channel moves to marketplace: because *channel* is named in the strategy's choice set, this is a Strategy restatement, a new BusinessModel revision, VP revalidation (jobs unchanged, access and effort changed) and a new stage sequence. The acquisition-cost assumption is marked defeated; prior forecasts stay as forecasts. **Multi-industry group.** Group Strategy chooses which industries to be in and the capital-allocation logic; themes span business models. One BusinessModel per industry–segment–channel. Exiting a segment retires that BusinessModel to a terminal state (never deletes it) and restates the group Strategy only if that market was a named choice; the shared VP citation from the surviving business model remains resolvable. Value streams follow business models, not legal entities. **Negative case.** A project list labelled strategy is **rejected**: it is a portfolio projection. It carries no rejected alternative, no recipient of value, no assumption, no causal hypothesis, no horizon and no review trigger, and its items are WM-ACT-030 records. ## Invariants 1. A strategy states at least one explicitly rejected alternative. 2. Strategy has a horizon and a named decision authority, cited to WM-ACT-024/WM-REC-010. 3. Mission and policy constrain but never constitute strategic choice. 4. An initiative never substitutes for a strategy, and no project list creates one. 5. Every value stream starts from a recipient need and its trigger. 6. Stage is a recipient value-state change; process realization is referenced, not owned. 7. Business model is distinct from organization; neither masters the other. 8. Value proposition is distinct from offer; price and terms are never held here. 9. Assumptions and causal hypotheses are labelled hypotheses with defeat conditions until externally assessed. 10. Forecasts never overwrite outcomes; realization requires qualified observations in the window. 11. No scenario output feeds authoritative actuals, baselines or benefit realization. 12. Released strategy versions are immutable; change proceeds by successor and supersession. 13. Contribution and alignment links require a stated basis. 14. Blocked and unallocated referents are never silently promoted. ## Minimal model set New, identifier unassigned: **Strategy** (aggregate root, containing StrategicTheme), **BusinessModel** (aggregate root, containing ValueProposition), **ValueStream** (aggregate root, containing Stage), **StrategicScenario** (aggregate root, containing assumption and projection sets). Profiles/contained only: StrategicTheme, ValueProposition, Stage. Reuse by reference: WM-KNW-011, WM-ACT-030, WM-KNW-010, WM-ACT-024, WM-REC-010. Blocked: Capability (WM-ACT-001), Process/Workflow (WM-ACT-003), assessment referent. Declared-unallocated: Outcome/Benefit Realization (EM-STR-02), metric definition, policy/mission, offer/product, party, portfolio. ## Holds No identifier is allocated; `boundary_decision` stays pending and `target_model_ids` empty. Every reused base is `publishableCanonical: false`; WM-KNW-011, WM-KNW-010 and WM-ACT-024 are Claude-only under an owner waiver, WM-ACT-030 is Codex-only with Claude and Grok waived. Relationship contracts for the asserted references are absent or empty, so all boundary exclusions here are declared and unenforceable. Two required realization referents have no current specification and two more have no registry allocation. No semantic crosswalk, mastership confirmation, immutable refs or fixture checks have been performed. This review claims no canonical completeness, no installability and no publication readiness.