tegwick
574bb11db6
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>
51 lines
2.0 KiB
Markdown
51 lines
2.0 KiB
Markdown
# Entity Extraction Rules — Supply Chain Infospace
|
||
|
||
## What Constitutes an Entity
|
||
|
||
Extract a concept as an entity when it is:
|
||
|
||
1. **Named**: referred to by a consistent, recognisable label in the
|
||
source material
|
||
2. **Distinct**: meaningfully different from other entities being extracted
|
||
3. **Explanatory**: contributes to understanding how supply chains work,
|
||
fail, or could be improved
|
||
4. **Mappable**: has a plausible correspondence to at least one concept in
|
||
the Wealth of Nations reference set
|
||
|
||
Do NOT extract:
|
||
- Proper nouns for specific companies or products (Toyota, Amazon) unless
|
||
they name a concept (e.g., the Toyota Production System is a concept)
|
||
- Historical examples unless the example itself is the concept
|
||
- Vague modifiers (e.g., "lean", "agile" as standalone adjectives)
|
||
|
||
## Granularity Rules
|
||
|
||
Target 4–8 entities per source document. Avoid:
|
||
- Entities so broad they subsume multiple distinct mechanisms (split them)
|
||
- Entities so narrow they are examples of a broader concept (elevate them)
|
||
- Entities that restate the same concept with different words (merge them)
|
||
|
||
## Naming Conventions
|
||
|
||
- Title case: `Bullwhip Effect`, not `bullwhip effect`
|
||
- Noun phrases: `Supply Chain Visibility`, not `supply chain is visible`
|
||
- Avoid acronyms in titles: `Just-in-Time Inventory`, not `JIT Inventory`
|
||
|
||
## WoN Cross-Reference
|
||
|
||
For each entity, consult the WoN core entity reference
|
||
(`artifacts/won-reference/core-entities.md`) to identify the most relevant
|
||
Wealth of Nations concept. Every entity should have a WoN Concept section —
|
||
even if the mapping is weak, noting the absence of a direct analogue is
|
||
informative.
|
||
|
||
## Supply Chain Domain Assignment
|
||
|
||
Assign the supply chain domain that best characterises the entity:
|
||
|
||
- **Coordination**: mechanisms that synchronise activity across chain nodes
|
||
- **Capital Management**: decisions about how working capital is deployed
|
||
- **Market Structure**: competitive arrangements, power relations, platform dynamics
|
||
- **Risk**: disruption, fragility, resilience
|
||
- **Logistics**: physical movement, warehousing, last-mile
|