Enhanced usecase example weave tangle for later workflows

workplans/MKTT-WP-0003-core-toolkit-implementation.md

@@ -116,6 +116,10 @@ LLM-assisted hooks supplied by external providers.
 
 Extension point: `EP-MKTT-001`.
 
+Keep this slice focused on deterministic templates and generation hooks. Rich
+processors, named chunks, weave/tangle, namespaces, and content-class
+inheritance are captured in `MKTT-WP-0010` after this hook surface is clear.
+
 ## P3.7 - Add caching and incremental processing
 
 ```task

workplans/MKTT-WP-0006-cache-backend-architecture-core.md

@@ -12,8 +12,10 @@ depends_on_workplans:
   - MKTT-WP-0004
 depends_on_tasks:
   - MKTT-WP-0003-T005
+related_workplans:
+  - MKTT-WP-0010
 created: "2026-05-03"
-updated: "2026-05-03"
+updated: "2026-05-04"
 state_hub_workstream_id: "0c585f8a-5c7e-4c89-b785-5b0089180256"
 ---
 
@@ -31,6 +33,7 @@ Research and architecture are captured in:
 
 - `docs/research-lab-cache-backend-research.md`
 - `docs/cache-backend-architecture-blueprint.md`
+- `docs/content-reference-literate-workflow-research.md`
 
 ## Decision
 
@@ -38,6 +41,11 @@ Do not start this before the current deterministic transform/composition slice
 has enough shape to show what cache invalidation must preserve. Start it before
 WP-0003 P3.7 caching becomes implementation work.
 
+Keep the backend fabric open for `MKTT-WP-0010` content-unit identities,
+reference graphs, processor provenance, and weave/tangle source maps. Those
+features do not need to be implemented here, but the capability model should not
+make them awkward later.
+
 ## P6.1 - Define backend capability model
 
 ```task
@@ -70,6 +78,9 @@ state_hub_task_id: "5debc135-908a-47ed-ba15-564610970e38"
 Specify content-addressed document snapshots keyed by source content hash,
 parser version, parse options, and contract version where relevant.
 
+Include a placeholder for stable content-unit identities and dependency edges so
+references/chunks can be cached and invalidated later.
+
 ## P6.3 - Define backend interfaces
 
 ```task
@@ -82,6 +93,9 @@ state_hub_task_id: "a3e37112-1197-4f6f-8de8-7b3067ef060e"
 Add protocol classes for snapshot backends, index backends, query adapters,
 context package registries, and access policy gateways.
 
+Leave room for processor-result stores, reference graph adapters, and source-map
+or provenance adapters.
+
 ## P6.4 - Implement local backend registry
 
 ```task

workplans/MKTT-WP-0007-advanced-query-and-local-index-backend.md

@@ -10,8 +10,10 @@ planning_priority: P2
 planning_order: 60
 depends_on_workplans:
   - MKTT-WP-0006
+related_workplans:
+  - MKTT-WP-0010
 created: "2026-05-03"
-updated: "2026-05-03"
+updated: "2026-05-04"
 state_hub_workstream_id: "d61a82e4-651a-4df2-944a-9ff996b2e1f6"
 ---
 
@@ -22,6 +24,10 @@ state_hub_workstream_id: "d61a82e4-651a-4df2-944a-9ff996b2e1f6"
 Implement the first practical backend use case: cached AST introspection,
 JSONPath querying, SQLite metadata, and FTS5 search over Markdown documents.
 
+This backend should later be able to index `MKTT-WP-0010` references, named
+regions, chunks, and processor provenance without changing its basic storage
+contract.
+
 ## P7.1 - Implement local snapshot store
 
 ```task
@@ -77,6 +83,9 @@ state_hub_task_id: "479f11a3-4ab4-451b-991c-7f143f2bffea"
 Persist source files, content hashes, frontmatter, headings, sections, blocks,
 and metrics in SQLite.
 
+Keep schema extension points for reference edges, named regions, chunks, and
+processor outputs.
+
 ## P7.5 - Add FTS5 section/block search
 
 ```task
@@ -100,6 +109,8 @@ state_hub_task_id: "7d9472e6-0716-435b-866c-d2c66ad786cf"
 
 Refresh only changed files based on content hash and parser version.
 
+Include dependency invalidation hooks for future transclusion/reference graphs.
+
 ## P7.7 - Add local index CLI
 
 ```task

workplans/MKTT-WP-0010-content-reference-processor-literate-workflows.md

@@ -0,0 +1,170 @@
+---
+id: MKTT-WP-0010
+type: workplan
+title: "Content References, Processors, and Literate Workflows"
+domain: markitect
+status: todo
+owner: markitect-tool
+topic_slug: markitect
+planning_priority: P1
+planning_order: 55
+depends_on_workplans:
+  - MKTT-WP-0004
+depends_on_tasks:
+  - MKTT-WP-0003-T006
+informs_workplans:
+  - MKTT-WP-0006
+  - MKTT-WP-0007
+  - MKTT-WP-0008
+  - MKTT-WP-0009
+created: "2026-05-04"
+updated: "2026-05-04"
+state_hub_workstream_id: "7863fd01-0be0-4dbc-9941-0151365bb9e1"
+---
+
+# MKTT-WP-0010: Content References, Processors, and Literate Workflows
+
+## Purpose
+
+Build the richer framework layer for namespaced content references,
+processor-driven Markdown blocks, reversible explode/implode, and literate
+weave/tangle workflows.
+
+This preserves the important `markitect-main` ideas that were intentionally not
+pulled into the first transform/compose/include slice.
+
+## Background
+
+The first P3.5 implementation provides a clean deterministic kernel:
+frontmatter/body/heading transforms, file composition, and explicit include
+markers. That is better for the core toolkit than the old platform-heavy
+implementation, but it leaves out several valuable capabilities:
+
+- reversible explode/implode variants
+- named chunks and Knuth-style weave/tangle
+- scoped variables and conditional transclusion
+- stable namespaces and content references
+- processor semantics for fenced blocks
+- reference graphs, provenance, and source maps
+- deterministic multi-inheritance for content classes and overlays
+
+See `docs/content-reference-literate-workflow-research.md`.
+
+## P10.1 - Define reference address model and namespace rules
+
+```task
+id: MKTT-WP-0010-T001
+status: todo
+priority: high
+state_hub_task_id: "f70d2b9d-151b-46c6-9613-bd6bdbf164e7"
+```
+
+Define stable content-unit identities, namespace mappings, reference syntax,
+resolver inputs/outputs, and error cases.
+
+Output: reference model docs, examples, and tests for path, namespace, selector,
+and ID resolution.
+
+## P10.2 - Add token-safe transforms and operation provenance
+
+```task
+id: MKTT-WP-0010-T002
+status: todo
+priority: high
+state_hub_task_id: "e35639b7-756f-4993-8b3c-2e58b23e0eca"
+```
+
+Make transform/include behavior aware of fenced blocks and parser tokens. Add
+structured operation provenance, dependency edges, source spans, and diagnostics.
+
+Output: token-safe transform implementation and provenance result envelope.
+
+## P10.3 - Implement named regions and addressable block selectors
+
+```task
+id: MKTT-WP-0010-T003
+status: todo
+priority: high
+state_hub_task_id: "98cafe28-a364-48f1-ae55-cb47c71d9441"
+```
+
+Support named Markdown/source regions, section IDs, fenced block IDs, and region
+selection by ID/tag/line range where appropriate.
+
+Output: region parser/resolver, CLI examples, and source-snippet tests.
+
+## P10.4 - Reimplement reversible explode/implode variants
+
+```task
+id: MKTT-WP-0010-T004
+status: todo
+priority: high
+state_hub_task_id: "67f77aa1-a7ee-485c-891e-6ae7ecc52067"
+```
+
+Recreate the useful `markitect-main` explode/implode functionality with a slim
+variant interface and manifest-first reversibility.
+
+Initial variants: flat and hierarchical. Semantic variant can follow once the
+reference and processor model is stable.
+
+Output: `mkt explode`, `mkt implode`, manifest schema, roundtrip tests.
+
+## P10.5 - Define processor registry for fenced blocks
+
+```task
+id: MKTT-WP-0010-T005
+status: todo
+priority: high
+state_hub_task_id: "eb7cde08-8a73-4163-ac54-19a2bc7b5f88"
+```
+
+Create a deterministic processor API for fenced blocks and directives.
+Processors should receive content units, resolver access, context, and policy,
+and return generated content/files, diagnostics, dependencies, and provenance.
+
+Output: processor registry API, deterministic built-in processors, and tests.
+
+## P10.6 - Implement literate weave/tangle MVP
+
+```task
+id: MKTT-WP-0010-T006
+status: todo
+priority: high
+state_hub_task_id: "090fcc38-758b-4414-b941-40f217eb17ca"
+```
+
+Implement Markdown-native literate workflows: named code chunks, chunk
+references, target files, tangling, and woven documentation with chunk
+cross-references.
+
+Output: `mkt tangle`, `mkt weave`, chunk-reference diagnostics, examples.
+
+## P10.7 - Design content class composition and multi-inheritance
+
+```task
+id: MKTT-WP-0010-T007
+status: todo
+priority: medium
+state_hub_task_id: "220e6b27-2d7b-4c22-b5e8-304198ecfea8"
+```
+
+Define content classes, slots, merge policies, and deterministic
+multi-inheritance resolution. Use a C3-like linearization with clear conflict
+diagnostics.
+
+Output: architecture note, examples, and a small deterministic resolver spike.
+
+## P10.8 - Add migration examples from markitect-main
+
+```task
+id: MKTT-WP-0010-T008
+status: todo
+priority: high
+state_hub_task_id: "287637d3-1997-43b2-b97d-10587d565cec"
+```
+
+Translate the relevant old explode/implode, transclusion, and spaces reference
+graph tests into successor-style fixtures and examples.
+
+Output: migration test inventory, example documents, and parity notes.