1. Executive Summary

This plan formally defines the six ITILv4 Service Value Chain (SVC) activities and maps them to the four existing Value Streams (VS01-VS04). It renames the existing “Value System Chain” terminology to Value Stream Chain and introduces a new cross-cutting governance document that defines each activity, its purpose, and the management practices most commonly associated with it.

The plan also renames 01 Value Stream Map.md to 01 Value Stream Stages.md across all Value Stream folders to better reflect the file’s purpose (showing which SVC activity stages a Value Stream traverses, with associated practices), and updates all references throughout the repository.

The solution formalises:

• Six Value Stream Chain activities (Plan, Improve, Engage, Design & Transition, Obtain | Build, Deliver & Support) with full definitions (currently empty “XXX” in archived source material)
• A terminology mapping table from Calab.ai terms to ITILv4 equivalents
• A new governance-level document in content/00 Governance/ defining the Value Stream Chain
• Mermaid diagrams in each VS’s renamed 01 Value Stream Stages.md showing which SVC stages that Value Stream traverses and what practices/processes participate at each stage
• A decision (Decision 09) recording the terminology and file-rename decisions
• Updated references across 15+ files throughout the repository

Key outcomes:

• Value Stream Chain activities have authoritative definitions in the live handbook (migrated from archived, incomplete content)
• Each Value Stream clearly shows its relationship to SVC activity stages via visual diagrams
• Consistent terminology throughout the handbook with an explicit mapping to ITILv4 standards
• File names accurately reflect content purpose (“Stages” vs. “Map”)

Critical dependencies:

• No external dependencies — all changes are content and reference updates within the existing repository
• Existing VS01 Mermaid diagram content must be preserved and adapted (not lost) during rename

2. Architecture / Context Overview

Background

The archived document content/99 Archive/Human Resources (deprecated 2026-02-11)/03 Operational Governance.md introduced the “Value System Chain” concept with six activities directly adapted from ITILv4’s Service Value Chain. However, the activity descriptions were left as empty placeholders (“XXX”) and the entire document was subsequently archived during the Plan 01 governance restructure.

The live handbook currently has:

• No active SVC activity definitions anywhere in published content
• Four Value Streams (VS01-VS04) with 01 Value Stream Map.md files, of which only VS01 has substantive Mermaid diagram content; VS02-VS04 are empty stubs
• Terminology inconsistency — the archived doc uses “Value System Chain” while ITILv4 uses “Service Value Chain”

Terminology Decision

This plan adopts “Value Stream Chain” as the primary Calab.ai term, replacing both the legacy “Value System Chain” and the ITILv4 “Service Value Chain”. This term:

• Makes the relationship to Value Streams immediately obvious
• Is more accessible than ITILv4’s formal “Service Value Chain” terminology
• Corrects the archived “Value System” naming which conflated the chain with the broader system

Terminology Mapping Table (to be included in the new governance document):

File Rename Rationale

The current file 01 Value Stream Map.md is being renamed to 01 Value Stream Stages.md because:

1. Accuracy — The file’s purpose is to show which Value Stream Chain activity stages a VS traverses, not a generic “map”
2. Disambiguation — “Map” conflicts with L1 Value Stream Map diagrams (per Decision 07 diagram hierarchy), which are Mermaid diagrams embedded within this file. The file contains stages with diagrams, not just a single map
3. Alignment — The name “Stages” directly connects to the Value Stream Chain activities concept being introduced

Governance Model Alignment

Per the established governance principles:

• Company Governance owns cross-cutting methodology documents — the Value Stream Chain definition document belongs in content/00 Governance/
• Value Streams own their own VS folder documents — each VS’s 01 Value Stream Stages.md remains owned by the VS
• Practices own artefacts — practices referenced within VS stage diagrams are links, not duplicated content

Six Value Stream Chain Activities

The six activities, adapted from ITILv4 with Calab.ai-specific context:

VS-to-Activity Stage Mapping

Each Value Stream traverses a subset of the six activities. The primary mappings:

