generated from coulomb/repo-seed
tegwick
39a053bfd0
Honest first-pass maturity vector grounded in README/docs/tests present in this repo; no invented evidence. Flagged for human review before publish. See reuse-surface history/2026-07-06-coverage-classification.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
122 lines
4.6 KiB
Markdown
122 lines
4.6 KiB
Markdown
---
|
|
id: capability.memory.phase-planning
|
|
name: Profile-Driven Memory Phase Planning (phase-memory)
|
|
summary: Interprets Markitect memory profiles as runtime plans, modeling memory phases and producing deterministic
|
|
dry-run actions for retention, refresh, compaction, stabilization, and activation.
|
|
owner: phase-memory
|
|
status: draft
|
|
domain: communication
|
|
tags:
|
|
- memory
|
|
- agentic
|
|
- planning
|
|
maturity:
|
|
discovery:
|
|
current: D3
|
|
target: D5
|
|
confidence: medium
|
|
rationale: README explicitly documents the repo's boundary against adjacent repos (markitect-tool
|
|
owns profile/graph/event contracts; kontextual-engine owns durable storage/retrieval; infospace-bench
|
|
owns pilots/evaluation) and states the first slice is local-first, dependency-light, dry-run only.
|
|
availability:
|
|
current: A1
|
|
target: A3
|
|
confidence: medium
|
|
rationale: Python package (`phase-memory`), pip-installable; explicitly does not launch a service
|
|
or mutate durable memory stores by default in this first slice.
|
|
external_evidence:
|
|
completeness:
|
|
level: C1
|
|
confidence: low
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- memory phase modeling (retention, refresh, compaction, stabilization, activation)
|
|
- deterministic dry-run action generation
|
|
- explicit boundary docs vs three adjacent repos
|
|
broken_expectations: []
|
|
out_of_scope_expectations: []
|
|
reliability:
|
|
level: R0
|
|
confidence: low
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- first slice is dry-run only; does not yet mutate durable stores
|
|
discovery:
|
|
intent: Interpret Markitect memory profiles as runtime plans and produce deterministic dry-run actions
|
|
for memory-phase transitions, as the operating layer between profile definition (markitect-tool) and
|
|
durable storage (kontextual-engine).
|
|
includes:
|
|
- memory phase modeling and deterministic dry-run planning for retention/refresh/compaction/stabilization/activation
|
|
excludes:
|
|
- memory profile/graph/event contract definition (markitect-tool)
|
|
- durable storage and permission-aware retrieval (kontextual-engine)
|
|
- concrete pilots and evaluation (infospace-bench)
|
|
assumptions: []
|
|
use_cases: []
|
|
research_memos: []
|
|
availability:
|
|
current_level: A1
|
|
target_level: A3
|
|
current_artifacts:
|
|
- Python package (`phase-memory`)
|
|
target_artifacts: []
|
|
consumption_modes:
|
|
- library import
|
|
relations:
|
|
depends_on: []
|
|
supports: []
|
|
related_to: []
|
|
evidence:
|
|
documentation:
|
|
- README.md
|
|
tests:
|
|
- tests/
|
|
consumer_feedback: []
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- agentic systems needing deterministic memory-phase planning distinct from storage or profile-contract
|
|
concerns
|
|
not_recommended_for:
|
|
- needs for durable memory mutation today (first slice is dry-run only)
|
|
known_limitations:
|
|
- local-first, dependency-light first slice; no service or durable mutation yet
|
|
promotion_history: []
|
|
---
|
|
|
|
# Profile-Driven Memory Phase Planning (phase-memory)
|
|
|
|
## Overview
|
|
|
|
`phase-memory` is the profile-driven memory operating layer for agentic systems: it interprets Markitect memory profiles as runtime plans and produces deterministic dry-run actions for memory phases (retention, refresh, compaction, stabilization, activation), explicitly bounded against adjacent repos that own contracts (markitect-tool), durable storage (kontextual-engine), and evaluation (infospace-bench).
|
|
|
|
## Assessment notes
|
|
|
|
### Discovery
|
|
|
|
README explicitly documents the repo's boundary against adjacent repos (markitect-tool owns profile/graph/event contracts; kontextual-engine owns durable storage/retrieval; infospace-bench owns pilots/evaluation) and states the first slice is local-first, dependency-light, dry-run only.
|
|
|
|
### Availability
|
|
|
|
Python package (`phase-memory`), pip-installable; explicitly does not launch a service or mutate durable memory stores by default in this first slice.
|
|
|
|
### Completeness
|
|
|
|
First-pass honest assessment from the REUSE-WP-0017 coverage campaign
|
|
(reuse-surface). No external consumer feedback exists yet; levels reflect
|
|
scope-vs-intent documentation quality, not internal code quality.
|
|
|
|
### Reliability
|
|
|
|
No production consumer telemetry exists yet; reliability level is
|
|
intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
|
|
|
|
## Promotion checklist
|
|
|
|
- [x] ID follows `capability.<domain>.<name>` pattern
|
|
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
|
|
- [x] `external_evidence` is populated separately from `maturity`
|
|
- [ ] Relations reference valid capability IDs (none yet)
|
|
- [x] Index entry added in `registry/indexes/capabilities.yaml`
|