Workplan for dataflow pipeline workflows

docs/workplan-planning-map.md

@@ -35,6 +35,7 @@ and descriptions mirror the operational view.
 | `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. |
 
@@ -53,6 +54,12 @@ 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
@@ -69,6 +76,7 @@ dependencies:
 - `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`