markitect-main/docs
tegwick d68e762612 feat: implement Phase 1 - Enhanced Schema Format with Classifications
Complete Phase 1 of Schema Evolution Workplan implementing flexible content
control and section classification system.

## New Features

### 1. x-markitect-sections Extension
- Five classification levels: required, recommended, optional, discouraged, improper
- Per-section content constraints (paragraphs, code blocks, lists)
- Position hints for section ordering
- Custom error/warning messages
- Alternative section names support
- Content instructions for authors

### 2. x-markitect-content-control Extension
- Required/discouraged/forbidden pattern matching
- Content quality metrics (word count, readability target, sentence count)
- Content instruction arrays
- Link validation configuration

### 3. Metaschema Validation
- Updated markitect-metaschema.json with complete validation rules
- Enhanced metaschema.py with validation methods for both extensions
- Comprehensive validation of all extension properties
- Clear error messages for invalid schemas

### 4. Documentation & Examples
- Complete specification in docs/specifications/schema-extensions-spec.md
- Enhanced manpage schema demonstrating all 5 classification levels
- API documentation schema showing alternative patterns
- Detailed usage examples and validation behavior

## Implementation Details

**Files Modified:**
- markitect/schemas/markitect-metaschema.json: Added extension definitions
- markitect/metaschema.py: Added _validate_sections() and _validate_content_control()

**Files Created:**
- docs/specifications/schema-extensions-spec.md: Complete specification (v1.0)
- examples/manpages/enhanced-manpage-schema.json: Demonstrates all classifications
- examples/manpages/api-documentation-schema.json: Shows API doc patterns

## Validation Behavior

**Classification Levels:**
- required: Missing = ERROR (validation fails)
- recommended: Missing = WARNING (validation succeeds with warnings)
- optional: No validation impact
- discouraged: Present = WARNING (validation succeeds with warnings)
- improper: Present = ERROR (validation fails)

## Next Steps

Phase 2: Schema Refinement Tools (schema-analyze, schema-refine, schema-compose)
Phase 3: Enhanced Validation Engine (classification-aware validation, quality metrics)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-04 21:02:51 +01:00
..
adr refactor: failed attempt at edit mode recovery and robustness implementation 2025-11-12 00:19:03 +01:00
api feat: complete Issue #151 - Phase 4: Integration and Documentation 2025-10-14 11:11:51 +02:00
architecture docs: add comprehensive capabilities architecture documentation 2025-12-16 00:15:57 +01:00
cost-analysis feat: complete Issue #151 - Phase 4: Integration and Documentation 2025-10-14 11:11:51 +02:00
development docs: reorganize markdown documentation into proper directory structure 2025-11-09 23:26:48 +01:00
integration feat: Integrate Requirements Engineering Agent and fix Issue #59 test failures 2025-10-02 00:45:06 +02:00
manuals feat: Complete test-fixing agent implementation and CLI consolidation 2025-10-03 01:48:03 +02:00
specifications feat: implement Phase 1 - Enhanced Schema Format with Classifications 2026-01-04 21:02:51 +01:00
user-guides feat: complete Issue #151 - Phase 4: Integration and Documentation 2025-10-14 11:11:51 +02:00
advanced_packaging.md feat: complete Issue #150 - Advanced Packaging Features (.mdz, .mdt) 2025-10-13 23:09:18 +02:00
agents feat: consolidate and optimize Claude Code agent ecosystem 2025-10-05 20:50:52 +02:00
ASSET_MANAGEMENT_USER_GUIDE.md feat: complete Issue #146 - Asset Management Implementation Milestone 2025-10-14 18:29:37 +02:00
CAPABILITIES_QUICK_REFERENCE.md docs: add comprehensive capabilities architecture documentation 2025-12-16 00:15:57 +01:00
CLI_TUTORIAL.md chore: history cleanup 2025-10-03 03:39:43 +02:00
DOCUMENT_NAVIGATOR_INTEGRATION.md docs: add DocumentNavigator development infrastructure and test suite 2025-11-10 19:41:18 +01:00
ERROR_HANDLING_STRATEGY.md refactor: failed attempt at edit mode recovery and robustness implementation 2025-11-12 00:19:03 +01:00
graphql_interface.md feat: implement GraphQL write interface with mutations (issue #10) 2025-10-03 16:48:03 +02:00
markitect.1 feat: Strategic pivot to CLI implementation with comprehensive foundation 2025-09-24 01:14:27 +02:00
md-explode-command.md feat: complete TDD8 implementation of markdown file explosion - Issue #138 2025-10-07 15:44:30 +02:00
PLUGIN_SYSTEM.md feat: complete asset deployment for plugin engines 2025-11-14 09:20:37 +01:00
README.md docs: add comprehensive capabilities architecture documentation 2025-12-16 00:15:57 +01:00
search.md feat: implement lightweight full text search plugin using SQLite FTS5 (issue #83) 2025-10-03 17:03:11 +02:00
WIDGET_PLUGIN_INFRASTRUCTURE_WORKPLAN.md docs: add DocumentNavigator development infrastructure and test suite 2025-11-10 19:41:18 +01:00
wishlist.md feat: implement feature wishlist system (issue #85) 2025-10-03 19:12:45 +02:00
workplan-testdrive-jsui-capability.md feat: complete testdrive-jsui capability extraction with full JavaScript test integration 2025-11-09 22:29:30 +01:00
WORKSPACE_AND_DATABASES.md docs: complete project documentation and task management cleanup 2025-11-10 14:34:54 +01:00

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

For Users

For Developers

Project Management

Key Concepts

Core Architecture Principles

  1. Parse Once, Use Many Times - AST caching for 60-85% performance improvement
  2. Convention Over Configuration - Sensible defaults with minimal setup
  3. Schema-Driven Processing - Structured markdown with validation
  4. 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:

  1. Clear Structure - Logical organization and navigation
  2. Practical Examples - Real-world usage patterns
  3. Performance Context - Why architectural decisions matter
  4. 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.