The minimum set is two unassigned roots: **Value Stream** (the definition) and **Value Stream Realization** (the enterprise binding). No identifier is allocated. External and internal are boundary roles of one definition, not two roots. Stages, exchange intent, and the terminal value-state are contained. Maps, portfolios, journeys, process runs, and stream “instances” do not master facts.

Archetype names below are classification labels only. They are not registry identifiers.

## A. Coverage frame

Completeness is argued on five finite dimensions, not on industries or departments.

**D1. Boundary role.** A role of one definition against one governing boundary: outbound-external (primary beneficiary outside), inbound-crossing (beneficiary inside, value or permission crosses in), or internal (beneficiary inside; the stream enables, governs, changes, or sustains). The same definition may be external to a subsidiary and internal to the group. Role change does not mint a second root.

**D2. Value-cycle phase.** Every admitted stream must show a beneficiary value-state progression in at least one of: acquisition, creation, delivery, realization, capture, renewal/retirement, change, enablement, governance, assurance, recovery. A phase is not itself a stream. A phase is covered if it is the terminal phase of some archetype or a real stage of one.

**D3. Beneficiary class.** One primary class per stream: external user, right-holder, duty-subject, funded performer, partner, network participant, relying party, or harmed external party; the enterprise as recipient of supply, return, resources, or authorization; an internal operation; a worker; a governing body; a decision-maker; a risk owner; or the enterprise as duty-bearer. Two beneficiary classes means two streams and a hand-off.

**D4. Terminal-outcome class.** The class of beneficiary condition that ends the stream, stated separately from outputs, delivery, payment, and accounting recognition.

**D5. Exclusions.** Department lists, generic value-chain templates, application workflows, project plans, touchpoint-only journeys, and product or asset lifecycles with no beneficiary value progression. Also excluded: seller pipeline states, system status, report publication, course delivery, go-live, and ticket closure, unless a beneficiary state sequence remains after those outputs are removed.

**Admission rule.** An archetype is a class-level stream: named beneficiary class, recognizable trigger, ordered beneficiary states, terminal outcome distinct from outputs, identity stable across process, system, and organization redesign. A variant may change channel, sector, offering form, jurisdiction, or price. It may not change beneficiary class, trigger class, state-sequence meaning, or terminal-outcome class. If one of those four changes, it is another definition or a new semantic version, not a variant.

**Coverage claim.** Any admissible stream lands on exactly one archetype by beneficiary class, trigger class, and terminal-outcome class. Every phase in D2 is terminal for at least one archetype below, or a non-terminal stage of one. A new sector produces variants. A new archetype is justified only by a new beneficiary class or terminal-outcome class, and that extension must be explicit.

Renewal is not an archetype. It is a new cycle of the same definition when the trigger is “continuation required.” Retirement is either Active holding to closed holding or the closure stage of the worker, asset, or obligation streams.

## B. External value streams

Outbound unless marked inbound. “Masters” are realizers or evidence, not the stream. There is no value-stream master in the frozen inventory of 403.

