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>
MarkiTect Documentation
Welcome to the MarkiTect documentation. This directory contains comprehensive documentation for developers, users, and contributors.
Documentation Structure
📐 Architecture Documentation (architecture/)
Deep technical documentation about system design, performance, and implementation details.
- Capabilities Architecture - Critical: How capabilities work as independent git submodules and separation of concerns
- Caching System - Why and how MarkiTect's AST caching delivers 60-85% performance improvements
- Coming soon: Database Schema, CLI Architecture
👥 User Guides (user-guides/)
End-user documentation for working with MarkiTect CLI and features.
- Coming soon: Getting Started, Command Reference, Best Practices
🔧 Development Documentation (development/)
Documentation for contributors and developers extending MarkiTect.
- Coming soon: Contributing Guide, Testing Strategy, Release Process
Quick Links
For Users
- Installation & Setup
- Command Reference (coming soon)
- Performance Guide (coming soon)
For Developers
- Architecture Overview - System design and component relationships
- Development Setup - Local development environment
- API Documentation (coming soon)
Project Management
- Project Status - Current development status
- Roadmap - Strategic development plan
- Current Tasks - Task management using Keep a Todofile format
Key Concepts
Core Architecture Principles
- Parse Once, Use Many Times - AST caching for 60-85% performance improvement
- Convention Over Configuration - Sensible defaults with minimal setup
- Schema-Driven Processing - Structured markdown with validation
- Relational Metadata - Database-powered document relationships
Performance Philosophy
MarkiTect treats markdown documents as structured, queryable data rather than plain text. This approach enables:
- Lightning-fast document processing through intelligent caching
- Complex querying and relationship management
- Schema validation and consistency enforcement
- Scalable performance that grows with your content
Contributing to Documentation
Documentation follows the same quality standards as code:
- Clear Structure - Logical organization and navigation
- Practical Examples - Real-world usage patterns
- Performance Context - Why architectural decisions matter
- User-Focused - Written for the intended audience
Documentation Standards
- Use clear, concise language
- Include practical examples
- Explain the "why" behind design decisions
- Keep technical accuracy as the highest priority
- Update docs when changing functionality
This documentation is maintained alongside the codebase. For the most current information, always refer to the latest version in the repository.