{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-055","code":"wm-act-055-value-stream","url":"https://ver.cy/models/wm-act-055-value-stream/","name":"Value Stream","alternateNames":["Enterprise Value Stream","Value Creation Stream"],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"aggregate","plane":"","domain":["ACT.VST"],"industry":["Cross-industry"],"navPath":"NAV.ACT.VST","tags":["value","stream","act.vst","enterprise value stream","value creation stream"],"facets":{}},"whatItIs":"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.","purpose":"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.","scope":{"in":["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":["Process steps, customer touchpoints, projects, systems, organization charts, observations, financial postings and benefit realization"],"boundaries":[{"neighbor":"WM-ACT-003 Process / Workflow","distinction":"A process is an internal realization mechanism. Redesigning it does not change the stream while beneficiary value states remain stable."},{"neighbor":"Outcome and Benefit Realization","distinction":"The stream defines its intended terminal value-state class but does not assert observed outcome or realized benefit."},{"neighbor":"Value Stream Realization","distinction":"Operating adoption and realizer bindings are governed separately from the definition and may change without revising the stream."}]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"vs-b1","name":"Identity and boundary","description":"Defines stable stream identity relative to a governed Enterprise boundary.","layers":[{"id":"vs-b1-l1","name":"Stream identity","description":"One recipient-value progression remains identifiable across process, system and organization redesign.","findings":[{"id":"vs-f01","name":"Stream identity","description":"One recipient-value progression remains identifiable across process, system and organization redesign.","questions":[{"text":"What authoritative identity and scope establish stream identity?","id":"vs-f01-q01","kind":"identity"},{"text":"Which change creates a successor for stream identity?","id":"vs-f01-q02","kind":"classification"},{"text":"Which evidence supports stream identity without copying another master?","id":"vs-f01-q03","kind":"provenance"}]}]},{"id":"vs-b1-l2","name":"Enterprise boundary role","description":"Internal and external are roles relative to a governed enterprise boundary, not separate roots.","findings":[{"id":"vs-f02","name":"Enterprise boundary role","description":"Internal and external are roles relative to a governed enterprise boundary, not separate roots.","questions":[{"text":"What authoritative identity and scope establish enterprise boundary role?","id":"vs-f02-q01","kind":"ownership"},{"text":"Which change creates a successor for enterprise boundary role?","id":"vs-f02-q02","kind":"authority"},{"text":"Which evidence supports enterprise boundary role without copying another master?","id":"vs-f02-q03","kind":"access"}]}]}]},{"id":"vs-b2","name":"Beneficiary progression","description":"Defines beneficiary need, trigger, contained stages and terminal value state.","layers":[{"id":"vs-b2-l1","name":"Beneficiary and need","description":"The stream begins with a named beneficiary role and a need the enterprise undertakes to satisfy.","findings":[{"id":"vs-f03","name":"Beneficiary and need","description":"The stream begins with a named beneficiary role and a need the enterprise undertakes to satisfy.","questions":[{"text":"What authoritative identity and scope establish beneficiary and need?","id":"vs-f03-q01","kind":"definition"},{"text":"Which change creates a successor for beneficiary and need?","id":"vs-f03-q02","kind":"relationship"},{"text":"Which evidence supports beneficiary and need without copying another master?","id":"vs-f03-q03","kind":"validation"}]}]},{"id":"vs-b2-l2","name":"Trigger","description":"A recognizable event or condition starts the value progression.","findings":[{"id":"vs-f04","name":"Trigger","description":"A recognizable event or condition starts the value progression.","questions":[{"text":"What authoritative identity and scope establish trigger?","id":"vs-f04-q01","kind":"event"},{"text":"Which change creates a successor for trigger?","id":"vs-f04-q02","kind":"temporal"},{"text":"Which evidence supports trigger without copying another master?","id":"vs-f04-q03","kind":"constraint"}]}]},{"id":"vs-b2-l3","name":"Stage sequence","description":"Contained stages record ordered beneficiary value-state changes rather than internal tasks.","findings":[{"id":"vs-f05","name":"Stage sequence","description":"Contained stages record ordered beneficiary value-state changes rather than internal tasks.","questions":[{"text":"What authoritative identity and scope establish stage sequence?","id":"vs-f05-q01","kind":"composition"},{"text":"Which change creates a successor for stage sequence?","id":"vs-f05-q02","kind":"process"},{"text":"Which evidence supports stage sequence without copying another master?","id":"vs-f05-q03","kind":"interoperability"}]}]},{"id":"vs-b2-l4","name":"Terminal value outcome","description":"The terminal condition is distinct from output, delivery, completion, payment and benefit realization.","findings":[{"id":"vs-f06","name":"Terminal value outcome","description":"The terminal condition is distinct from output, delivery, completion, payment and benefit realization.","questions":[{"text":"What authoritative identity and scope establish terminal value outcome?","id":"vs-f06-q01","kind":"measurement"},{"text":"Which change creates a successor for terminal value outcome?","id":"vs-f06-q02","kind":"quality"},{"text":"Which evidence supports terminal value outcome without copying another master?","id":"vs-f06-q03","kind":"evidence"}]}]}]},{"id":"vs-b3","name":"Governance and realization","description":"Separates definition governance from mutable realization and evidence.","layers":[{"id":"vs-b3-l1","name":"Version and lifecycle","description":"Released versions are immutable and change only when beneficiary, trigger, state sequence or terminal outcome changes.","findings":[{"id":"vs-f07","name":"Version and lifecycle","description":"Released versions are immutable and change only when beneficiary, trigger, state sequence or terminal outcome changes.","questions":[{"text":"What authoritative identity and scope establish version and lifecycle?","id":"vs-f07-q01","kind":"lifecycle"},{"text":"Which change creates a successor for version and lifecycle?","id":"vs-f07-q02","kind":"state"},{"text":"Which evidence supports version and lifecycle without copying another master?","id":"vs-f07-q03","kind":"retention"}]}]},{"id":"vs-b3-l2","name":"Realization separation","description":"Processes, capabilities, units and systems realize stages by reference and never define the stream identity.","findings":[{"id":"vs-f08","name":"Realization separation","description":"Processes, capabilities, units and systems realize stages by reference and never define the stream identity.","questions":[{"text":"What authoritative identity and scope establish realization separation?","id":"vs-f08-q01","kind":"security"},{"text":"Which change creates a successor for realization separation?","id":"vs-f08-q02","kind":"privacy"},{"text":"Which evidence supports realization separation without copying another master?","id":"vs-f08-q03","kind":"exception"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["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."]},"ethics":{"considerations":["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."],"affectedParties":["Customers and other beneficiaries of the stream","Staff who perform the realizing processes","Decision makers who fund and prioritize stages"]},"owners":{"steward":"Owning Dimension identifier","roles":[{"name":"Model steward","responsibilities":["Own definitions and version decisions."]},{"name":"Operating owner","responsibilities":["Own adoption and realization evidence."]},{"name":"Evidence producer","responsibilities":["Supply attributable observations and source references."]},{"name":"Reviewer","responsibilities":["Review boundary, invariants and publication holds."]}],"masterSystems":[]},"relations":[{"target":"WM-XCT-023","type":"references","note":"Beneficiary and counterparty roles"},{"target":"WM-ACT-015","type":"references","note":"Trigger occurrence classes"},{"target":"WM-XCT-022","type":"references","note":"Immutable version and successor semantics"},{"target":"WM-KNW-011","type":"references","note":"Goal and objective alignment"},{"target":"WM-ACT-003","type":"references","note":"Process realization without identity import"},{"target":"WM-XCT-041","type":"references","note":"Governed enterprise realization binding"},{"target":"WM-ACT-003 Process / Workflow","type":"neighbor","note":"A process is an internal realization mechanism. Redesigning it does not change the stream while beneficiary value states remain stable."},{"target":"Outcome and Benefit Realization","type":"neighbor","note":"The stream defines its intended terminal value-state class but does not assert observed outcome or realized benefit."},{"target":"Value Stream Realization","type":"neighbor","note":"Operating adoption and realizer bindings are governed separately from the definition and may change without revising the stream."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Owning-Dimension identifier","Content digest"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["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":{"applicability":"required","items":["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":{"applicability":"required","items":["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."]},"interfaces":{"applicability":"required","items":["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":{"applicability":"required","items":["No jurisdiction-specific meaning is inferred; local duties and rights remain external."]}},"sources":[{"title":"Process / Workflow","url":"https://ver.cy/models/wm-act-003-process-workflow/spec.yaml","note":"Vercy"},{"title":"Occurrence / Event","url":"https://ver.cy/models/wm-act-015-occurrence-event/spec.yaml","note":"Vercy"},{"title":"Party Role","url":"https://ver.cy/models/wm-xct-023-party-role/spec.yaml","note":"Vercy"},{"title":"Goal / Objective","url":"https://ver.cy/models/wm-knw-011-goal-objective/spec.yaml","note":"Vercy"},{"title":"Version / Change History","url":"https://ver.cy/models/wm-xct-022-version-change-history/spec.yaml","note":"Vercy"},{"title":"Dependency / Impact Edge","url":"https://ver.cy/models/wm-xct-037-dependency-impact-edge/spec.yaml","note":"Vercy"},{"title":"Claude enterprise value-stream study","url":"https://ver.cy/enterprise/research/value-streams-2026-10-04/claude-study.raw.md","note":"Anthropic Claude"},{"title":"Grok enterprise value-stream study","url":"https://ver.cy/enterprise/research/value-streams-2026-10-04/grok-study.raw.md","note":"xAI Grok"},{"title":"Value Delivery Modeling Language (VDML) 1.1","url":"https://www.omg.org/spec/VDML/1.1","note":"Object Management Group"},{"title":"Process Classification Framework","url":"https://www.apqc.org/process-frameworks","note":"APQC"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-act-055-value-stream/spec.yaml","agents":"/models/wm-act-055-value-stream/AGENTS.md","source":"https://ver.cy/enterprise/research/value-streams-2026-10-04/"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-055-value-stream/spec.yaml","ver-cy/world-models/card-supplements/wm-act-055-value-stream.json"],"providers":["Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-04T17:55:00Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}