markitect-tool/docs/workplan-planning-map.md

Workplan Planning Map

Date: 2026-05-04

Purpose

This document captures the current sequencing and priority view for markitect-tool workplans.

State Hub currently supports workstream dependency edges, but it does not yet have native workstream priority/order fields and does not ingest dependency metadata from workplan frontmatter. Until that exists, this file and the workplan frontmatter are the repo source of truth; State Hub dependency edges and descriptions mirror the operational view.

Priority Scale

Priority	Meaning
P0	Current mainline work.
P1	Next enabling architecture or implementation work.
P2	High-value follow-on work, start when trigger conditions are met.
P3	Research-lab or security-sensitive extension work.
complete	Finished foundation or completed decision work.

Current Ordering

Workplan	Priority	Status	Depends On	Current View
MKTT-WP-0001	complete	done	none	Repository foundation is complete.
MKTT-WP-0002	complete	done	MKTT-WP-0001	Legacy scope extraction is complete.
MKTT-WP-0004	complete	done	MKTT-WP-0001, MKTT-WP-0002	Contract framework is complete and informs later validation/generation work.
MKTT-WP-0003	complete	done	MKTT-WP-0001, MKTT-WP-0002, MKTT-WP-0004	Core toolkit implementation is complete.
MKTT-WP-0006	P1	todo	MKTT-WP-0004; task-level trigger: MKTT-WP-0003-T005	Ready after transform/composition shape is clear; should account for future reference/provenance needs.
MKTT-WP-0010	P1	todo	MKTT-WP-0004; task-level trigger: MKTT-WP-0003-T006	Trigger is satisfied; keep as the richer content-reference, processor, explode/implode, and weave/tangle track.
MKTT-WP-0007	P2	todo	MKTT-WP-0006	First practical cache backend use case: AST/JSONPath/SQLite/FTS.
MKTT-WP-0005	P2	todo	MKTT-WP-0003, MKTT-WP-0004	Pick up when generation/form/context or semantic assessment pressure appears.
MKTT-WP-0011	P2	todo	MKTT-WP-0003; task-level triggers: MKTT-WP-0010-T001, MKTT-WP-0010-T005	Declarative Markdown dataflow workflows: source extraction, deterministic/assisted processing, and multi-output generation.
MKTT-WP-0009	P2	todo	MKTT-WP-0006	Establish access-control gateway before security-sensitive cache/context use.
MKTT-WP-0008	P3	todo	MKTT-WP-0006, MKTT-WP-0007, MKTT-WP-0009	Agent working-memory cache after backend and policy floor are available.

Dependency Notes

The first important nuance is MKTT-WP-0006: it should not wait for every task in MKTT-WP-0003, because it should shape cache architecture before P3.7. It should wait until MKTT-WP-0003-T005 gives transform/composition enough shape to know what cached identities and invalidation rules must preserve.

The second important nuance is MKTT-WP-0010: it captures richer content reference, processor, explode/implode, and weave/tangle work. Its task-level trigger MKTT-WP-0003-T006 is now satisfied. It should inform backend, index, context-memory, and access-control architecture before those become rigid.

These are mixed task/workstream dependencies. State Hub does not currently model them natively.

MKTT-WP-0011 captures the practical workflow layer that wires existing primitives together: Markdown sources, selectors, deterministic processors, optional assisted generation hooks, and multiple Markdown outputs. It should not block P3.7, but it should follow the first reference model and processor registry decisions in MKTT-WP-0010.

State Hub Mirror

Native State Hub dependency edges should mirror the whole-workstream dependencies:

• MKTT-WP-0002 -> MKTT-WP-0001
• MKTT-WP-0004 -> MKTT-WP-0001
• MKTT-WP-0004 -> MKTT-WP-0002
• MKTT-WP-0003 -> MKTT-WP-0001
• MKTT-WP-0003 -> MKTT-WP-0002
• MKTT-WP-0003 -> MKTT-WP-0004
• MKTT-WP-0006 -> MKTT-WP-0004
• MKTT-WP-0010 -> MKTT-WP-0004
• MKTT-WP-0007 -> MKTT-WP-0006
• MKTT-WP-0005 -> MKTT-WP-0003
• MKTT-WP-0005 -> MKTT-WP-0004
• MKTT-WP-0011 -> MKTT-WP-0003
• MKTT-WP-0009 -> MKTT-WP-0006
• MKTT-WP-0008 -> MKTT-WP-0006
• MKTT-WP-0008 -> MKTT-WP-0007
• MKTT-WP-0008 -> MKTT-WP-0009