memory graph and services

examples/memory/decision-graph.yaml

@@ -0,0 +1,46 @@
+schema_version: markitect.memory.graph.v1
+id: markitect-memory-decisions
+title: Markitect Memory Decisions
+intent: Preserve the decisions that keep memory graphs inside the contract layer.
+namespace:
+  project: markitect-tool
+  task: MKTT-WP-0016
+nodes:
+  - id: decision.contract-boundary
+    kind: decision
+    text: Markitect validates memory profiles and graph snapshots, then compiles selected graph nodes into context packages.
+    source_spans:
+      - path: workplans/MKTT-WP-0016-agentic-memory-graphs-and-service-blueprints.md
+        unit_kind: section
+        selector: tasks[id=P16.5]
+        engine: selector
+    metadata:
+      title: Contract boundary decision
+      summary: Markitect remains the deterministic contract and compiler layer.
+  - id: constraint.no-runtime-services
+    kind: constraint
+    text: Runtime storage, retrieval, refresh, and compaction belong in kontextual-engine, not markitect-tool.
+    metadata:
+      title: Runtime ownership constraint
+  - id: finding.bench-handoff
+    kind: finding
+    text: infospace-bench should measure package quality, retrieval latency, budget pressure, and regressions using the same graph/profile fixtures.
+    metadata:
+      title: Benchmark handoff
+edges:
+  - id: edge.boundary-to-runtime
+    kind: supports
+    source: constraint.no-runtime-services
+    target: decision.contract-boundary
+  - id: edge.boundary-to-bench
+    kind: references
+    source: decision.contract-boundary
+    target: finding.bench-handoff
+events:
+  - id: event.initial-contract
+    kind: recorded
+    timestamp: "2026-05-15T00:00:00Z"
+    task: MKTT-WP-0016
+    node_updates:
+      - node_id: decision.contract-boundary
+        operation: create