phase-memory/registry/capabilities/capability.memory.phase-planning.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.memory.phase-planning	Profile-Driven Memory Phase Planning (phase-memory)	Interprets Markitect memory profiles as runtime plans, modeling memory phases and producing deterministic dry-run actions for retention, refresh, compaction, stabilization, and activation.	phase-memory	draft	communication	memory agentic planning	discovery availability current target confidence rationale D3 D5 medium 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. current target confidence rationale A1 A3 medium Python package (`phase-memory`), pip-installable; explicitly does not launch a service or mutate durable memory stores by default in this first slice.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations memory phase modeling (retention, refresh, compaction, stabilization, activation) deterministic dry-run action generation explicit boundary docs vs three adjacent repos level confidence basis known_reliability_risks R0 low consumer_quality_signals first slice is dry-run only; does not yet mutate durable stores	intent includes excludes assumptions use_cases research_memos 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). memory phase modeling and deterministic dry-run planning for retention/refresh/compaction/stabilization/activation memory profile/graph/event contract definition (markitect-tool) durable storage and permission-aware retrieval (kontextual-engine) concrete pilots and evaluation (infospace-bench)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Python package (`phase-memory`) library import	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md tests/	recommended_for not_recommended_for known_limitations agentic systems needing deterministic memory-phase planning distinct from storage or profile-contract concerns needs for durable memory mutation today (first slice is dry-run only) local-first, dependency-light first slice; no service or durable mutation yet

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

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml