generated from coulomb/repo-seed
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# Agentic Memory Profile Pilot Report
|
|
|
|
## Decision
|
|
|
|
The pilot validates agentic memory profiles through file-backed evidence in
|
|
`infospace-bench`. The durable runtime remains out of scope. Markitect owns the
|
|
memory graph/profile/selection contracts and context package compiler, while
|
|
`kontextual-engine` owns future runtime state, audit, permissions, retention,
|
|
refresh, compaction, and durable write review gates.
|
|
|
|
## Fixture Set
|
|
|
|
- `output/memory/memory-profile.yaml`: Markitect-compatible memory profile.
|
|
- `output/memory/memory-graph.yaml`: reviewed decision, trace, and artifact
|
|
neighborhood graph.
|
|
- `output/memory/restart-context-selection.yaml`: graph selection for a restart
|
|
package.
|
|
- `output/memory/restart-context-package.expected.yaml`: deterministic
|
|
expectations for compiled package shape.
|
|
- `output/memory/context-package-evaluation.yaml`: package usefulness evidence
|
|
and contract feedback.
|
|
- `output/memory/traces/*.yaml`: applied workflow traces showing where memory
|
|
records arise.
|
|
|
|
## Result
|
|
|
|
The selected restart package combines three kinds of useful context:
|
|
|
|
- the boundary decision that keeps this repo as the evaluation layer
|
|
- the review gate that prevents hidden durable memory writes
|
|
- the Wealth/VSM source and entity neighborhood needed to resume artifact review
|
|
|
|
This is enough to answer the Workplan 17 pilot questions without turning the
|
|
infospace into a memory runtime.
|