Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
# Memory Consolidation Current Progress and Next Steps

Status: AI-authored draft. Not yet human-approved.
Last updated: 2026-05-13 21:23 KST
Last updated: 2026-05-13 22:38 KST





## v0.1.154 active runtime checkpoint

- Release: `v0.1.154` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`.
- Release: `v0.1.155` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- Hermes `personal-oss` hook accepted and `hermes --profile personal-oss hooks doctor` is green.
- Runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.154-runtime-qa-20260513T091806/`.
- v0.1.154 fixes episode decay-collapse evidence snapshots by reading episode `source_ids_json`; the v0.1.154 decay-collapse decision over the mixed corpus now runs read-only/no-mutation.
Expand All @@ -35,11 +35,11 @@ This document is the restartable checkpoint after the v0.1.153 release/runtime r

Current verified release state:

- Release: `v0.1.154`.
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`.
- Release: `v0.1.155`.
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`.
- npm: `@cafitac/agent-memory@0.1.153`.
- PyPI: `cafitac-agent-memory==0.1.153`.
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`.
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- Hermes hook doctor is green for `personal-oss` on the v0.1.153 runtime after `--accept-hooks`; default/earlypay/infra-admin stayed on prior green runtime unless explicitly upgraded later.
- Fresh G4 report directory retained: `/Users/reddit/.agent-memory/reports/g4-v0138-20260512-132253/`.

Expand Down
19 changes: 14 additions & 5 deletions .dev/status/current-handoff.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,21 @@
# agent-memory current handoff

Status: AI-authored draft. Not yet human-approved.
Last updated: 2026-05-13 21:23 KST
Last updated: 2026-05-13 22:38 KST





## v0.1.155 active runtime checkpoint

- Release: `v0.1.155` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- Hermes `personal-oss` hook accepted and `hermes --profile personal-oss hooks doctor` is green.
- Runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.155-runtime-qa-20260513T133421/`.
- v0.1.155 adds explicit `--epoch-start` support to `dogfood trace-quality` and propagates it through `dogfood scheduled-dry-run`, so fresh scheduled evidence can be measured without legacy lookback pollution.
- Fresh v0.1.155 hook-window smoke (`2026-05-13T13:33:00Z`) is read-only/no-mutation and passes scheduled dry-run as `scheduled_dry_run_quality_gate_passed_plan_g4_only`; broad G4/background apply is still not enabled.

## v0.1.154 continuation / v0.1.155 source checkpoint

- Continuation report directory: `/Users/reddit/.agent-memory/reports/v0.1.154-continuation-20260513T120215/`.
Expand All @@ -18,8 +27,8 @@ Last updated: 2026-05-13 21:23 KST

## v0.1.154 active runtime checkpoint

- Release: `v0.1.154` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`.
- Release: `v0.1.155` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- Hermes `personal-oss` hook accepted and `hermes --profile personal-oss hooks doctor` is green.
- Runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.154-runtime-qa-20260513T091806/`.
- v0.1.154 fixes episode decay-collapse evidence snapshots by reading episode `source_ids_json`; the v0.1.154 decay-collapse decision over the mixed corpus now runs read-only/no-mutation.
Expand All @@ -45,8 +54,8 @@ Use `.dev/status/next-agent-memory-action.md` as the shortest current source of
Current verified state:

- Latest completed release/runtime rollout: `v0.1.153`.
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`.
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`.
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`.
- npm/PyPI latest verified as `0.1.153`.
- Hermes hook doctor is green for `personal-oss` after `--accept-hooks` smoke on the v0.1.153 runtime.
- Fresh G4 report directory retained: `/Users/reddit/.agent-memory/reports/g4-v0138-20260512-132253/`.
Expand Down
24 changes: 12 additions & 12 deletions .dev/status/next-agent-memory-action.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# agent-memory next action

Status: AI-authored draft. Not yet human-approved.
Last updated: 2026-05-13 21:23 KST
Last updated: 2026-05-13 22:38 KST

## Use this first when the user asks

Expand Down Expand Up @@ -36,12 +36,12 @@ Reasoning:

## Latest verified checkpoint

- Release: `v0.1.154`
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`
- npm: `@cafitac/agent-memory@0.1.154`
- PyPI: `cafitac-agent-memory==0.1.154`
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`
- Runtime smoke: PyPI install smoke passed after simple-index propagation, npm installed-bin smoke passed, GitHub release exists, and `hermes --profile personal-oss hooks doctor` is green after `--accept-hooks` approval for the v0.1.153 hook command. v0.1.154 runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.154-runtime-qa-20260513T091806/`.
- Release: `v0.1.155`
- GitHub Release: `https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`
- npm: `@cafitac/agent-memory@0.1.155`
- PyPI: `cafitac-agent-memory==0.1.155`
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`
- Runtime smoke: PyPI install smoke passed after simple-index propagation, npm installed-bin smoke passed, GitHub release exists, and `hermes --profile personal-oss hooks doctor` is green after `--accept-hooks` approval for the v0.1.153 hook command. v0.1.155 runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.155-runtime-qa-20260513T133421/`.
- Current source follow-up reports: `/tmp/agent-memory-g4-corridor-smoke/`, `/tmp/agent-memory-telemetry-reset-decision/`, `/tmp/agent-memory-fresh-epoch-v0149/`, and `/tmp/agent-memory-apply-corridor-v0150/`.
- Fresh report directory retained from G4 diagnostics: `/Users/reddit/.agent-memory/reports/g4-v0138-20260512-132253/`.
- Fresh linkage diagnosis retained: `/Users/reddit/.agent-memory/reports/g4-v0138-20260512-132253/g4-linkage-gap-diagnose-v0138-fresh.json` with decision `fresh_trace_linkage_gap_not_detected`.
Expand All @@ -54,7 +54,7 @@ Reasoning:

