# Markitect Main — intent

Markitect Main is the legacy integrated markdown and knowledge-artifact
platform. It preserves implementation history, examples, and evidence needed
to finish migration to the successor repositories.

The May 23 [successor gap assessment](docs/successor-gap-assessment.md) records
the retirement direction. Retirement is **not complete**: the disposition of
the render/asset stack, the older `markitect/spaces/` abstraction, and the
project-operations modules still needs explicit decisions. This document does
not authorize deleting those components or claim successor feature parity.

New core development belongs with the relevant successor:

| Repository | Responsibility |
| --- | --- |
| `markitect-tool` | Markdown syntax and structured-document primitives; adapter contracts |
| `kontextual-engine` | Headless knowledge operations, persistence, workflows, query and assessment |
| `infospace-bench` | Concrete infospaces, evaluation methodology and reference pilots |
| `markitect-filter` | Source-format ingestion adapters |
| `markitect-quarkdown` | Quarkdown rendering/export adapter |
| `testdrive-jsui` | Standalone JavaScript editor library and its package releases |

Work retained here is maintenance needed for existing consumers, evidence-based
migration and retirement decisions, and verification of Markitect's integration
with pinned dependencies. The current publication coordination is tracked in
[MARKITECT-WP-0002](workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md).
Package repair and publication belong to `testdrive-jsui`; Markitect view/edit
integration evidence belongs here.

Keep historical evidence and existing task identities intact. Prefer finishing
existing work over expanding the monolith. Scope changes and retirement require
an explicit decision rather than an inference from an old roadmap.