This commit sets up the comprehensive workplan for implementing a
markdown-first schema management system with naming conventions,
versioning, and self-validation capabilities.
## Directory Reorganization
- Renamed `todo/` → `roadmap/` for better organization
- Created `roadmap/schema-of-schemas/` subdirectory
- Moved schema management planning artifacts to dedicated directory
## Planning Artifacts Created
### Workplan & Documentation
- **WORKPLAN.md** (19KB) - Comprehensive 6-phase implementation plan
- **SCHEMA_MANAGEMENT_PROPOSAL.md** - Full analysis with 4 options
- **SCHEMA_MANAGEMENT_SUMMARY.md** - Executive summary
- **README.md** - Quick reference guide
### Example Schema
- **examples/schemas/manpage-schema-v1.md** - Demonstrates markdown format
## Schema Management System Design
### Naming Convention
**Format:** `{domain}-schema-v{major}.{minor}.md`
**Examples:**
- `manpage-schema-v1.0.md`
- `terminology-schema-v1.0.md`
- `api-documentation-schema-v1.0.md`
### Markdown-First Format
Schemas will be markdown files with:
- YAML frontmatter for metadata
- Rich documentation sections
- Embedded JSON schema in code block
- Version history and examples
### Implementation Phases (8-10 days)
**Phase 0:** Planning & Setup ✅ (0.5 days) - COMPLETE
**Phase 1:** Filename Convention (1 day) - NEXT
**Phase 2:** Markdown Loader (2-3 days)
**Phase 3:** Schema-for-Schemas (2 days)
**Phase 4:** Schema Migration (1-2 days)
**Phase 5:** CLI & Documentation (1 day)
**Phase 6:** Testing & Validation (1 day)
### Goals
1. ✅ Establish naming convention
2. ⏳ Implement filename validation
3. ⏳ Create markdown schema loader
4. ⏳ Build schema-for-schemas metaschema
5. ⏳ Migrate 5 existing schemas (remove 2 duplicates)
6. ⏳ Update CLI and documentation
## Updated Tracking
### TODO.md
- Added Schema-of-Schemas as active work item
- Documented Phase 1 tasks and timeline
- Paused capability extraction work
### CHANGELOG.md
- Added schema management system to [Unreleased]
- Documented directory reorganization
- Added "In Progress" section for current work
## Next Steps
Begin Phase 1:
1. Implement schema_naming.py with validation
2. Add unit tests
3. Update CLI schema-ingest command
4. Create naming specification document
## Files Changed
- CHANGELOG.md - Added unreleased schema management features
- TODO.md - Updated active work tracking
- roadmap/ - Reorganized from todo/
- roadmap/schema-of-schemas/ - New planning directory
- examples/schemas/ - Example markdown schema
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
8.4 KiB
8.4 KiB
Manpage Schema v1.0
Schema ID: https://markitect.dev/schemas/manpage/v1
Version: 1.0.0
Status: Stable
Created: 2026-01-04
Document Types: Manual pages, CLI documentation
Overview
This schema validates Unix/Linux manual page documentation following standard conventions. Manual pages (man pages) are the traditional form of documentation for Unix commands and system calls.
Typical Structure
A well-formed manual page includes:
- NAME - Command name and one-line description
- SYNOPSIS - Command syntax showing all options
- DESCRIPTION - Detailed explanation of what the command does
- OPTIONS - Description of each command-line option
- EXAMPLES - Practical usage examples
- SEE ALSO - Related commands or documentation
Usage
Validate a Manpage
markitect validate mycommand.1.md --schema manpage-schema-v1
Generate Manpage Template
markitect generate-stub manpage-schema-v1.json --output newcommand.1.md
Refine Existing Schema
markitect schema-refine manpage-schema-v1.json --loosen-counts
Examples
Complete examples can be found in:
Validation Rules
Required Sections (Level 2 Headings)
NAME
- Classification: Required
- Content: Command name in bold followed by brief description
- Format:
**command** - one line description - Example:
**markitect** - validate and analyze markdown documents
SYNOPSIS
- Classification: Required
- Content: Command syntax with all options
- Min code blocks: 1
- Max paragraphs: 3
- Example:
markitect [OPTIONS] COMMAND [ARGS]
DESCRIPTION
- Classification: Required
- Content: Detailed explanation of the command
- Min paragraphs: 2
- Min words: 50
Recommended Sections
OPTIONS
- Classification: Recommended
- Content: Definition list or table of command-line options
- Format: Each option as
**--option** *type*followed by description
EXAMPLES
- Classification: Recommended
- Content: Practical usage examples with explanations
- Min code blocks: 1
- Benefit: Greatly improves documentation usability
Optional Sections
ENVIRONMENT
- Environment variables affecting command behavior
FILES
- Important files used or created by the command
EXIT STATUS
- Explanation of exit codes
BUGS
- Known issues or limitations
AUTHORS
- Command authors and contributors
SEE ALSO
- Related commands or documentation
Schema Definition
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://markitect.dev/schemas/manpage/v1",
"version": "1.0.0",
"title": "Unix Manual Page Schema",
"description": "Schema for validating Unix/Linux manual page documentation",
"type": "object",
"properties": {
"headings": {
"type": "object",
"properties": {
"level_1": {
"type": "array",
"description": "Document title (command name)",
"items": {
"type": "object",
"properties": {
"content": {
"type": "string",
"pattern": ".*"
}
}
},
"minItems": 1,
"maxItems": 1
},
"level_2": {
"type": "array",
"description": "Section headings",
"items": {
"type": "object",
"properties": {
"content": {
"type": "string",
"enum": [
"NAME",
"SYNOPSIS",
"DESCRIPTION",
"OPTIONS",
"EXAMPLES",
"ENVIRONMENT",
"FILES",
"EXIT STATUS",
"BUGS",
"AUTHORS",
"SEE ALSO"
]
}
}
},
"minItems": 3,
"maxItems": 20
}
},
"required": ["level_1", "level_2"]
},
"paragraphs": {
"type": "array",
"description": "Paragraph content",
"items": {
"type": "object",
"properties": {
"content": {
"type": "string",
"minLength": 1
}
}
},
"minItems": 3
},
"code_blocks": {
"type": "array",
"description": "Code examples and command syntax",
"items": {
"type": "object",
"properties": {
"language": {
"type": "string"
},
"content": {
"type": "string"
}
}
},
"minItems": 1
}
},
"required": ["headings", "paragraphs"],
"x-markitect-sections": {
"NAME": {
"classification": "required",
"heading_level": 2,
"content_instruction": "Command name in bold followed by brief description",
"pattern": "\\*\\*[a-z-]+\\*\\*.*",
"error_if_missing": "NAME section is required in all manual pages"
},
"SYNOPSIS": {
"classification": "required",
"heading_level": 2,
"content_instruction": "Command syntax showing all options and arguments",
"min_code_blocks": 1,
"error_if_missing": "SYNOPSIS section is required to show command usage"
},
"DESCRIPTION": {
"classification": "required",
"heading_level": 2,
"content_instruction": "Detailed explanation of what the command does and when to use it",
"min_paragraphs": 2,
"min_words": 50,
"error_if_missing": "DESCRIPTION section is required for detailed explanation"
},
"OPTIONS": {
"classification": "recommended",
"heading_level": 2,
"content_instruction": "Description of each command-line option with syntax and explanation",
"warning_if_missing": "OPTIONS section recommended for commands with options"
},
"EXAMPLES": {
"classification": "recommended",
"heading_level": 2,
"content_instruction": "Practical usage examples with explanations",
"min_code_blocks": 1,
"warning_if_missing": "EXAMPLES greatly improve documentation usability"
},
"ENVIRONMENT": {
"classification": "optional",
"heading_level": 2,
"content_instruction": "Environment variables that affect command behavior"
},
"FILES": {
"classification": "optional",
"heading_level": 2,
"content_instruction": "Important files used or created by the command"
},
"SEE ALSO": {
"classification": "optional",
"heading_level": 2,
"content_instruction": "Related commands or documentation references"
}
},
"x-markitect-content-control": {
"name_section": {
"required_pattern": "\\*\\*[a-z-]+\\*\\*",
"description": "Command name must be in bold",
"example": "**markitect** - validate and analyze markdown documents"
},
"synopsis_section": {
"min_code_blocks": 1,
"code_block_language": "bash",
"description": "Must include at least one code block showing command syntax"
},
"description_section": {
"min_paragraphs": 2,
"min_words": 50,
"description": "Detailed description with at least 50 words across 2+ paragraphs"
}
},
"x-markitect-metadata": {
"schema-type": "document-schema",
"domain": "manpage",
"document-types": ["manual-page", "man-page", "cli-documentation"],
"version": "1.0.0",
"author": "MarkiTect Project",
"created": "2026-01-04",
"updated": "2026-01-04",
"example": "examples/manpages/markdown-schema-validation.1.md",
"supersedes": null,
"superseded-by": null
}
}
Version History
v1.0.0 (2026-01-04)
- Initial stable release
- Validates standard manpage sections
- Classification system (required/recommended/optional)
- Content control for NAME, SYNOPSIS, DESCRIPTION
- MarkiTect extensions for improved validation
Future Enhancements
Planned for v2.0:
- Multi-language support (internationalization)
- Extended sections (DIAGNOSTICS, SECURITY, STANDARDS)
- Cross-reference validation
- Version-specific section variants (man1, man5, man8)
Contributing
To suggest improvements to this schema:
- Open an issue describing the enhancement
- Provide example documents demonstrating the need
- Propose specific schema changes
License
This schema is part of the MarkiTect project and follows the same license.