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` | complete | done | `MKTT-WP-0004`; task-level trigger: `MKTT-WP-0003-T005` | Optional backend fabric is complete: manifests, capabilities, snapshot identity, interfaces, registry, provenance, and read-only CLI scaffolding. |
| `MKTT-WP-0010` | complete | done | `MKTT-WP-0004`; task-level trigger: `MKTT-WP-0003-T006` | Content references, processors, explode/implode, weave/tangle, content classes, and migration examples are complete as the first WP-0010 extension layer. |
| `MKTT-WP-0007` | complete | done | `MKTT-WP-0006` | Advanced query and local index backend is complete: AST inspection, optional JSONPath, SQLite snapshots/metadata, FTS5 search, incremental refresh, and local index CLI. |
| `MKTT-WP-0013` | complete | done | `MKTT-WP-0003`, `MKTT-WP-0004`, `MKTT-WP-0006`, `MKTT-WP-0007`, `MKTT-WP-0010` | Internal extension framework is complete: characterization tests, canonical processing model, descriptors, registries, lifecycle callbacks, query-engine registry, built-in extension catalog, CLI command specs, and authoring guide. |
| `MKTT-WP-0005` | complete | done | `MKTT-WP-0003`, `MKTT-WP-0004` | Runtime context, form state, dynamic rules, workflow integration, and provider-neutral assessment boundary are complete. |
| `MKTT-WP-0011` | complete | done | `MKTT-WP-0003`; task-level triggers: `MKTT-WP-0010-T001`, `MKTT-WP-0010-T005` | Markdown dataflow workflow layer is complete: workflow standard, source collectors, binding model, deterministic steps, assisted boundary, safe outputs, CLI, docs, and examples. |
| `MKTT-WP-0009` | complete | done | `MKTT-WP-0006` | Access-controlled knowledge gateway is complete: local labels, trust zones, path rules, policy-aware cache query/search, decisions, diagnostics, and external adapter boundaries. |
| `MKTT-WP-0012` | P3 | todo | `MKTT-WP-0004`, `MKTT-WP-0010`, `MKTT-WP-0011` | Future Quarkdown-inspired document function layer: reusable Markdown-native function calls over processors, references, contracts, workflows, and later assisted steps. |
| `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`.

`MKTT-WP-0013` captures internal extensibility pressure found while adding
optional query, backend, processor, and index features. It should precede major
runtime/workflow expansion because it reduces central wiring and gives future
features a canonical processing context/result/diagnostic/provenance model. It
is not a business dataflow layer; that remains `MKTT-WP-0011`.

`MKTT-WP-0012` captures the Quarkdown-inspired document function layer. It
should follow `MKTT-WP-0011` because the workflow layer will reveal which
operations deserve author-facing function syntax. It should remain optional and
capability-gated, especially before assisted, external, file, or network
functions are allowed.

## 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-0013 -> MKTT-WP-0003`
- `MKTT-WP-0013 -> MKTT-WP-0004`
- `MKTT-WP-0013 -> MKTT-WP-0006`
- `MKTT-WP-0013 -> MKTT-WP-0007`
- `MKTT-WP-0013 -> MKTT-WP-0010`
- `MKTT-WP-0012 -> MKTT-WP-0004`
- `MKTT-WP-0012 -> MKTT-WP-0010`
- `MKTT-WP-0012 -> MKTT-WP-0011`
- `MKTT-WP-0008 -> MKTT-WP-0006`
- `MKTT-WP-0008 -> MKTT-WP-0007`
- `MKTT-WP-0008 -> MKTT-WP-0009`