Skip to content

memory-lifecycle-v2 README: name which ai-memory pin it means - #300

Merged
seathatflowsinourveins merged 1 commit into
mainfrom
claude/memory-lifecycle-v2-pin-wording-20260925
Sep 25, 2026
Merged

memory-lifecycle-v2 README: name which ai-memory pin it means#300
seathatflowsinourveins merged 1 commit into
mainfrom
claude/memory-lifecycle-v2-pin-wording-20260925

Conversation

@seathatflowsinourveins

@seathatflowsinourveins seathatflowsinourveins commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Scope

  • What this PR changes: wording only, in blueprints/memory-lifecycle-v2/README.md (Memory lifecycle v2: ai-memory 2.3.2 and 2.4.0 pass 89/89 checks each (real-time TTL, 4-project scope, restart durability) #292). It changes "the repository's adopted pin" to "the durable-memory landscape winner pin" and adds a dated pin note.
    • Production on the workstation moved to ai-memory 2.4.0 in a user-approved window.
    • The cleanup session's pin-move PR takes manifests/stack.json and the Linux bootstrap pins to 2.4.0.
    • The landscape winner pin stays 2.3.2 until a verdict wave.
  • Not edited: the sealed PREREGISTRATION.md and the run's results-20260925.json stay as recorded, because they were accurate when written.
  • Requested by: cleanup-wsl-audit, which is moving the pins.
  • Lane: lane:foundation.

SOTA sources

Local commands run

validate.yml's offline validate-job steps + evidence_manifest.py --check -> 0 failures

🤖 Generated with Claude Code

Scout @claude
memory-lifecycle-v2 README: name which ai-memory pin it means
f0d8dc1 
Production and stack.json move to ai-memory 2.4.0 while the durable-memory landscape winner pin stays 2.3.2 until a verdict wave; the README now says 'landscape winner pin' and carries a dated pin note. The sealed PREREGISTRATION.md and the run's results JSON are left as recorded.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 25, 2026

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Sep 25, 2026
@seathatflowsinourveins
seathatflowsinourveins merged commit efa32d9 into main Sep 25, 2026
24 checks passed
@seathatflowsinourveins
seathatflowsinourveins deleted the claude/memory-lifecycle-v2-pin-wording-20260925 branch September 25, 2026 23:16
@seathatflowsinourveins seathatflowsinourveins mentioned this pull request Sep 26, 2026
Open
9 of 22 tasks
@seathatflowsinourveins

seathatflowsinourveins commented Sep 26, 2026

Copy link
Copy Markdown
Collaborator Author

Cross-family review (Codex CLI 0.155.1, gpt-6-astra, model_reasoning_effort=max, read-only sandbox), 2026-09-26. Run by the workstation coordinator against a clean checkout of main after merge. Supported findings get a repair PR (one repair round; residuals recorded).

DEFECTS FOUND

medium | blueprints/memory-lifecycle-v2/README.md:138 | The production-upgrade claim, repeated in the PR body, lacks retained native evidence. The workstation use receipt records 2.3.2; the later token-tools receipt mentions 2.4.0 in narrative without retaining service-version output. The lifecycle results cover disposable stores only. Stack and bootstrap pins still specify 2.3.2. | Link a sanitized post-upgrade service/version receipt and the companion pin-change PR. Until supported, identify the upgrade as reported but unverified and the pin change as pending.

@seathatflowsinourveins seathatflowsinourveins mentioned this pull request Sep 26, 2026
Merged
seathatflowsinourveins added a commit that referenced this pull request Sep 26, 2026
@seathatflowsinourveins Scout @claude
Token tooling review fixes: probe exit status and process-group lifec…
e3cbd24 
…ycle, context-mode Codex binding, retained coverage evidence (#333)

Repairs the GPT-6 cross-family findings on #289, #297, #300 and #303.

Co-authored-by: Scout <scout@local>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@seathatflowsinourveins