feat(example): add supply-chain-vsm composition demo (S3.5)

Demonstrates infospace composition: the Wealth of Nations infospace is
used as a discipline, applying Smith's economic framework as a lens to
analyse modern supply chain management concepts.

New example: examples/supply-chain-vsm/
- infospace.yaml binding WoN as discipline (../infospace-with-history)
- 3 source documents: coordination mechanisms, capital & inventory,
  market structure (~400 words each, original content)
- supply-chain-entity-schema-v1.0.md with WoN Concept required section
- won-mapping-schema-v1.0.md with Conceptual Continuity rating
- artifacts/won-reference/core-entities.md — 12 curated WoN entities
  for injection as discipline context
- 8 hand-crafted entity files demonstrating LLM output format
- 3 mapping files with full rationale and VSM inheritance chains
- Viable: YES (5/5 thresholds)

Key mappings demonstrated:
  Demand Signal          → Effectual Demand        (Strong, S2)
  Vendor-Managed Inventory → Division of Labour    (Strong, S1/S2)
  Just-in-Time Inventory → Circulating Capital     (Strong, S1/S3)
  Bullwhip Effect        → Natural Price           (Moderate, S2)
  Platform Intermediary  → Merchant Capital        (Strong, S2/S4)
  Monopsony Power        → Combination of Masters  (Strong, S3*)

Platform fix: entity_parser.py now recognises ## Supply Chain Domain
as a domain alias for ## Economic Domain, enabling composed infospaces
to use their own domain section name.

Tutorial §13 rewritten with real commands, real output, and the full
mapping table from the demo.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

examples/infospace-with-history/TUTORIAL.md

@@ -613,31 +613,109 @@ that are sparse in earlier books, then recovers as the matrix fills in.
 ## 13. Using the Infospace as a Discipline
 
 A completed, viable infospace can itself become a **discipline** — a lens
-applied to a new topic. For example, the Wealth of Nations infospace could
-be applied to analyse a modern supply chain.
+applied to a new topic. The working example is in
+`examples/supply-chain-vsm/`: it binds this WoN infospace as a discipline
+and applies Smith's framework to modern supply chain management.
+
+### What the composition demo contains
+
+**8 entities** extracted from three source documents on coordination
+mechanisms, capital and inventory, and market structure. Each entity
+maps to a specific WoN concept with a rationale and conceptual continuity
+rating (Strong / Moderate / Weak):
+
+| Supply Chain Entity | WoN Concept | Strength | VSM |
+|---|---|---|---|
+| Demand Signal | Effectual Demand | Strong | S2 |
+| Vendor-Managed Inventory | Division of Labour | Strong | S1/S2 |
+| Just-in-Time Inventory | Circulating Capital | Strong | S1/S3 |
+| Bullwhip Effect | Natural Price as Central Price | Moderate | S2 |
+| Safety Stock | Accumulation of Stock | Moderate | S3 |
+| Platform Intermediary | Merchant Capital | Strong | S2/S4 |
+| Monopsony Power | Combination of Masters | Strong | S3* |
+| Single-Source Dependency | Monopoly in Trade | Moderate | S4/S5 |
+
+Because WoN entities are already mapped to VSM systems, supply chain
+entities **inherit VSM positions by transitivity** — the supply chain
+infospace gets VSM coverage without needing its own VSM reference.
+
+### Running the composition demo
 
 ```bash
-# In a new infospace directory:
+cd examples/supply-chain-vsm
+
+# Check bound disciplines and their viability:
+markitect infospace disciplines
+```
+
+```
+Name                           Entities   Viable Path
+----------------------------------------------------------------------
+Wealth of Nations                   988      YES ../infospace-with-history
+```
+
+```bash
+# Show infospace status:
+markitect infospace status
+```
+
+```
+Infospace: Modern Supply Chain Management
+Domain:    Operations Management
+Entities:  8
+Disciplines: Wealth of Nations
+```
+
+```bash
+# Run checks and review viability:
+markitect infospace check
+markitect infospace viability
+```
+
+```
+Metric                            Value       Threshold   Status
+---------------------------------------------------------------
+redundancy_ratio                 0.0000         max=0.1     PASS
+coverage_ratio                   1.0000         min=0.5     PASS
+coherence_components             0.0000           max=2     PASS
+consistency_cycles               0.0000           max=0     PASS
+granularity_entropy              1.9056         min=0.8     PASS
+
+Viable: YES (5/5 thresholds met)
+```
+
+### Setting up your own composed infospace
+
+```bash
+mkdir my-new-topic/ && cd my-new-topic/
+
 markitect infospace init \
-  --topic "Modern Supply Chain Management" \
-  --domain "Operations Research" \
-  --discipline "Wealth of Nations"
+  --topic "My Topic" \
+  --domain "My Domain"
 
 # Bind the WoN infospace as a discipline:
-markitect infospace bind-discipline ../infospace-with-history
+markitect infospace bind-discipline --name "Wealth of Nations" \
+  ../infospace-with-history
 
-# List bound disciplines and their viability:
+# Confirm it is viable before using:
 markitect infospace disciplines
-# Viable System Model    PASS (from vsm-reference/)
-# Wealth of Nations      PASS (from ../infospace-with-history)
-
-# Check for stale mappings after discipline update:
-markitect infospace stale-mappings
 ```
 
 The discipline infospace must be viable (meeting its own thresholds)
 before it can be used as a lens. If the discipline's entities change,
-dependent mappings are flagged for re-evaluation.
+use `markitect infospace stale-mappings` to identify mappings that need
+re-evaluation.
+
+### The WoN core entity reference
+
+Rather than injecting all 988 WoN entities into every prompt (which
+would overflow context), the supply chain demo uses a curated reference
+file at `artifacts/won-reference/core-entities.md` — 12 key WoN entities
+selected for their relevance to operations and market structure. The
+pipeline stage macro `@{won_core_entities}` injects this file.
+
+For a different topic, create an equivalent curated reference of the
+WoN entities most relevant to your domain.
 
 ---