tegwick
4ce856d4d0
Add METRICS-METHODOLOGY.md documenting the theoretical frameworks (SEQUAL, OntoClean, OOPS!, OntoQA, FCA, DSL principles) adapted for two-layer evaluation (LLM-Eval + deterministic aggregation) across five collection concerns: redundancy, coverage, coherence, consistency, and granularity balance. Extend INFRA-TASKS.md with assignment assessment (tasks 4-7), per-concept metrics (tasks 8-12), and collection-level metrics (tasks 13-19). Add roadmap/infospace-tooling/PLAN.md defining terminology (infospace, topic, discipline, entity, evaluation, viability) and a three-stage implementation plan: Stage 1 platform additions, Stage 2 infospace tooling layer, Stage 3 example revision. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
MarkiTect Project Roadmap
This roadmap directory contains planning directories for roadmap topics.
- When starting to implement a topic its directory will be timestamped
- If implementing multiple topics in parallel use branches
- Keep current state of what's next to implement in TODO.md
- See ../history directory for closed topics
Naming Convention
Directory Format: yymmdd-topic-name
- Use 2-digit year prefix (e.g.,
260106-for 2026-01-06) - Lowercase topic names with hyphens
- Examples:
260106-semantic-document-validation,260105-schema-evolution
This convention keeps names concise while maintaining chronological sorting.
Purpose
This planning documentation serves multiple purposes:
- Implementation State Awareness: Allow for recovery after breaks or breakdowns
- Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
- Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
- Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized
xxx