# Markitect Main

Legacy Python markdown and knowledge-artifact platform, with a JavaScript
editor integration. The repository is transitioning to successor repositories;
it has not been fully retired. Start with [INTENT.md](INTENT.md) for current
responsibilities and the successor map.

## Current work

- [Publication coordination](workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md)
  is blocked on TestDrive package and release evidence plus Markitect integration
  verification. Its readiness definition and repository-structure decision are
  complete. The remaining tasks retain their original State Hub identities.
- [Successor gap assessment](docs/successor-gap-assessment.md) identifies pending
  decisions about rendering/assets, the older spaces abstraction, and
  project-operations code. It is an assessment, not permission to remove code.
- [WORK-RECORDS.md](WORK-RECORDS.md) is the generated task index;
  [workplans/](workplans/) contains the authoritative task records.

## Working with the legacy code

The [Makefile](Makefile) defines `make setup`, `make test`, `make lint`, and
`make build`; `make help` lists the available commands. These describe the
legacy workflow, not a claim that the full suite passes in a fresh checkout.

Capabilities are Git submodules. Inspect `git submodule status` before using
capability targets. The TestDrive submodule was uninitialized during the
September 28 review, so `make testdrive-jsui-test-all` was unavailable. Its
legacy URL in [.gitmodules](.gitmodules) may need a local override to the
current forge before initialization. Verify the pinned commit and dependency
setup before running the integration checks. Do not publish the root npm
package as the TestDrive library.

See [AGENTS.md](AGENTS.md) for repository and State Hub procedures,
[INTRODUCTION.md](INTRODUCTION.md) for historical product concepts, and
[SCOPE.md](SCOPE.md) for the legacy capability inventory.