markitect-main/registry/capabilities/capability.communication.markitect-legacy-platform.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.communication.markitect-legacy-platform	MarkiTect Legacy Platform	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.	markitect-main	draft	communication	markitect markdown legacy	discovery availability current target confidence rationale D3 D3 medium 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). current target confidence rationale A1 A1 medium 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 reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations broad legacy feature set (schema validation, transclusion, LLM evaluation) level confidence basis known_reliability_risks R0 low consumer_quality_signals actively being superseded by markitect-tool/infospace-bench/kontextual-engine; new consumers should prefer the successors per each successor's own scope-assessment docs	intent includes excludes assumptions use_cases research_memos Document the legacy MarkiTect platform honestly as a superseded predecessor, so planners route new work to the successor repos rather than extending this one. legacy markdown engine, schema validation, transclusion, LLM-driven evaluation, infospace lifecycle (as originally built) new feature development (happens in markitect-tool, infospace-bench, kontextual-engine)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A1 legacy Python/Node application application (legacy, not recommended for new integration)	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents INTRODUCTION.md SCOPE.md GUARDRAILS.md tests/ pytest.ini	recommended_for not_recommended_for known_limitations understanding the historical design this scope split from; not for new integrations new consumers — use markitect-tool, infospace-bench, or kontextual-engine instead, per their own scope-assessment docs actively being split apart; treat as reference/legacy, not a forward-looking target

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

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml