This commit completes Phase 2 of schema evolution work and establishes
a new example demonstrating schema usage for terminology documents.
## New Features
### Terminology Validation Example (examples/terminology/)
- Complete example terminology document with proper structure
- JSON schema with MarkiTect extensions for validation
- Demonstrates schema usage beyond manpages (glossaries, lexicons)
- Validates term structure: Definition, Synonyms, Related Terms, Examples
- Includes content control and quality validation rules
- Full documentation with usage examples and best practices
### Schema Registration System
- Registered terminology schema in markitect database
- Created schema catalog (markitect/schemas/schema-catalog.yaml)
- Copied schema to official location (markitect/schemas/)
- Provides metadata, features, and usage info for all schemas
### Improved schema-list Command
- Now displays creation timestamps in default output
- Table format includes Created/Updated columns
- Cleaner timestamp formatting (removed microseconds)
- Better visibility into when schemas were added
## Files Changed
Added:
- examples/terminology/README.md - Complete documentation
- examples/terminology/terminology-example.md - Example glossary
- examples/terminology/terminology-schema.json - Validation schema
- markitect/schemas/terminology-schema.json - Registered schema
- markitect/schemas/schema-catalog.yaml - Schema registry
Modified:
- markitect/cli.py - Enhanced schema-list with timestamps
- TODO.md - Documented Phase 2 completion and new example
Moved:
- SCHEMA_EVOLUTION_WORKPLAN.md → todo/ directory
## Schema Features Demonstrated
- Heading hierarchy validation (H1 → H2 → H3)
- Term structure validation with required/optional fields
- Content quality metrics (word counts, readability targets)
- MarkiTect extensions (x-markitect-sections, x-markitect-content-control)
- Classification system (required/recommended/optional/discouraged/improper)
## Usage
```bash
# List schemas with timestamps
markitect schema-list
# Validate terminology document
markitect validate glossary.md --schema terminology-schema.json
# View in table format
markitect schema-list --format table
```
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Created detailed gameplan for cost tracking and allocation system
- Designed database schema for financial data (costs, periods, transactions, allocations)
- Planned cost allocation algorithm with loss carried forward handling
- Created 9 implementation issues (#110-118) registered in system
- Organized by 3 phases: Foundation → Business Logic → User Features
- Includes CLI commands, reporting, and automation capabilities
Key Features:
- Track monthly/one-time costs with audit trail
- Allocate costs to active issues in calculation periods
- Financial reporting and trend analysis
- Automated period management and calculations
- Integration with existing issue management system
Implementation Timeline: 23 days (4.5 weeks)
Total Issues Created: 9 issues (#110-118)
Estimated Monthly Costs: €87 (server, SaaS, domains, tools)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Moved LLM_INTEGRATION_GAMEPLAN.md to history/ (strategic planning complete)
- Moved IMPLEMENTATION_ISSUES.md to history/ (issues created in system)
- Both documents served their purpose in planning and issue creation
- Issues #100-109 now registered in MarkiTect issue management system
- Ready for future development when LLM integration work begins
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Created detailed implementation strategy for OpenRoute integration (issue #98)
- Designed auto-fill templates system with LLM assistance (issue #99)
- Analyzed existing infrastructure and identified reusable components
- Provided 4-6 week phased development plan with clear priorities
- Included technical architecture, database schemas, and testing strategy
- Added risk assessment, success metrics, and requirements engineering guidance
- Recommended starting with OpenRoute client as shared foundation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
