phase-memory/workplans/PMEM-MATURITY-SCORECARD.md

id, type, title, domain, repo, status, owner, created, updated, state_hub_workstream_id

id	type	title	domain	repo	status	owner	created	updated	state_hub_workstream_id
PMEM-MATURITY-SCORECARD	scorecard	Phase Memory Maturity Scorecard	markitect	phase-memory	active	phase-memory	2026-05-18	2026-05-18	e82b1c2d-0c5e-47d3-9627-f85e7173dcbe

Phase Memory Maturity Scorecard

Purpose

Track progress from the current foundation toward the full INTENT.md vision: a profile-driven, phase-aware memory infrastructure layer for agentic systems.

This scorecard is intentionally practical. It scores what exists in this repo, not what adjacent repositories may already provide.

Scoring Scale

Score	Meaning
0	Not started.
1	Intent or docs exist, but no executable behavior.
2	Deterministic local library slice exists with tests.
3	Usable local runtime or CLI exists with stable envelopes.
4	Integration-ready with policy, persistence, interop, and evaluation coverage.
5	Service-ready and operationally mature with adapter conformance and diagnostics.

Milestone Ladder

Milestone	Target State	Primary Workplans
M1	Foundation complete: domain model, contract ingress, dry-run planners, ports, tests.	PMEM-WP-0001
M2	Usable local runtime: facade, CLI, stable JSON envelopes, local file persistence.	PMEM-WP-0002, PMEM-WP-0003
M3	Governed interop runtime: review gates, audit, policy-aware activation, Markitect package bridge.	PMEM-WP-0004, PMEM-WP-0005
M4	Evaluated activation memory: graph neighborhoods, event paths, ranking, quality metrics.	PMEM-WP-0006
M5	Service-ready adapter layer: service contracts, config, health, external adapter conformance.	PMEM-WP-0007

Current Baseline - 2026-05-18

Overall maturity: 2.0 / 5

The repo has crossed from intent-only into a working deterministic library foundation. It is not yet a usable local runtime because there is no facade, CLI, file-backed persistence, review-gated apply path, package compiler bridge, or service contract.

Dimension	Current	Target	Evidence	Needed Next
Intent and boundaries	4.0	5.0	INTENT.md, SCOPE.md, README.md, architecture doc, PMEM-WP-0001 closure	Keep boundaries current as runtime behavior expands.
Package foundation	2.5	4.0	Python package, exports, dependency-light tests	Add runtime facade, stable public envelopes, CLI.
Profile contract ingress	2.0	4.0	Markitect-compatible profile loading and diagnostics	Add validation adapter boundary and compatibility fixture catalog.
Graph/event contract ingress	2.0	4.0	Graph loading, edge endpoint diagnostics, event model	Add richer event path modeling and import/export repair diagnostics.
Phase domain model	2.5	4.0	Phases, memory kinds, lifecycle states, actions	Add transition rules, approved apply behavior, path-aware state updates.
Profile execution planning	2.5	4.0	Adapter plan, capabilities, policy gates, fallback behavior	Add runtime orchestration, JSON snapshots, CLI outputs.
Lifecycle planning	2.0	4.0	Transition, retention, refresh, compaction dry-run plans	Add profile-driven rule evaluation and review-gated apply.
Activation planning	2.0	5.0	Budgeted selection and Markitect-compatible selection output	Add graph neighborhoods, event paths, ranking, metadata preservation, metrics.
Local persistence	1.0	4.0	In-memory adapters only	Add versioned file-backed graph store and JSONL event log.
Policy and audit	1.5	5.0	Policy/audit ports, allow-all gateway, recording sink, review flags	Add enforcement points, review records, redaction, audit schema.
Observability and diagnostics	1.5	4.0	Planner diagnostics and observability event names	Add audit/health envelopes and adapter status diagnostics.
Markitect interop	1.5	4.0	Compatible schema constants and selection handoff	Add package bridge envelopes, optional validation/compiler adapters.
Kontextual/Infospace interop	1.0	4.0	Boundaries documented and small derived fixtures	Add delegation envelope design and evaluation fixture reports.
Testing and evaluation	2.0	4.0	13 deterministic tests over core planners/adapters	Add CLI snapshots, file-store round trips, policy denial, activation metrics.
Service readiness	0.5	4.0	Runtime ports exist	Add service contracts, config, health checks, adapter conformance tests.
Developer experience	2.0	4.0	README quick start and package map	Add CLI guide, local persistence guide, examples, troubleshooting.

Score Movement Rules

A dimension should move up only when executable behavior and tests exist. Documentation alone can justify score 1, but not score 2 or higher.

Suggested gates:

• Move to 3 when the behavior is usable through the runtime facade or CLI.
• Move to 4 when the behavior has policy, persistence, interop, and regression coverage appropriate to its risk.
• Move to 5 when the behavior has service contracts, health diagnostics, adapter conformance tests, and operational documentation.

Workplan Dependency Map

flowchart TD
  WP1["PMEM-WP-0001\nArchitecture and foundation"]
  WP2["PMEM-WP-0002\nLocal runtime facade and CLI"]
  WP3["PMEM-WP-0003\nFile-backed stores and event paths"]
  WP4["PMEM-WP-0004\nPolicy, audit, review gates"]
  WP5["PMEM-WP-0005\nMarkitect package bridge"]
  WP6["PMEM-WP-0006\nRetrieval and activation quality"]
  WP7["PMEM-WP-0007\nService readiness and adapters"]

  WP1 --> WP2
  WP2 --> WP3
  WP2 --> WP4
  WP2 --> WP5
  WP3 --> WP4
  WP5 --> WP6
  WP4 --> WP6
  WP3 --> WP7
  WP4 --> WP7
  WP5 --> WP7
  WP6 --> WP7

Next Tracking Cadence

Update this scorecard at the end of each workplan closure review:

• record completed task ids
• update dimension scores only when tests and docs support the change
• add residual risks
• list score regressions if behavior was removed or narrowed
• link new workplans if the intent expands