diff --git a/registry/capabilities/capability.communication.markitect-legacy-platform.md b/registry/capabilities/capability.communication.markitect-legacy-platform.md new file mode 100644 index 00000000..f14caf17 --- /dev/null +++ b/registry/capabilities/capability.communication.markitect-legacy-platform.md @@ -0,0 +1,124 @@ +--- +id: capability.communication.markitect-legacy-platform +name: MarkiTect Legacy Platform +summary: Intelligent markdown engine and information-management platform treating documents as structured, + queryable information spaces with schema validation, transclusion, and LLM-driven evaluation; the legacy + umbrella now being split into markitect-tool, infospace-bench, and kontextual-engine. +owner: markitect-main +status: draft +domain: communication +tags: +- markitect +- markdown +- legacy +maturity: + discovery: + current: D3 + target: D3 + confidence: medium + rationale: INTRODUCTION.md and SCOPE.md describe a mature, broad platform (schema validation, transclusion, + LLM evaluation, infospace lifecycle); GUARDRAILS.md and DEPENDENCIES.md indicate an actively-managed + but legacy codebase now being superseded by successor repos (markitect-tool, infospace-bench, kontextual-engine + each reference a markitect-main-scope-assessment.md boundary doc). + availability: + current: A1 + target: A1 + confidence: medium + rationale: Extensive real application code (application/, domain/, services/ dirs) with both a Python + package and a package.json; availability target is intentionally capped at A1 since the successor + repos are the forward path, not this legacy platform. +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - broad legacy feature set (schema validation, transclusion, LLM evaluation) + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - actively being superseded by markitect-tool/infospace-bench/kontextual-engine; new consumers should + prefer the successors per each successor's own scope-assessment docs +discovery: + intent: Document the legacy MarkiTect platform honestly as a superseded predecessor, so planners route + new work to the successor repos rather than extending this one. + includes: + - legacy markdown engine, schema validation, transclusion, LLM-driven evaluation, infospace lifecycle + (as originally built) + excludes: + - new feature development (happens in markitect-tool, infospace-bench, kontextual-engine) + assumptions: [] + use_cases: [] + research_memos: [] +availability: + current_level: A1 + target_level: A1 + current_artifacts: + - legacy Python/Node application + target_artifacts: [] + consumption_modes: + - application (legacy, not recommended for new integration) +relations: + depends_on: [] + supports: [] + related_to: [] +evidence: + documentation: + - INTRODUCTION.md + - SCOPE.md + - GUARDRAILS.md + tests: + - tests/ + - pytest.ini + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - understanding the historical design this scope split from; not for new integrations + not_recommended_for: + - new consumers — use markitect-tool, infospace-bench, or kontextual-engine instead, per their own scope-assessment + docs + known_limitations: + - actively being split apart; treat as reference/legacy, not a forward-looking target +promotion_history: [] +--- + +# MarkiTect Legacy Platform + +## Overview + +`markitect-main` is the legacy MarkiTect umbrella platform — an intelligent markdown engine and information-management system. It is actively being split into successor repos (`markitect-tool` for syntax-layer tooling, `infospace-bench` for the application layer, `kontextual-engine` for the knowledge-operations runtime); this entry is registered mainly so planners can see it is superseded rather than accidentally building against it. + +## Assessment notes + +### Discovery + +INTRODUCTION.md and SCOPE.md describe a mature, broad platform (schema validation, transclusion, LLM evaluation, infospace lifecycle); GUARDRAILS.md and DEPENDENCIES.md indicate an actively-managed but legacy codebase now being superseded by successor repos (markitect-tool, infospace-bench, kontextual-engine each reference a markitect-main-scope-assessment.md boundary doc). + +### Availability + +Extensive real application code (application/, domain/, services/ dirs) with both a Python package and a package.json; availability target is intentionally capped at A1 since the successor repos are the forward path, not this legacy platform. + +### Completeness + +First-pass honest assessment from the REUSE-WP-0017 coverage campaign +(reuse-surface). No external consumer feedback exists yet; levels reflect +scope-vs-intent documentation quality, not internal code quality. + +### Reliability + +No production consumer telemetry exists yet; reliability level is +intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence. + +## Promotion checklist + +- [x] ID follows `capability..` pattern +- [x] Maturity enums match `specs/CapabilityMaturityStandard.md` +- [x] `external_evidence` is populated separately from `maturity` +- [ ] Relations reference valid capability IDs (none yet) +- [x] Index entry added in `registry/indexes/capabilities.yaml` diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index f944e472..5458b355 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,4 +1,20 @@ version: 1 -updated: '2026-06-16' +updated: '2026-07-06' domain: helix_forge -capabilities: [] +capabilities: +- id: capability.communication.markitect-legacy-platform + name: MarkiTect Legacy Platform + summary: Intelligent markdown engine and information-management platform treating documents as structured, + queryable information spaces with schema validation, transclusion, and LLM-driven evaluation; the + legacy umbrella now being split into markitect-tool, infospace-bench, and kontextual-engine. + vector: D3 / A1 / C1 / R0 + domain: communication + status: draft + owner: markitect-main + path: registry/capabilities/capability.communication.markitect-legacy-platform.md + tags: + - markitect + - markdown + - legacy + consumption_modes: + - application (legacy, not recommended for new integration)