Files Requiring Changes

Files to rename (git mv)

Files to create

Files requiring reference updates (14 files)

1. content/01 Value Streams/VS01 Hire to High Performer/README.md — link to 01 Value Stream Map
2. content/01 Value Streams/VS02 Discovery to Deployment/README.md — link to 01 Value Stream Map
3. content/01 Value Streams/VS03 Request to Release/README.md — link to 01 Value Stream Map
4. content/01 Value Streams/VS04 Incident to Resolution/README.md — link to 01 Value Stream Map
5. content/00 Governance/Plans/01 Governance Model & Content Structure/README.md — reference to 01 Value Stream Map.md
6. content/00 Governance/Plans/08 Automated Content Scaffolding/README.md — template strings referencing 01 Value Stream Map
7. content/_authoring/diagrams/mermaid/L1-value-stream-guide.md — references to 01 Value Stream Map
8. content/_authoring/diagrams/mermaid/L2-process-map-guide.md — references to 01 Value Stream Map
9. content/_authoring/diagrams/mermaid/L3-sub-process-map-guide.md — reference to 01 Value Stream Map
10. content/_authoring/diagrams/mermaid/L4-procedure-map-guide.md — reference to 01 Value Stream Map
11. content/00 Governance/Decisions/07 Knowledge Management Practice.md — reference to 01 Value Stream Map
12. content/00 Governance/Decisions/08 README as Folder Index Standard.md — references to 01 Value Stream Map
13. .opencode/skills/mermaid-diagrams/SKILL.md — references to 01 Value Stream Map
14. content/00 Governance/Plans/05 Remove README Pattern/README.md — references to 01 Value Stream Map

3. Implementation Steps

All steps are sequential. Each step must be completed and verified before proceeding to the next.

Branch Strategy: All implementation work should be performed in a feature branch (feat/svc-activities) and tested before merging to main.

Step 0 — Create Decision 09: Value Stream Chain Terminology and File Rename

Tasks

0.1 Create decision document:

Create content/00 Governance/Decisions/09 Value Stream Chain Terminology and File Rename.md with the following structure:

---
publish: true
page-status: approved
created: 2026-03-02
owner: guild-executive
type: decision
decision-status: Accepted
---
 
# Decision 09 — Value Stream Chain Terminology and File Rename
 
## Status
 
Accepted
 
## Context
 
The archived Operational Governance document (deprecated 2026-02-11) introduced the concept of
a "Value System Chain" with six activities adapted from ITILv4's Service Value Chain. However:
 
1. The activity descriptions were never completed (all marked "XXX")
2. The document was archived during the Plan 01 governance restructure
3. The terminology "Value System Chain" conflated the chain concept with the broader
   "Value System Architecture"
4. The file `01 Value Stream Map.md` in each Value Stream folder did not clearly convey
   its purpose of showing which SVC activity stages a VS traverses
 
Additionally, each Value Stream folder contains a file named `01 Value Stream Map.md`.
This name is ambiguous because:
 
- It conflicts with the L1 Value Stream Map diagram concept defined in Decision 07
- The file's actual purpose is to define the stages (Value Stream Chain activities) that the
  Value Stream traverses, not just provide a single map visual
 
## Decision
 
1. **Rename terminology:** Adopt "Value Stream Chain" as the Calab.ai term for the set of
   six activity stages, replacing the legacy "Value System Chain". Include a mapping table to
   ITILv4 equivalent terms for cross-reference.
 
2. **Rename file:** Rename `01 Value Stream Map.md` to `01 Value Stream Stages.md` across
   all four Value Stream folders (VS01-VS04) and update all references throughout the repository.
 
3. **Create governance document:** Create `content/00 Governance/05 Value Stream Chain.md`
   as the authoritative definition of the six Value Stream Chain activities.
 
4. **Populate VS stage files:** Each Value Stream's `01 Value Stream Stages.md` should contain
   a Mermaid diagram showing which Value Stream Chain activity stages the VS traverses and which
   management practices participate at each stage.
 
