Value Stream
Represent a governed, outside-in progression from a beneficiary need and trigger through contained beneficiary value-state stages to a terminal value outcome, independently of the processes, systems and organization that realize it.
Bundle → Layer → Finding → Questions Filled
3 bundles · 8 layers · 8 findings · 24 questions
Identity and boundary Defines stable stream identity relative to a governed Enterprise boundary.
Stream identity
One recipient-value progression remains identifiable across process, system and organization redesign.
Stream identity
One recipient-value progression remains identifiable across process, system and organization redesign.
- What authoritative identity and scope establish stream identity? identity
- Which change creates a successor for stream identity? classification
- Which evidence supports stream identity without copying another master? provenance
Enterprise boundary role
Internal and external are roles relative to a governed enterprise boundary, not separate roots.
Enterprise boundary role
Internal and external are roles relative to a governed enterprise boundary, not separate roots.
- What authoritative identity and scope establish enterprise boundary role? ownership
- Which change creates a successor for enterprise boundary role? authority
- Which evidence supports enterprise boundary role without copying another master? access
Beneficiary progression Defines beneficiary need, trigger, contained stages and terminal value state.
Beneficiary and need
The stream begins with a named beneficiary role and a need the enterprise undertakes to satisfy.
Beneficiary and need
The stream begins with a named beneficiary role and a need the enterprise undertakes to satisfy.
- What authoritative identity and scope establish beneficiary and need? definition
- Which change creates a successor for beneficiary and need? relationship
- Which evidence supports beneficiary and need without copying another master? validation
Trigger
A recognizable event or condition starts the value progression.
Trigger
A recognizable event or condition starts the value progression.
- What authoritative identity and scope establish trigger? event
- Which change creates a successor for trigger? temporal
- Which evidence supports trigger without copying another master? constraint
Stage sequence
Contained stages record ordered beneficiary value-state changes rather than internal tasks.
Stage sequence
Contained stages record ordered beneficiary value-state changes rather than internal tasks.
- What authoritative identity and scope establish stage sequence? composition
- Which change creates a successor for stage sequence? process
- Which evidence supports stage sequence without copying another master? interoperability
Terminal value outcome
The terminal condition is distinct from output, delivery, completion, payment and benefit realization.
Terminal value outcome
The terminal condition is distinct from output, delivery, completion, payment and benefit realization.
- What authoritative identity and scope establish terminal value outcome? measurement
- Which change creates a successor for terminal value outcome? quality
- Which evidence supports terminal value outcome without copying another master? evidence
Governance and realization Separates definition governance from mutable realization and evidence.
Version and lifecycle
Released versions are immutable and change only when beneficiary, trigger, state sequence or terminal outcome changes.
Version and lifecycle
Released versions are immutable and change only when beneficiary, trigger, state sequence or terminal outcome changes.
- What authoritative identity and scope establish version and lifecycle? lifecycle
- Which change creates a successor for version and lifecycle? state
- Which evidence supports version and lifecycle without copying another master? retention
Realization separation
Processes, capabilities, units and systems realize stages by reference and never define the stream identity.
Realization separation
Processes, capabilities, units and systems realize stages by reference and never define the stream identity.
- What authoritative identity and scope establish realization separation? security
- Which change creates a successor for realization separation? privacy
- Which evidence supports realization separation without copying another master? exception
Classifiers Filled
- Family
- World Models
- Category
- Activities and processes
- Entry kind
- aggregate
- Navigation path
- NAV.ACT.VST
- Domain
- ACT.VST
- Industry
- Cross-industry
- Tags
- valuestreamact.vstenterprise value streamvalue creation stream
- Also called
- Enterprise Value Stream, Value Creation Stream
What it is Filled
Owns stable Value Stream identity, immutable definition versions, beneficiary and enterprise-boundary role, trigger class, contained stage order and value states, entry and exit criteria, terminal outcome class and lifecycle. It references realization, objectives, observations and decisions without absorbing their mastership.
In scope
- Stable value-stream identity and immutable definition versions
- Beneficiary need, trigger, contained stage sequence and terminal value outcome
- Internal, inbound, outbound and reciprocal roles relative to a governed Enterprise boundary
Out of scope
- Process steps, customer touchpoints, projects, systems, organization charts, observations, financial postings and benefit realization
Why it exists Filled
Represent a governed, outside-in progression from a beneficiary need and trigger through contained beneficiary value-state stages to a terminal value outcome, independently of the processes, systems and organization that realize it.
Distinguishing features Filled
- Describes the end-to-end stages by which a beneficiary receives value, not the steps or tasks that perform the work.
- Starts from a trigger and ends in a terminal outcome class that matters to the beneficiary.
- Stage order and value states are versioned definitions, separate from any observed realization.
- Differs from a process or workflow, which defines how activities are executed and by whom.
What robots and AI may and may not do Filled
Must not
- Edit a published definition version in place instead of issuing a new one.
- Treat a value stream map as a process specification or as authority to reorganize work.
- Assign performance targets to named people from value stream metrics alone.
- Merge streams with different beneficiaries into one definition.
Only with a human decision
- Approving a value stream definition as an official version.
- Retiring a value stream that strategy or funding decisions reference.
- Choosing the beneficiary and the enterprise boundary.
May
- Draft a value stream definition with trigger, stages, entry and exit criteria and terminal outcome.
- Link a value stream version to realizations, objectives and observations owned elsewhere.
- Compare two definition versions and report changed stages.
- Flag stages that have no realizing process or capability.
Moral aspects Filled
- Choosing whose value counts decides whose needs drive redesign; secondary beneficiaries can be left out.
- Value stream analysis is often used to justify cutting roles, and the people affected should have a voice.
- Outcome measures should reflect real benefit to the beneficiary, not only internal efficiency.
Who is affected
- Customers and other beneficiaries of the stream
- Staff who perform the realizing processes
- Decision makers who fund and prioritize stages
Owners Filled
Steward
Owning Dimension identifier
Roles
- Model steward
- Own definitions and version decisions.
- Operating owner
- Own adoption and realization evidence.
- Evidence producer
- Supply attributable observations and source references.
- Reviewer
- Review boundary, invariants and publication holds.
Links to other meta-models Filled
references
- WM-XCT-023 - Beneficiary and counterparty roles
- WM-ACT-015 - Trigger occurrence classes
- WM-XCT-022 - Immutable version and successor semantics
- WM-KNW-011 - Goal and objective alignment
- WM-ACT-003 - Process realization without identity import
- WM-XCT-041 - Governed enterprise realization binding
neighbor
- WM-ACT-003 Process / Workflow - A process is an internal realization mechanism. Redesigning it does not change the stream while beneficiary value states remain stable.
- Outcome and Benefit Realization - The stream defines its intended terminal value-state class but does not assert observed outcome or realized benefit.
- Value Stream Realization - Operating adoption and realizer bindings are governed separately from the definition and may change without revising the stream.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Authoritative master-system identifier
- Owning-Dimension identifier
- Content digest
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Filled
- A value stream has a named beneficiary, a triggering event, an ordered set of value-adding stages and a terminal outcome.
- It is confused with a process model, a customer journey map and a lean value stream map of material flow.
Capabilities and actions required Filled
- Register value stream: Create a stable identity and initial immutable definition.
- Release stream version: Freeze a reviewed definition revision.
- Supersede stream version: Link a successor after a semantic change.
- Classify boundary role: Classify one stream relative to a pinned enterprise boundary.
Hazards and failure modes required Filled
- Redesign based on an outdated stream definition.
- Benefits claimed for a stage that has no realization behind it.
- Local optimization of one stage that harms the end-to-end outcome.
Standards and interfaces required Filled
- The Open Group ArchiMate value stream element.
- TOGAF Series Guide on value streams.
- BIZBOK Guide value stream mapping practice.
- OMG BPMN 2.0 for linking realizing processes.
Context of use required Filled
- No jurisdiction-specific meaning is inferred; local duties and rights remain external.
Sources Filled
- Process / Workflow - Vercy
- Occurrence / Event - Vercy
- Party Role - Vercy
- Goal / Objective - Vercy
- Version / Change History - Vercy
- Dependency / Impact Edge - Vercy
- Claude enterprise value-stream study - Anthropic Claude
- Grok enterprise value-stream study - xAI Grok
- Value Delivery Modeling Language (VDML) 1.1 - Object Management Group
- Process Classification Framework - APQC
Open questions
- Allocate Business Capability, Capability Realization and Metric Definition through their owning contours.
- Validate industry-specific profiles without changing the generic identity rule.
- Observed outcome and benefit realization remain external.
- Industry-specific stage vocabularies are profiles.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-act-055-value-stream/spec.yaml, ver-cy/world-models/card-supplements/wm-act-055-value-stream.json