| Archetype | Beneficiary / counterparty | Trigger | Terminal value outcome | Typical variants | Current masters | Gaps |
|---|---|---|---|---|---|---|
| Demand to realized use | External user; payer may differ | A need the enterprise undertakes to satisfy | The beneficiary’s job or need is met to the promised condition | Goods, services, subscriptions where use is in scope, public paid service | WM-ORG-014, WM-ECO-021, WM-ECO-020, WM-ECO-022, WM-ECO-006, WM-ECO-024, WM-ACT-004, WM-OBJ-002; contours EM-COM-02, EM-COM-03, EM-PRD-01, EM-PRD-02 | Stream root unassigned. EM-COM-01 pending. Delivery or payment is not this outcome. EM-STR-02 outcome root deferred |
| Demand to granted right | External right-holder | Need for a usable right, not for governed use | A usable right is held; use sits outside this stream | Licence, access, entitlement, wholesale right | WM-ECO-022, WM-KNW-003, EM-TEC-02 licence candidate, EM-COM-03 entitlement hypothesis; WM-POL-014 is not this right | Use EM-COM-03 only as a parked hypothesis. Do not treat a contract record as the right or the stream |
| Duty to discharged outcome | Duty-subject who need not pay | A duty-bearing need or eligibility | The duty outcome holds, distinct from service performed | Mandated service, protection, benefit-in-kind, professional duty | WM-POL-012, WM-POL-018, WM-ACT-004; sector acts such as WM-ACT-014 only as realizers | No public-sector stream root. Terminal condition stays contained until an Outcome identity exists |
| Awarded purpose to evidenced application | Funded performer | An award whose purpose another party must apply | Purpose application is evidenced. Ultimate beneficiary outcome may be out of scope | Grant, subcontracted mission, sponsored delivery | WM-ECO-030, WM-ACT-034 | Payment issued is an output. End-beneficiary result is a hand-off, not automatic success |
| Complement to partner outcome | External partner | A complementarity the enterprise commits to | The partner’s complementary outcome is realized | Reseller, alliance, consortium, platform complementor | WM-ORG-015, WM-ORG-012, WM-ECO-006 | EM-COM-01 pending. One direction per stream; the return direction is another stream |
| Unmet input to accepted supply (inbound) | Enterprise as supply recipient; supplier is counterparty | An input need the enterprise cannot meet itself | Fit-for-purpose supply is accepted | Goods, services, data, energy, contingent capacity | WM-ECO-007, WM-ECO-019, WM-ORG-015, WM-FLW-004, WM-FLW-011, WM-OBJ-020; EM-OPS-02 | Procurement Request and Sourcing Event stay unassigned realizers. Procure-to-pay is not this stream |
| Earned claim to secured return (inbound capture) | Enterprise or its owners | A consideration claim has arisen | Return is secured, not merely invoiced, recognized, or booked | Customer payment, fee, member dues tied to an exchange | WM-ECO-008, WM-ECO-009, WM-ECO-010, WM-ECO-016; EM-FIN-03 profiles only | Capture is not customer outcome, not benefit, and not the journal entry |
| Resource gap to usable resources (inbound) | Enterprise mission capacity; funder is counterparty | A resource gap or a funder’s intent | Resources are usable for the stated purpose | Appropriation, donation, grant income, capital contribution | WM-ECO-030, WM-ECO-012, WM-ECO-005; EM-FIN-01 | Budget is not the stream. Distinct from earned return |
| Reliance need to justified reliance | External relying party | Someone must rely on a claim | Reliance is justified at a stated level | Audit opinion, certification, regulatory attestation | WM-ECO-035, WM-ACT-033, WM-REC-002; EM-RSK-02 procedure candidate | Engagement completion and report issue are outputs |
| Authorization gap to sufficient standing (inbound) | Enterprise as regulated actor; authority is counterparty | An intended activity lacks permission | Standing is sufficient to act | Licence to operate, permit, approval | WM-POL-004, WM-POL-001; EM-LEG-04 authorization candidate | The authorization object is not the stream. WM-POL-014 stays rejected for this |
| Degraded external value to restored or remedied state | External party who holds the degraded value | Harm, defect, or loss of an entitled state | Baseline restored or remedy accepted | Warranty, recall, service recovery, redress | WM-ECO-025, WM-ACT-021, WM-ACT-019, WM-ACT-042; EM-COM-04 profile | Case closure is not restoration. EM-TEC-05 incident identity is a realizer |
| Participation to realized network value | One side’s participant | Joining or contributing where others’ presence matters | Network benefit is realized, not merely product use | Marketplace side, exchange member, community contributor | WM-ORG-014, WM-ECO-001, WM-VRT-006 | No network-outcome master. If other participants do not define the terminal state, use Demand to realized use |
| Active holding to closed holding | External holder | Exit, expiry, or withdrawal | Obligations are discharged and exposure has ended | Contract end, account closure, entitlement revocation | WM-ECO-006, WM-XCT-029, WM-XCT-035, WM-ECO-025 | EM-COM-03 renewal is a version link, not a stream and not closure |
| Current arrangement to re-established successor value | External beneficiary of a successor | A successor offering or rule the beneficiary must move to | Entitled value is re-established on the successor | Migration, contract novation, mandated channel change | WM-ACT-030, WM-ACT-032, WM-ACT-005; EM-PRD-01 roadmap profile | Project close and cutover are outputs |

