Markitect boundary and reuse tests

workplans/KONT-WP-0005-asset-registry-governance-state.md

@@ -37,6 +37,14 @@ ports, policy port, audit port, and SQLite/in-memory adapters described in
 `docs/architecture-blueprint.md`. The asset registry must not depend on HTTP,
 source connectors, document extractors, search backends, or AI providers.
 
+## markitect-tool Boundary Remark
+
+The asset registry may persist Markitect snapshot IDs, parser metadata,
+frontmatter-derived metadata, selector references, and operation provenance as
+adapter metadata on representations or versions. It must not make Markitect
+document classes canonical engine entities, and asset identity must remain
+independent of Markitect snapshot identity.
+
 ## G5.1 - Implement stable asset identity and source references
 
 ```task
@@ -76,6 +84,8 @@ Acceptance:
 - Derived artifacts are stored as asset-linked records, not detached strings.
 - Representation metadata includes media type, digest, size, extractor or
   producer, and provenance.
+- Markdown representation metadata can include serialized Markitect snapshot
+  identity without coupling engine identity to it.
 
 ## G5.3 - Implement metadata classification lifecycle and schema validation