Markitect boundary and reuse tests

workplans/KONT-WP-0004-knowledge-operations-architecture.md

@@ -33,10 +33,21 @@ workflow state, exportability, and agent-safe operation from the start.
 - Updated scope and roadmap documentation.
 - `docs/architecture-blueprint.md` as the architecture baseline for the V0.2
   implementation sequence.
+- `docs/markitect-tool-reuse-boundary.md` and
+  `docs/markitect-tool-integration-usecases.md` as the explicit boundary
+  between markdown syntax tooling and the engine runtime.
 - Architecture decision notes for the P0 capability baseline.
 - Traceability from PRD/FRS V0.2 requirements to implementation workplans.
 - Revised implementation sequence for `KONT-WP-0005` through `KONT-WP-0010`.
 
+## markitect-tool Boundary Remark
+
+The architecture work must treat `markitect-tool` as the Markdown-native syntax
+and operations dependency, not as a subsystem to copy into this repo.
+Architecture decisions should require adapter-only imports, public Markitect
+APIs, and integration contract tests for parser, selector, operation,
+snapshot, and context-package behavior.
+
 ## A4.1 - Reconcile implementation baseline with V0.2 vision
 
 ```task
@@ -192,6 +203,8 @@ Acceptance:
 - `docs/knowledge-operations-roadmap.md` maps PRD/FRS areas to workplans.
 - `docs/architecture-blueprint.md` defines the implementation shape and review
   checklist.
+- Markitect dependency boundaries and use cases are linked from roadmap and
+  scope materials where they affect implementation sequencing.
 - `README.md` points to the new research and roadmap materials.
 
 ## Definition Of Done