## C. Internal value streams

| Archetype | Beneficiary / counterparty | Trigger | Terminal value outcome | Typical variants | Current masters | Gaps |
|---|---|---|---|---|---|---|
| Unmet contribution need to reliable contribution | Internal operation that needs people | A contribution need | Contribution is reliable in role | Employment, internal mobility, contingent help once inside | WM-ORG-008, WM-ORG-005, WM-ACT-039, WM-ACT-040; EM-PEO-02, EM-PEO-04 candidates | Requisition and candidacy are not the stream. Hire-to-retire is not this archetype |
| Worker expectation to honored relationship or clean closure | The worker | A work relationship with governed expectations | Expectations are met, or separation obligations are honored | Employment, membership work, appointment | WM-ORG-005, WM-ORG-017, WM-ECO-031; EM-PEO-05, EM-PEO-08, EM-PEO-09 candidates | EM-PEO-06 is pending, so performance evidence is unknown, not success |
| Operating need to fit asset availability | Internal consuming operation | Need for a fit asset | The operation can rely on availability and fitness | Equipment, premises, software runtime treated as an asset | WM-ACT-013, WM-ACT-007, WM-OBJ-022; EM-OPS-03 candidates | WM-OBJ-022 is a lifecycle record, not a stream |
| Offering gap to releasable offering | Enterprise as offeror | A promised offer cannot yet be released | The offering is releasable to a beneficiary | Product, service, policy, data product readiness | EM-PRD-01, EM-PRD-02, WM-ACT-010, WM-DAT-008, WM-SFT-008 | Release, build, or roadmap item is an output. Customer receipt is an external stream |
| Direction need to binding direction | Accountable internal body | A direction is required | Actors are bound by an authorized direction | Policy choice, investment choice, priority call | WM-ORG-018, WM-ORG-007, WM-ACT-024, WM-KNW-010, WM-REC-010; EM-STR-01 Strategy candidate | Strategy is a choice set, not this stream. A meeting or a signed paper is an output |
| Current operating state to intended state in force | Internal operation | An authorized change of operating state | The intended state is in force | Operating-model change, new method of work | WM-ACT-005, WM-ACT-029, WM-ACT-030, WM-ACT-008; EM-WRK-02, EM-WRK-03 | Project, program, and benefit assertions do not own this terminal state |
| Uncertainty to accepted assurance | Governing body | Need to know whether a claim or control holds | Assurance is accepted, or an exception is bound | Internal audit, control attestation, safety case | WM-ECO-035, WM-ACT-033, WM-XCT-027; EM-RSK-01 Control candidate, EM-RSK-02 | Procedure Definition is the method. External reliance is the external assurance archetype |
| Disrupted operation to restored baseline | Internal operation | Disruption of an operating baseline | An accepted baseline is restored | Continuity, operational recovery, cyber recovery | WM-ACT-043, WM-ACT-019, WM-ACT-020; EM-RSK-04, EM-TEC-05 | The continuity plan and the ticket are not the stream |
| Decision question to accepted understanding | Named internal decision-maker | A decision lacks adequate understanding | Understanding is accepted for that decision | Analysis, experiment, investigation | WM-ACT-036, WM-KNW-007, WM-DAT-008, WM-REC-002; EM-DAT-07 | Most “data-to-insight” work fails here because it ends at a report |
| Ability gap to reliable ability | Operation that must be able | An ability the intent already assumes is missing | The ability is reliable at the required level | Skill, system capability, supplier-backed ability | WM-ACT-001 as split by EM-STR-03, WM-PER-009, EM-PEO-05, WM-SFT-002 | Capability and learning roots stay in their own contours. Course delivery is not ability |
| Obligation exposure to controlled obligation | Enterprise as duty-bearer | An obligation applies | The obligation is under demonstrable control | Privacy, tax duty, safety duty, policy duty | WM-XCT-029, WM-KNW-012, WM-POL-011, WM-ACT-051; EM-LEG-03, EM-LEG-06 | Control candidate is unassigned. Filing and policy publication are outputs |
| Contention to secured capacity share | Consuming internal operation | Competing claims on finite capacity | That operation has a known, reliable share | People, machines, funds, slots | EM-WRK-05 demand and pool candidates, WM-ACT-008 | Those work roots are not required to define the stream. A plan file is not the share |
| Risk exposure to authorized risk position | Internal risk owner | A risk or opportunity requires a position | Position is accepted, treated, or closed at an authorized level | Enterprise risk, opportunity, treated exposure | WM-KNW-015, WM-XCT-027; EM-RSK-01 | The register row and the heatmap are not the stream |

