Files
markitect-main/examples/supply-chain-vsm/schemas/won-mapping-schema-v1.0.md
tegwick 574bb11db6 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>
2026-02-23 00:08:51 +01:00

55 lines
1.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# WoN Mapping Schema v1.0
Every mapping from a supply chain entity to a Wealth of Nations concept
must contain the following sections.
## Required Sections
### H1 Heading
Format: `Supply Chain Entity → WoN Entity`
Example: `# Bullwhip Effect → Natural Price as Central Price`
### Supply Chain Entity
The supply chain entity being mapped (title case name).
### WoN Entity
The Wealth of Nations entity being mapped to. Must be an entity that
exists in the WoN infospace (see `artifacts/won-reference/core-entities.md`
for the curated reference set).
### Mapping Rationale
Minimum 40 words. Explain why this supply chain concept corresponds to
this WoN concept. Ground the mapping in both the supply chain definition
and Smith's original analysis. Do not rely on surface-level name similarity.
### Conceptual Continuity
One of: **Strong**, **Moderate**, **Weak**
- **Strong**: The modern concept directly instantiates the WoN concept —
same mechanism, different technology or scale
- **Moderate**: The modern concept resembles the WoN concept in structure
but differs in important ways
- **Weak**: The mapping is analogical — useful for analysis but not a
direct correspondence
### VSM Inheritance
Because the WoN entity is already mapped to a VSM system in the WoN
infospace, the supply chain entity inherits a VSM position by transitivity.
State: `[Supply Chain Entity] inherits [VSM System] via [WoN Entity]`
## Quality Metrics
- **Rationale Rigour** (15): Is the mapping justified by substantive
analysis, not just surface similarity?
- **Continuity Calibration** (15): Is the declared strength consistent
with the rationale?
- **VSM Coherence** (15): Does the inherited VSM assignment make sense
for the supply chain entity?