## Consequences
 
**Positive:**
 
- Clear, authoritative definitions for all six SVC activities in the live handbook
- File names accurately reflect content purpose
- Consistent terminology with explicit ITILv4 mapping
- Value Streams visually show their relationship to the methodology
 
**Negative:**
 
- 14+ files require reference updates (one-time migration cost)
- Contributors must learn the new "Value Stream Chain" term
- Existing bookmarks or external links to `01 Value Stream Map` will break
 
**Risks:**
 
- References may be missed during update (mitigated by comprehensive search in plan)
- Future Value Streams (if added) must follow the same pattern
 
## Alternatives Considered
 
1. **Keep "Value System Chain"** — Rejected because it conflates chain with system
2. **Use ITILv4's "Service Value Chain"** — Rejected; "Value Stream Chain" is more intuitive
   for readers already familiar with Value Streams
3. **Keep filename "01 Value Stream Map.md"** — Rejected; does not describe the staged
   activity content being introduced

Deliverable

Decision 09 document created and committed.

Verification

• File exists at content/00 Governance/Decisions/09 Value Stream Chain Terminology and File Rename.md
• Decision follows the existing format (matches Decision 07, Decision 08 structure)
• Status is “Accepted”
• All four decision points are documented

Step 1 — Create the Value Stream Chain Governance Document

Tasks

1.1 Create content/00 Governance/05 Value Stream Chain.md:

This document serves as the authoritative, cross-cutting reference for the Value Stream Chain concept. It should include:

Frontmatter:

---
publish: true
page-status: active
created: 2026-03-02
owner: guild-executive
type: governance-reference
---

Required sections:

1. Purpose — Explain that the Value Stream Chain defines six standard stages of work used as a conceptual lens to describe how value is created and delivered. These stages are not a strict lifecycle; they can occur in different sequences, repeat, and operate in parallel.

2. Terminology Mapping — Include the mapping table from Section 2 of this plan, showing Calab.ai terms vs ITILv4 equivalents.

3. Value Stream Chain Activities — Define all six activities with the descriptions from Section 2 of this plan (Plan, Improve, Engage, Design & Transition, Obtain | Build, Deliver & Support). Each activity should include:

   • Purpose: What the activity achieves
   • Key inputs: What triggers or feeds the activity
   • Key outputs: What the activity produces
   • Commonly involved practices: Which management practices are most frequently invoked (as links to practice READMEs)

4. How Value Streams Use the Chain — Explain that each Value Stream traverses a subset of the six activities depending on the type of value being delivered. Include the VS-to-Activity mapping table from Section 2.

5. Relationship to Management Practices — Explain that practices are invoked by Value Streams at specific stages. A single practice may participate in multiple stages across multiple Value Streams.

6. Diagram — Include a high-level Mermaid diagram showing the six activities and the flow between them (adapted from the ITILv4 Service Value Chain visual):

block-beta
   columns 1

   DEMAND(("Demand"))

   block:VSC
      columns 1
      ENGAGE["Engage"]

      block:OUTER
         columns 2
         PLAN["Plan"]
         IMPROVE["Improve"]
      end

      block:CORE
         columns 3
         BUILD["Build | Obtain"]
         SUPPORT["Support | Deliver"]
         DESIGN["Design | Transition"]
      end

      SERVICE["Products & Services"]
   end

   VALUE(("Value"))

   DEMAND --> VSC 
   VSC --> VALUE

7. Related Resources — Links to:

   • [[02 Operating Model|Organisational Structure]]
   • [[01 Value Streams/README|Value Stream Index]]
   • Each VS’s 01 Value Stream Stages document

8. Version footer with version, date, and maintainer.

1.2 Activity-to-Practice mapping reference:

Within the activity definitions, include indicative practice associations. The following mapping provides the recommended starting point:

Note: This mapping is indicative and will evolve as practices mature. Each VS’s 01 Value Stream Stages.md file carries the authoritative mapping for that specific Value Stream.