## D. Composition rules

**Nesting.** A definition contains ordered stages and nothing that has a different beneficiary. A stage is a value-state transition: entry condition, exit condition, same beneficiary. If a supposed stage has its own beneficiary, it is another stream.

**Decomposition.** Further breakdown of work inside a stage is process, procedure, or activity (WM-ACT-003, WM-ACT-009, EM-OPS-01). It must not be stored as child streams. A shared library of stage names fails transfer: the same label under different beneficiaries is not the same value state. Shared names, if needed, are classifications over WM-KNW-018, not a root.

**Variants.** Variants specialize channel, sector, offering, place, or commercial form. They inherit beneficiary, trigger, state meaning, and terminal class. Semantic version of a definition changes only when beneficiary class, trigger class, state sequence or state meaning, or terminal outcome changes. Label-only edits are history (WM-XCT-022 pattern), not a new semantic version. Process, system, organization, metric, and channel changes do not version the definition.

**Cross-boundary hand-off.** A hand-off links the exit state of one stream to the trigger of another. It is not containment. Accepted supply may enable an offering stream; a releasable offering may enable Demand to realized use; a claim arising on that stream may trigger Earned claim to secured return before or after use is realized. Order is not a universal sequence. External versus internal is reclassified per boundary (WM-ORG-001, EM-ORG-01, EM-LND-02). It is not copied into a second definition.

**Many-to-many realization.** One stage may be realized by many processes, capabilities, units, or systems. One process may realize stages of many streams. Those links are not inside the definition. If they were, a redesign would create a new stream version and contradict the identity already stated for Value Stream: the progression survives process redesign, automation, and organization change. Missing realizers are gaps. They are not evidence that the stream is absent or that realization failed.

**Not a process.** A process masters how work is executed. A stream masters how a beneficiary’s value state is intended to change. Execution records do not create stream identity.

**Not a journey.** A journey is a touchpoint or trip sequence (WM-FLW-009; EM-TEC-06 deferred and non-normative). Touchpoints become stages only when they change beneficiary value state.

**Not a lifecycle.** Product, asset, employment, and contract lifecycles master the subject’s states. They are streams only where a named beneficiary’s value progresses. Otherwise they remain WM-OBJ-022, WM-ORG-005, WM-ECO-006, and peers.

**Not a capability.** A capability is an ability identified independently of organization and process (EM-STR-03 pair of outcome class and acted-upon object). A stream may be enabled by capabilities. It is not a capability and does not own Capability Realization.

**Not a value chain.** A generic chain is a fixed activity classification with no beneficiary, trigger, or terminal outcome. It may inspire variants. It is not a definition.

**Not an instance.** One customer’s passage, one hire, or one incident is a correlation across existing occurrence masters. Independent instance identity is not demonstrated. Correlation keys are views, as with the rejected independent identities of Backlog and Iteration.

## E. Meta-model decision register

| Item | Decision | Ownership and dependency boundary |
|---|---|---|
| Value Stream | **NEW**, confirms the EM-STR-01 candidate | Strategy/value contour owns the definition. May cite party role WM-XCT-023, organization WM-ORG-001, classification, goals WM-KNW-011, version history. Must not depend on process, metric, ERP, or journey masters |
| Value Stream Stage | **CONTAINED** | Owned only by one stream version. Fails as a root: no identity after removal from beneficiary, trigger, and terminal outcome |
| Exchange intent | **CONTAINED** | Optional specification of value object, direction, and counterparty role. Occurrences stay in WM-ECO-006, WM-ECO-008, WM-ECO-009, WM-ECO-020, WM-ECO-030, WM-XCT-029 |
| Terminal value-state | **CONTAINED** | Owned by the stream. Shape must be replaceable later by a pinned Outcome reference. Does not master observations |
| Value Stream Realization | **NEW** | Operating owner, distinct from the definition owner. Depends on one pinned stream version and one governing boundary. Reuses stewardship WM-XCT-001. Does not restate states |
| Stage–realizer binding | **CONTAINED** in Realization | References only. Realizer masters remain process, capability, unit, system, facility |
| Archetype and boundary role | **PROFILE** WM-KNW-018 / WM-XCT-020 | Classification facts. Not a root. Role is per boundary |
| Value Stream Map / View | **PROFILE / PROJECTION** | Non-authoritative picture of one definition plus optional realization and metrics. Follow the EM-LND-04 read-only landscape pattern. No runtime identity |
| Portfolio / landscape | **PROFILE / PROJECTION** | Selection filter, same landscape pattern. Investment selection reuses EM-WRK-04 over WM-ACT-029. EM-LND-11 must not own realization facts |
| Stream occurrence correlation | **PROFILE / PROJECTION** | View key only. No root |
| Value Exchange as a root | **Reject** | Mechanism belongs later to Business Model. Occurrences already have masters |
| Value Proposition | **CONTAINED**, already decided under EM-STR-01 | Theme/proposition inside the business-model contour. A stream may cite it. WM-ECO-021 is an offer occurrence, not the proposition |
| Outcome | **Defer** | EM-STR-02 rejected a combined Outcome+Benefit root and deferred two identities. The boundary-register identity statement is absent. Proof fails |
| Benefit Realization | **Reject as a root** | Program-owned assertions under EM-WRK-03; evidence reuses WM-ACT-034 and WM-MAT-008 |
| Business Capability | **Existing candidate, not in this minimum** | EM-STR-03. Reference only. Do not profile WM-ACT-001 into the stream |
| Capability Realization | **Existing candidate, not a substitute** | Different pair: capability to realizer, not stage to realizer |
| Metric Definition | **REUSE candidate EM-DAT-05** | Bindings, if drawn, sit on the map. A metric change must not version the stream |
| Journey | **Reject** | EM-TEC-06 remains specified-deferred and non-normative |
| Process execution | **REUSE** | WM-ACT-003 and EM-OPS-01. Do not narrow the process master into a stream |
| Business Model, Strategy, Strategic Scenario | **Out of minimum** | Already unassigned under EM-STR-01. Different identities: mechanism, choice set, hypothesis space. They may reference streams later. This study does not re-prove them |
| Financial, commercial, HR, risk, and work candidates | **REUSE or leave in their contours** | None of them masters a recipient-value progression |

No pending contour (EM-COM-01, EM-PEO-06, EM-XCT-01 through EM-XCT-10, EM-KRN-01) is treated as zero, success, or completion.

## F. Minimum new roots

### Value Stream — passes

- **Identity.** One governed recipient-value progression: primary beneficiary class, triggering need, ordered beneficiary value states, and one terminal outcome distinct from outputs. The frozen statement holds: it remains identifiable across process redesign, automation, and organization change.
- **Lifecycle.** Authored, reviewed, effective, superseded, or retired, independently of realizing processes, projects, systems, and reporting periods.
- **Mastership.** One definition owner under the EM-STR-01 contour. Strategy may select it. A business model may use it. A process may realize it. None of those is the master.
- **Version driver.** Semantic version changes only if beneficiary class, trigger class, state sequence or state meaning, or terminal outcome changes.
- **Transfer.** Another legal entity may adopt the same definition. Stewardship may move without changing identity. Redesign of work does not.
- **Aggregate.** Beneficiary specification; trigger; contained stages; contained terminal condition; optional contained exchange intent; archetype classification. Not contained: metrics, processes, systems, maps, benefits, cash, outcomes-as-catalogue.
- **Invariants.** Exactly one primary beneficiary class. At least an entry state and a terminal state. Each stage’s exit is the next stage’s entry. A stage is not an internal work step. External/internal is not intrinsic. Realization links are forbidden inside the definition. Absence of evidence is unknown, not failure.

### Value Stream Realization — passes, and is separate because ownership and version driver differ

- **Identity.** One governing boundary’s binding of exactly one immutable Value Stream version, plus a scope (enterprise-wide, or a referenced offering, unit, region, or population). Tool and diagram changes do not change it.
- **Lifecycle.** Proposed, active, superseded when the operating binding changes, while the definition remains.
- **Mastership.** The operation accountable for the operating model, not the definition owner.
- **Version driver.** Realizer set, stage-to-realizer mapping, scope, or effective interval. It must not change beneficiary, trigger, states, or terminal outcome. If those change, this object points at a new definition version instead.
- **Transfer.** Stewardship can move inside the same boundary and remain the same fact. Another enterprise adopting the definition gets a new realization. That is the correct result of the transfer test, not a failure.
- **Aggregate.** Pinned definition version; governing organization; scope references; contained stage bindings to pinned realizers; explicit gaps; stewardship reference. No restated value states.
- **Invariants.** Cannot “correct” a definition by local stages. Zero realizers on a stage is a gap, not a negative outcome. Many realizers per stage are allowed. The same realizer may serve many realizations.

**Near-misses that fail and are not roots.**

- Stage library: fails transfer once removed from its stream.
- Stream instance: occurrence facts already have masters; correlation is a view.
- Map, portfolio, landscape: views do not mint business identity; EM-LND-04 and EM-LND-11 stay projections.
- Value Exchange: no residue left after contained intent plus existing commercial masters.
- Outcome and Benefit: deferred or rejected by EM-STR-02; identity statement for the boundary register is absent.
- Value Proposition: already contained; it has no state progression.
- Separate external and internal roots: forbidden by the role rule.
- Profiling realization onto WM-XCT-037: impact dependency and operating realization are different facts. EM-WRK-06 already uses that dependency family for impact.

## G. Negative cases

1. **Order-to-cash.** Commercial process across WM-ECO-020, WM-ECO-008, WM-ECO-009, and WM-ECO-016. Invoice and cash are outputs. Customer value is Demand to realized use. Secured return is the capture stream. Payment proves neither outcome nor benefit.
2. **Hire-to-retire.** An HR process family across vacancy, employment, learning, payroll, and separation. It mixes enterprise benefit with worker benefit. Admissible pieces are Unmet contribution need to reliable contribution and Worker expectation to honored relationship, and only as value states, not as ATS steps.
3. **Incident-to-recovery.** WM-ACT-019, WM-ACT-042, and WM-ACT-021 workflow. Ticket closure is an output. The streams are restored external value or a restored internal baseline.
4. **Strategy-to-outcome.** A management chain across strategy, initiative, portfolio, project, and KPI. It has no single beneficiary progression. EM-STR-01 Strategy remains a choice set. Direction and operating-state streams cover only their own terminals. Benefit realization stays deferred.
5. **Data-to-insight.** Pipelines, studies, and reports (WM-DAT-005, WM-ACT-036, WM-REC-002). A published report is an output. Decision question to accepted understanding applies only when a named decision-maker’s accepted understanding is the terminal state. Otherwise it is not a stream.
6. **Procure-to-pay.** Requisition through payment. Accepted supply ends when fit input is accepted. Paying the supplier is settlement of the supplier’s claim, not proof that supply was fit.
7. **Lead-to-opportunity.** Seller states on WM-ECO-026 and WM-ECO-027. Awareness and pipeline stage are not beneficiary value states.
8. **Idea-to-product lifecycle.** Roadmap, design, and production run. Offering gap to releasable offering is admissible only when “releasable to a beneficiary” is the terminal state. Design approval alone is not.
9. **Record-to-report.** Close, consolidation, and statement issue (EM-FIN-04, WM-ECO-018). A statement is an output. Consolidation Scope and Run remain execution identities, not streams.
10. **Plan-to-deliver.** Project phases, milestones, and gate reviews. WM-ACT-005 completion does not mean an operating state is in force or that a beneficiary outcome occurred.
11. **Customer-journey map.** Touchpoints and channels. EM-TEC-06 User Journey stays deferred and non-normative. It does not become a stream by being drawn under the stream’s name.
12. **Application workflow.** Status machines inside WM-SFT-002 or case tools. System state is not beneficiary state.
13. **Generic value chain.** A fixed list of primary and support activities. No beneficiary, trigger, or terminal outcome. Excluded even if every department is mapped onto it.
14. **Risk-register-to-heatmap.** Maintenance of WM-KNW-015 rows and a view. An authorized risk position is a stream only when the owner’s position is the terminal state. The heatmap is a projection.
15. **Deploy-to-operate.** Build, release, and deployment (WM-SFT-008, WM-SFT-009). Go-live is an output. It realizes Ability gap to reliable ability only if reliability of the ability is the terminal state.
16. **Cost-to-serve.** A metric view over delivery, using EM-FIN-05. Cost is neither the beneficiary outcome nor value capture.

## H. Adjudication

| Concept | Decision |
|---|---|
| Value Stream | **Accept as the definition root.** Unassigned. Do not duplicate the EM-STR-01 candidate |
| Value Stream Stage | **Contain** in that root. Reject an independent stage root |
| Value Stream Map / View | **Projection only.** Not a master. No identifier |
| Value Stream Portfolio / Landscape | **Projection or filter.** Investment selection reuses the existing portfolio profile. No new root |
| Value Exchange | **Not a root.** Contain the intent; reuse commercial and obligation masters for occurrences; leave the mechanism to Business Model later |
| Outcome | **Defer.** Do not create. Terminal condition stays inside the stream until a separate identity statement exists |
| Benefit Realization | **Reject as a root.** Keep program-owned assertions and assessment evidence. Distinct from outcome, output, and capture |
| Business Capability | **Do not create here.** Existing EM-STR-03 candidate may be referenced. Not required to publish a stream |
| Capability Realization | **Do not create here and do not overload it.** Different binding from stream realization |
| Metric Definition | **Reuse the EM-DAT-05 candidate by reference from maps.** Not part of stream identity |
| Value Proposition | **Keep contained** in the EM-STR-01 theme/proposition decision. Not a stream |
| Journey | **Reject.** Remains deferred and non-normative. WM-FLW-009 is a trip, not a value stream |
| Process Execution | **Reuse** WM-ACT-003 and EM-OPS-01 as realizers and execution records only |

Also decided, because otherwise the two accepted roots collapse: **Value Stream Realization is a second root.** **A stream instance is only a correlation view.**

## I. Implementation sequence

No identifier is allocated and nothing here is a canonical publication. EM-XCT-10 remains pending, so this is an order for a later registry act.

**Must-have roots, in this order.**

1. **Value Stream**, with contained beneficiary, trigger, stages, terminal value-state, and optional exchange intent. Publish no realizer facts in this slice.
2. **Archetype and boundary-role classifications** as profiles on that root. Still no new identifier.
3. **Value Stream Realization**, only after a definition version can be pinned. Until it exists, realization facts stay unknown; they must not be written into the definition “temporarily.”
4. **Map and landscape projections**, non-authoritative, only after readers can see which object masters the stream. Metric bindings on a map wait for a real Metric Definition reference; otherwise the binding stays unknown.

**Optional later, and not blockers.**

- Business Model, Strategy, and Strategic Scenario referencing streams, still under EM-STR-01.
- Outcome, then Benefit, only if a later study supplies the missing identity statements. Then replace contained terminal copies with pinned references; do not rename the streams.
- Business Capability and Capability Realization links.
- User Journey overlay, still non-normative.
- Portfolio selection of streams through the existing investment-portfolio profile.
- Right objects already hypothesized elsewhere (consumption entitlement, regulatory authorization, licence) for variants of granted right and standing. They are not stream roots.

The safe first publication is definition-only: steps 1 and 2. That slice does not claim that realization, outcome, benefit, capture, or measurement has been modeled.