phase-memory/SCOPE.md

SCOPE

In Scope

phase-memory owns phase-aware memory runtime planning for agentic systems.

Current scope:

• memory phase semantics for ephemeral, fluid, stabilized, and rigid memory
• profile execution planning from Markitect-compatible profile dictionaries
• deterministic lifecycle plans for retention, deletion request, refresh, compaction, stabilization, and activation
• local runtime port definitions for graph stores, event logs, context-package compilers, semantic indexes, policy gateways, audit sinks, and runtime registries
• deterministic in-memory adapters for tests and early integration
• fixture-driven compatibility with Markitect memory profile and graph shapes

Out Of Scope

phase-memory does not own:

• Markitect memory syntax vocabulary or context-package internals
• generic content or knowledge artifact persistence
• durable knowledge query APIs already owned by kontextual-engine
• benchmark corpus ownership or evaluation dashboards
• full identity, authorization, or policy decision platforms
• generic vector database behavior
• provider-specific LLM memory plugins
• durable service deployment topology in the first implementation slice

Adjacent Repositories

• markitect-tool owns memory contracts, validation, and package compilation.
• kontextual-engine owns durable runtime records, audit, policy-aware retrieval, and persistence.
• infospace-bench owns applied pilots, fixture quality checks, and metrics.

phase-memory consumes their contracts and evidence while keeping its own implementation centered on memory-native planning.