memory graph and services

This commit is contained in:
2026-05-15 01:35:58 +02:00
parent 8f732fc868
commit 9d31dcf2af
11 changed files with 1665 additions and 9 deletions

View File

@@ -0,0 +1,19 @@
schema_version: markitect.memory.selection.v1
graph: decision-graph.yaml
profile: memory-profile.local.yaml
title: Memory Contract Boundary Package
intent: Activate the core contract/runtime boundary decisions for implementation work.
namespace:
project: markitect-tool
task: MKTT-WP-0016
node_ids:
- decision.contract-boundary
- constraint.no-runtime-services
- finding.bench-handoff
event_ids:
- event.initial-contract
budget:
max_items: 4
max_tokens: 1200
metadata:
purpose: implementation-context

View File

@@ -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

View File

@@ -0,0 +1,45 @@
schema_version: markitect.memory.profile.v1
id: local-agent-memory
title: Local Agent Memory
intent: Validate local memory contracts and compile selected graph context.
memory_kinds:
- reasoning
- knowledge
- package
stores:
reasoning: local-event-log
knowledge: local-graph-store
package: markitect-context-registry
limits:
reasoning:
max_nodes: 200
knowledge:
max_nodes: 1000
package:
max_items: 8
latency:
reasoning:
target_ms: 50
knowledge:
target_ms: 120
retention:
reasoning:
strategy: summarize-after-window
window_events: 50
knowledge:
strategy: explicit-forget-or-supersede
refresh:
cadence: manual
compaction:
strategy: event-summary-layer
activation:
max_items: 6
max_tokens: 1800
reserve_tokens: 200
policy:
required_labels:
- public
observability:
emit_events: true
failure:
missing_store: degrade-to-context-package