Deliverable

Governance document 05 Value Stream Chain.md created in content/00 Governance/ with all required sections populated.

Verification

• File exists at content/00 Governance/05 Value Stream Chain.md
• All six activities have complete definitions (no “XXX” placeholders)
• Terminology mapping table is present
• VS-to-Activity mapping table is present
• Mermaid diagram renders correctly
• Practice links use valid Obsidian wikilink syntax
• Frontmatter has page-status: active

Step 2 — Rename Value Stream Map Files to Value Stream Stages

Tasks

2.1 Rename files using git mv:

Execute the following renames (preserving git history):

git mv "content/01 Value Streams/VS01 Hire to High Performer/01 Value Stream Map.md" \
       "content/01 Value Streams/VS01 Hire to High Performer/01 Value Stream Stages.md"
 
git mv "content/01 Value Streams/VS02 Discovery to Deployment/01 Value Stream Map.md" \
       "content/01 Value Streams/VS02 Discovery to Deployment/01 Value Stream Stages.md"
 
git mv "content/01 Value Streams/VS03 Request to Release/01 Value Stream Map.md" \
       "content/01 Value Streams/VS03 Request to Release/01 Value Stream Stages.md"
 
git mv "content/01 Value Streams/VS04 Incident to Resolution/01 Value Stream Map.md" \
       "content/01 Value Streams/VS04 Incident to Resolution/01 Value Stream Stages.md"

2.2 Update internal headings in each renamed file:

For each renamed file, update the top-level heading and any self-referencing text to use “Value Stream Stages” instead of “Value Stream Map”.

Deliverable

All four files renamed with git history preserved.

Verification

• 01 Value Stream Map.md no longer exists in any VS folder
• 01 Value Stream Stages.md exists in all four VS folders
• git log --follow shows history is preserved for each file
• File content headings updated to match new name

Step 3 — Update All Cross-Repository References

Tasks

Update every file that references 01 Value Stream Map to use 01 Value Stream Stages instead. The comprehensive list of files and the specific changes required:

3.1 Value Stream READMEs (4 files):

Also update any surrounding descriptive text — e.g. "Visual flow diagram and stage definitions" can remain or be updated to "Value Stream Chain activity stages and practice participation".

3.2 Plan documents (3 files):

3.3 Diagram guide documents (4 files):

3.4 Decision documents (2 files):

3.5 Agent skill files (1 file):

3.6 Final sweep:

After all targeted updates, run a repository-wide search for any remaining references to Value Stream Map (excluding the 99 Archive/ folder and this plan) to catch any missed occurrences. The search should cover:

grep -r "Value Stream Map" --include="*.md" content/ .opencode/ .github/ | grep -v "99 Archive"

Deliverable

All 14 files updated with zero remaining references to 01 Value Stream Map in active content.

Verification

• Repository-wide search for "01 Value Stream Map" returns zero results outside 99 Archive/ and this plan
• All Obsidian wikilinks resolve correctly (no broken links)
• No unintended changes to other content

Step 4 — Populate Value Stream Stages Files with Mermaid Diagrams

Tasks

Populate each VS’s 01 Value Stream Stages.md with:

1. An updated heading and purpose section explaining the Value Stream Chain activity stages
2. A Mermaid flowchart diagram showing which SVC activities the VS traverses, with practices shown at each stage
3. A tabular summary of stages with descriptions specific to that VS

4.1 VS01 Hire to High Performer — Update existing content:

VS01 already has a Mermaid diagram with three stages (Onboarding, Progression, Remuneration). This existing content should be preserved and enhanced, not replaced. The enhancement adds:

• A mapping section showing how the three existing stages relate to Value Stream Chain activities
• The existing Mermaid diagram remains as the primary visual
• A new section (or table) explicitly mapping: Onboarding → Engage + Design & Transition, Progression → Deliver & Support + Improve, Remuneration → Plan + Deliver & Support

Recommended structure for the updated file:

# VS01 Hire to High Performer — Value Stream Stages
 