## Current blocker

The v0.1.154 runtime is healthy, and current source has an epoch-start scheduled-dry-run measurement fix queued for release, but broad brain-like automation is still intentionally blocked:
The v0.1.155 runtime is healthy and includes the epoch-start scheduled-dry-run measurement fix, but broad brain-like automation is still intentionally blocked:

- Fresh epoch report `/Users/reddit/.agent-memory/reports/default-ranking-v0152-shadow/fresh-epoch-since-v0152-with-metadata-gap-diagnostic.json`: quality gate still fails with `low_epoch_observation_trace_coverage` and `epoch_empty_retrieval_outcome_metadata_gap_classified`. The new metadata-gap diagnostic shows `dominant_blocker=classified_legacy_missing_outcome`, `classified_missing_outcome_count=6`, and `unresolved_adapter_payload_gap_count=0`; continue metadata-rich dogfooding before telemetry reset or default ranking migration.
- G4 review queue copy/live-safe smoke `/tmp/agent-memory-apply-corridor-v0150/`: live preview/list/reconciliation were read-only; copy telemetry reset and copy G4 queue apply preserved durable memory (`mutated=false`); live G4 queue apply was idempotent with `applied_count=0`, `already_applied_count=1`, `mutated=false`, and `default_retrieval_unchanged=true`.
Expand All @@ -69,7 +69,7 @@ The v0.1.154 runtime is healthy, and current source has an epoch-start scheduled
Proceed in this sequence:

1. Keep live default ranking on `conservative_legacy`; do not run `retrieval-ranking-migrate-default` against the live profile until an operator gives the exact approval phrase and fresh-epoch telemetry is green.
2. Release the current `--epoch-start` scheduled-dry-run measurement slice, then keep metadata-rich dogfooding and compare fresh-epoch windows using the explicit epoch boundary; do not let legacy lookback rows drive go/no-go decisions.
2. Keep metadata-rich dogfooding and compare fresh-epoch windows using the released explicit `--epoch-start` boundary; do not let legacy lookback rows drive go/no-go decisions.
3. Keep live mixed retrieval corpus coverage in the shadow-only lane; extend it only through guarded reviewed-candidate promotions with backup/audit evidence.
4. Keep fresh reviewed candidate promotion limited to the guarded explicit-approval corridor.
5. Keep broad G4/background apply blocked until ranking gate, rollback replay, telemetry reconciliation/fresh epoch, and reviewed queue approvals all pass on real runtime evidence.
Expand Down Expand Up @@ -99,16 +99,16 @@ git status --short --branch
import agent_memory
print(agent_memory.__version__)
PY
/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory dogfood supersession-preview /Users/reddit/.agent-memory/memory.db --limit 200 --top 10 --output /tmp/agent-memory-next-g5f-supersession-preview.json
/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory dogfood supersession-preview /Users/reddit/.agent-memory/memory.db --limit 200 --top 10 --output /tmp/agent-memory-next-g5f-supersession-preview.json
```

Expected: read-only/no-mutation. Collapse proof may become satisfied only through proof artifacts; collapse/delete apply and broad G4/background apply remain blocked.


## v0.1.154 active runtime checkpoint

- Release: `v0.1.154` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.154`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory`.
- Release: `v0.1.155` (`https://github.com/cafitac/agent-memory/releases/tag/v0.1.155`).
- Runtime: `/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory`.
- Hermes `personal-oss` hook accepted and `hermes --profile personal-oss hooks doctor` is green.
- Runtime QA artifacts: `/Users/reddit/.agent-memory/reports/v0.1.154-runtime-qa-20260513T091806/`.
- v0.1.154 fixes episode decay-collapse evidence snapshots by reading episode `source_ids_json`; the v0.1.154 decay-collapse decision over the mixed corpus now runs read-only/no-mutation.
Expand Down
4 changes: 2 additions & 2 deletions tests/test_roadmap_contract.py
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,8 @@ def test_v0152_status_docs_record_current_brainlike_runway_and_blocked_broad_app
stage_g = _read_doc(".dev/roadmap/memory-consolidation/stage-g-cautious-automation.md")

for doc in (next_action, handoff, current_progress):
assert "v0.1.154" in doc
assert "/Users/reddit/.agent-memory/runtime/v0.1.154/.venv/bin/agent-memory" in doc
assert "v0.1.155" in doc
assert "/Users/reddit/.agent-memory/runtime/v0.1.155/.venv/bin/agent-memory" in doc
assert "fresh_trace_linkage_gap_not_detected" in doc
assert "g4-v0138-20260512-132253" in doc
assert "Overall north-star: 78-80%" in doc
Expand Down