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>
This commit is contained in:
@@ -0,0 +1,59 @@
|
||||
# Supply Chain Entity Schema v1.0
|
||||
|
||||
Every extracted entity must contain the following sections in this order.
|
||||
|
||||
## Required Sections
|
||||
|
||||
### H1 Heading
|
||||
|
||||
The entity name in title case. Should be a noun phrase identifying a
|
||||
distinct concept, mechanism, or structure in supply chain management.
|
||||
|
||||
Example: `# Bullwhip Effect`
|
||||
|
||||
### Definition
|
||||
|
||||
20–150 words. Precise, non-circular definition of the concept. Must
|
||||
identify what it is, not just what it does. Avoid defining a term
|
||||
using the term itself.
|
||||
|
||||
### Source
|
||||
|
||||
The source document this entity was extracted from, citing section
|
||||
if available. Format: `[Source Name], [Section]`
|
||||
|
||||
### Supply Chain Domain
|
||||
|
||||
One of: **Coordination**, **Capital Management**, **Market Structure**,
|
||||
**Risk**, **Logistics**
|
||||
|
||||
### VSM Assignment
|
||||
|
||||
One of: S1, S2, S3, S3*, S4, S5 — which layer of the Viable System Model
|
||||
this entity primarily inhabits. Brief rationale (one sentence).
|
||||
|
||||
### WoN Concept
|
||||
|
||||
The Wealth of Nations concept this entity most directly corresponds to.
|
||||
State the WoN entity name and a one-sentence explanation of the connection.
|
||||
If no direct correspondence exists, state "No direct WoN analogue" and
|
||||
explain why.
|
||||
|
||||
## Optional Sections
|
||||
|
||||
### Modern Context
|
||||
|
||||
Additional notes on how the concept has evolved since Smith's time, or
|
||||
how it differs from its classical form.
|
||||
|
||||
## Quality Metrics
|
||||
|
||||
Evaluation rubric for per-entity LLM assessment:
|
||||
|
||||
- **Definition Precision** (1–5): Is the definition specific, non-circular,
|
||||
and distinguishable from adjacent concepts?
|
||||
- **Source Grounding** (1–5): Is the entity grounded in the source material?
|
||||
- **Domain Placement** (1–5): Is the supply chain domain assignment correct?
|
||||
- **WoN Relevance** (1–5): Is the WoN mapping substantive and well-reasoned?
|
||||
- **Explanatory Value** (1–5): Does this entity contribute to understanding
|
||||
modern supply chains through the WoN lens?
|
||||
54
examples/supply-chain-vsm/schemas/won-mapping-schema-v1.0.md
Normal file
54
examples/supply-chain-vsm/schemas/won-mapping-schema-v1.0.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# 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** (1–5): Is the mapping justified by substantive
|
||||
analysis, not just surface similarity?
|
||||
- **Continuity Calibration** (1–5): Is the declared strength consistent
|
||||
with the rationale?
|
||||
- **VSM Coherence** (1–5): Does the inherited VSM assignment make sense
|
||||
for the supply chain entity?
|
||||
Reference in New Issue
Block a user