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>
55 lines
1.1 KiB
Markdown
55 lines
1.1 KiB
Markdown
# Map Supply Chain Entities to Wealth of Nations Concepts
|
|
|
|
You are analysing modern supply chain management through the lens of
|
|
Adam Smith's Wealth of Nations. For each supply chain entity, produce a
|
|
structured mapping to the most relevant WoN concept.
|
|
|
|
## Supply Chain Entities
|
|
|
|
@{entities}
|
|
|
|
## WoN Reference Entities
|
|
|
|
@{won_core_entities}
|
|
|
|
## Mapping Guidelines
|
|
|
|
@{mapping_rules}
|
|
|
|
## Output Format
|
|
|
|
For each supply chain entity, produce a mapping using the following
|
|
delimiter format:
|
|
|
|
```
|
|
--- MAPPING: Supply Chain Entity → WoN Entity ---
|
|
|
|
# Supply Chain Entity → WoN Entity
|
|
|
|
## Supply Chain Entity
|
|
|
|
[Entity name]
|
|
|
|
## WoN Entity
|
|
|
|
[WoN entity name from the reference set]
|
|
|
|
## Mapping Rationale
|
|
|
|
[Minimum 40 words explaining the structural correspondence]
|
|
|
|
## Conceptual Continuity
|
|
|
|
[Strong | Moderate | Weak]
|
|
|
|
## VSM Inheritance
|
|
|
|
[Supply Chain Entity] inherits [VSM System] via [WoN Entity]
|
|
|
|
---
|
|
```
|
|
|
|
Produce one mapping per supply chain entity. Where an entity has no
|
|
plausible WoN mapping, produce a mapping entry with WoN Entity: "No
|
|
direct analogue" and explain what is structurally novel.
|