## Purpose
 
This document defines the stages that VS01 Hire to High Performer traverses through the
Value Stream Chain, showing which activities and management practices participate at each stage.
 
## Value Stream Chain Activity Mapping
 
| VS Stage     | Value Stream Chain Activity | Key Practices                       |
| ------------ | --------------------------- | ----------------------------------- |
| Onboarding   | Engage, Design & Transition | HR Management                       |
| Progression  | Deliver & Support, Improve  | HR Management, Strategy Mgmt  |
| Remuneration | Plan, Deliver & Support     | HR Management, Financial Mgmt |
 
## Value Stream Stages Diagram
 
[Preserve existing Mermaid diagram from current file, with heading updated]
 
## Stage Details
 
[Preserve existing stage sections: Stage 1 — Onboarding, Stage 2 — Progressing, Stage 3 — Remuneration]

4.2 VS02 Discovery to Deployment — New content:

Create a Mermaid diagram showing 5-6 stages typical for a sales-to-delivery value stream:

Include a Mermaid flowchart following the L1 Value Stream guide format established in content/_authoring/diagrams/mermaid/L1-value-stream-guide.md.

4.3 VS03 Request to Release — New content:

4.4 VS04 Incident to Resolution — New content:

4.5 Mermaid diagram template:

All VS stage diagrams should follow this general pattern (adapted per VS):

flowchart TD

subgraph LEGEND["**Legend**"]
    Policy@{ shape: braces }
    Process@{ shape: subproc }
    Procedure@{ shape: rounded }
    Guide@{ shape: comment }
    Template@{ shape: doc }
end

subgraph VS["`**[VS Name]**`"]
    direction LR

    subgraph S1["**Stage 1: [Name]**"]
        direction TB
        practice1["[Practice/Process]"]@{ shape: subproc }
    end

    subgraph S2["**Stage 2: [Name]**"]
        direction TB
        practice2["[Practice/Process]"]@{ shape: subproc }
    end

     ==> S3 ==> ...
end

VS ~~~ LEGEND

4.6 Frontmatter updates:

Update the frontmatter of each renamed file to reflect the new purpose:

---
publish: true
page-status: draft
created: 2026-02-11
updated: 2026-03-02
owner: [vs-team-slug]
vs-code: [VS##]
type: value-stream-stages
level: L1
---

Deliverable

All four 01 Value Stream Stages.md files populated with:

• Purpose section
• Value Stream Chain activity mapping table
• Mermaid stage diagram
• Stage detail sections

Verification

• All four files have complete content (no “XXX” or “[To be completed]” placeholders)
• VS01 preserves its existing Mermaid diagram content while adding the SVC mapping
• VS02-VS04 have new Mermaid diagrams following the L1 guide format
• All Mermaid diagrams render correctly (test via npx quartz build or Obsidian preview)
• Each diagram includes a legend subgraph
• Frontmatter type updated to value-stream-stages
• Practice references use valid Obsidian wikilink syntax

Step 5 — Update Operating Model and Value Stream Index

Tasks

5.1 Update content/00 Governance/02 Operating Model.md:

Add a new section referencing the Value Stream Chain. Insert after the “Value Streams” section (around line 91):

## Value Stream Chain
 
The Value Stream Chain defines six standard activity stages that Value Streams traverse to create value. For full definitions, see [[05 Value Stream Chain]].

5.2 Update content/01 Value Streams/README.md:

Add a paragraph to the “What are Value Streams?” section explaining how Value Streams relate to the Value Stream Chain:

### Relationship to the Value Stream Chain
 
Each Value Stream traverses a subset of the six [[05 Value Stream Chain|Value Stream Chain]] activity
stages (Plan, Improve, Engage, Design & Transition, Obtain | Build, Deliver & Support). The specific
stages each VS traverses are documented in its `01 Value Stream Stages` file.

Deliverable

Operating Model and Value Stream Index updated with Value Stream Chain references.

Verification

• Operating Model links to 05 Value Stream Chain via valid wikilink
• Value Stream Index explains the relationship to the Value Stream Chain
• No broken links introduced

Step 6 — Final Validation and Merge

Tasks

6.1 Repository-wide reference validation:

Run a comprehensive search to confirm:

# Should return zero results (excluding archive and this plan):
grep -r "01 Value Stream Map" --include="*.md" content/ .opencode/ .github/ | grep -v "99 Archive" | grep -v "11 ITILv4"
 
# Should return zero results:
grep -r "Value System Chain" --include="*.md" content/ | grep -v "99 Archive" | grep -v "11 ITILv4"

6.2 Link validation:

Verify all Obsidian wikilinks resolve:

• Links to 01 Value Stream Stages in all four VS READMEs
• Links to 05 Value Stream Chain in Operating Model and VS Index
• Practice links in the new governance document
• Cross-references in Decision 09

6.3 Build validation:

npx quartz build

Confirm no build errors related to the changes.

6.4 Commit and merge:

• Commit all changes to the feature branch with a descriptive message
• Create PR from feat/svc-activities to main
• Include this plan’s README as the PR description reference

Deliverable

All changes validated, committed, and ready for merge.

Verification

• Zero stale references to 01 Value Stream Map or Value System Chain in active content
• Quartz build succeeds without errors
• PR created with clean diff
• All new/modified files have valid frontmatter

4. Decision Points & Options

Decision 1 — Terminology Choice

Decision: Option C — Use “Value Stream Chain” with an explicit mapping table to ITILv4 terms.

Decision 2 — File Rename Scope

Decision: Option A — Rename to 01 Value Stream Stages.md. The one-time migration cost is justified by long-term clarity.

Decision 3 — SVC Definition Location

Decision: Option A — Company Governance owns cross-cutting methodology, consistent with the Operating Model being there.

Decision 4 — VS01 Existing Content Handling

Decision: Option A — Preserve VS01’s existing Mermaid diagram and add SVC activity mapping alongside it.

5. Risk Assessment

Rollback Plan:

If critical issues are discovered during implementation:

1. Do NOT merge the feature branch to main
2. Document issues found
3. Revise plan to address issues
4. Re-implement in a new feature branch
5. Main branch remains unchanged and the vault stays functional

6. Success Criteria

Implementation is successful when:

• Decision 09 created and documents all terminology and rename decisions
• 05 Value Stream Chain.md exists in Company Governance with all six activities fully defined (no empty placeholders)
• Terminology mapping table present showing Calab.ai terms vs ITILv4 equivalents
• All four VS folders contain 01 Value Stream Stages.md (renamed from 01 Value Stream Map.md)
• VS01 preserves existing Mermaid diagram and adds SVC activity mapping
• VS02-VS04 have new Mermaid diagrams showing Value Stream Chain activity stages
• Zero references to 01 Value Stream Map remain in active content (outside 99 Archive/ and this plan)
• Zero references to Value System Chain remain in active content (outside 99 Archive/ and this plan)
• All 14 reference files updated successfully
• Operating Model references the new Value Stream Chain document
• Value Stream Index explains the relationship to the Value Stream Chain
• Quartz build succeeds without errors related to these changes
• All Obsidian wikilinks resolve correctly (no broken links)

7. Appendices

A. Value Stream Chain Activity Reference

B. Complete File Change Manifest

Created (2 files)

Renamed (4 files)

Modified (16 files)

C. ITILv4 Service Value Chain — Source Reference

The six activities are directly adapted from the ITILv4 Service Value Chain as defined in ITIL Foundation: ITIL 4 Edition (AXELOS, 2019). Calab.ai’s definitions have been contextualised for a technology professional services and product organisation, with terminology adapted as documented in Decision 09.

The original archived definitions (with empty descriptions) are preserved at: content/99 Archive/Human Resources (deprecated 2026-02-11)/03 Operational Governance.md, lines 276-293.

D. Practice-to-Guild Quick Reference

For reference when populating practice links in the VS stage files: