coulomb/infospace-bench
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Agentic memory profile

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-15 16:01:35 +02:00
parent 9a03fd1606
commit c3b62a6ec3
17 changed files with 960 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
infospaces/agentic-memory-profile-pilot/artifacts/sources/memory-pilot-brief.md Normal file
View File

@@ -0,0 +1,33 @@
# Agentic Memory Profile Pilot Brief
## Pilot Corpus
The pilot uses `infospaces/wealth-vsm-legacy-slice` as the concrete corpus. It
is small enough to inspect by hand, already contains a source, entities,
relations, evaluations, metrics, history, and an engine sync plan, and it
exercises the same restart and review questions that a memory package should
help with.
The fixture also references the generic source generator because that workflow
is the likely producer of future memory events. The pilot does not create a
durable memory store; it records file-backed evidence and Markitect-compatible
contracts only.
## Memory Questions
| Question | Fixture Coverage | Acceptance Signal |
| --- | --- | --- |
| Which reasoning decisions should become durable memory? | `decision.file-backed-pilot` and `constraint.no-durable-runtime` | A restart package can recover the boundary without reading every workplan. |
| Which workflow events are useful later? | `turn.review-handoff`, `tool_call.generator-status`, and `observation.restart-risk` | Trace events explain why the package contains both decisions and artifact neighborhoods. |
| Which knowledge graph neighborhoods improve review? | `entity.division-of-labour`, `entity.market-extent`, and `artifact.wealth-source` | The package ties the decision path to the concrete Wealth/VSM artifacts. |
| Which context package shape helps agents? | `restart-context-selection.yaml` | The package stays within eight items and 1200 tokens. |
| Which profile parameters are misplaced or missing? | `context-package-evaluation.yaml` | Feedback separates Markitect contracts, engine runtime needs, and infospace evaluation knobs. |
## Acceptance Targets
- Memory profile and graph fixtures validate with `markitect-tool`.
- Context package compilation is deterministic aside from runtime timestamps.
- Every selected package item has a source span or a Markitect synthetic memory
span.
- No provider credentials, secrets, or durable user memory are stored.
- Runtime persistence remains delegated to `kontextual-engine`.