markitect-tool/docs/markitect-main-wp0010-migration-notes.md

markitect-main WP-0010 Migration Notes

Date: 2026-05-04

Purpose

This note captures the relevant markitect-main ideas that WP-0010 now preserves in successor form.

The migration is conceptual rather than source-compatible. The successor keeps Markdown-native behavior and removes old platform, database, infospace, and service assumptions.

Parity Map

Legacy area	Successor shape	Status
Explode/implode variants	mkt explode, mkt implode, manifest-first flat/hierarchical variants	Reimplemented
Transclusion/includes	mkt include for path markers; processor mkt-include for reference-backed content	Reimplemented with clearer boundaries
Spaces/infospace references	Frontmatter namespaces plus mkt ref resolve	Reframed as syntax-layer references
Fenced-block processors	Explicit deterministic processor registry	Reimplemented as opt-in extension
Literate workflows	mkt tangle, mkt weave, named fenced chunks, noweb references	Reimplemented as MVP
Content classes/overlays	Data-defined classes with C3-style linearization and merge policies	Resolver spike implemented

Intentionally Not Migrated

These old concerns stay out of the WP-0010 toolkit layer:

• database-backed infospace lifecycle
• GraphQL/service APIs
• provider-specific LLM execution
• rendering/plugin/browser/editor infrastructure
• project finance, wishlist, and profile tooling

Migration Examples

Examples live under examples/migration/:

• legacy-explode-source.md: large document roundtrip via explode/implode.
• legacy-transclusion-context.md: namespace-backed reference include.
• legacy-path-include.md: simple path-based include marker.
• legacy-literate.md: named chunks tangled into source.

The tests in tests/test_wp0010_migration_examples.py exercise these files as successor fixtures. They are deliberately small, but they lock down the behaviors we most wanted to keep from markitect-main.