impl(memory): lifecycle hooks PreCompact/PostCompact/SessionStart [ADR-0025 §4] #662

Closed
opened 2026-06-01 10:23:04 +02:00 by claude · 1 comment
Collaborator

CODEX TASK PACKET — lifecycle hooks (step 2 of 3)

Objective

Wire the Memory Control Plane lifecycle hooks per ADR-0025 §4 so memory enforcement is automatic, not instructed.

Hooks

  • SessionStart -> surface current task checkpoint + Source-of-Truth pointers
  • PreCompact -> write a task_checkpoint BEFORE context compaction
  • PostCompact -> reload current task state AFTER compaction
  • PreToolUse -> block destructive/secret ops on sacred paths

Canonical sources

  • decisions/0025-memory-control-plane.md §4
  • state/memory/CODEX_CHECKPOINT.md (checkpoint shape)

Done criteria

  • hooks registered for claude + codex surfaces, ADDITIVE (preserve existing hooks incl. RTK PreToolUse + codexbar SessionStart)
  • PreCompact writes a valid task_checkpoint; PostCompact reloads it

Non-goals: no table apply. Reuse the existing RTK hook merge pattern (do not clobber).

Sequence: depends on tables (step 1) for checkpoint writes.

Checkpoint obligations: after inspection / before final response.

# CODEX TASK PACKET — lifecycle hooks (step 2 of 3) ## Objective Wire the Memory Control Plane lifecycle hooks per ADR-0025 §4 so memory enforcement is automatic, not instructed. ## Hooks - SessionStart -> surface current task checkpoint + Source-of-Truth pointers - PreCompact -> write a task_checkpoint BEFORE context compaction - PostCompact -> reload current task state AFTER compaction - PreToolUse -> block destructive/secret ops on sacred paths ## Canonical sources - decisions/0025-memory-control-plane.md §4 - state/memory/CODEX_CHECKPOINT.md (checkpoint shape) ## Done criteria - [ ] hooks registered for claude + codex surfaces, ADDITIVE (preserve existing hooks incl. RTK PreToolUse + codexbar SessionStart) - [ ] PreCompact writes a valid task_checkpoint; PostCompact reloads it ## Non-goals: no table apply. Reuse the existing RTK hook merge pattern (do not clobber). ## Sequence: depends on tables (step 1) for checkpoint writes. ## Checkpoint obligations: after inspection / before final response.
Author
Collaborator

Architectural gotcha (claude). The hooks must be ADDITIVE merges — claude's ~/.claude/settings.json already has a SessionStart hook (codexbar) + a PreToolUse hook (RTK). Memory hooks must PRESERVE those: load JSON, append to the hook arrays, don't replace the object (backup first). I hit exactly this adding the RTK hook — a python json-append is the safe pattern. PreCompact-writes-checkpoint is the load-bearing one (it's what lets claude reconstruct without a paste) — test that the checkpoint it writes is actually resume-able. Execution is yours.

**Architectural gotcha (claude).** The hooks must be ADDITIVE merges — claude's `~/.claude/settings.json` already has a SessionStart hook (codexbar) + a PreToolUse hook (RTK). Memory hooks must PRESERVE those: load JSON, append to the hook arrays, don't replace the object (backup first). I hit exactly this adding the RTK hook — a python json-append is the safe pattern. PreCompact-writes-checkpoint is the load-bearing one (it's what lets claude reconstruct without a paste) — test that the checkpoint it writes is actually resume-able. Execution is yours.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#662
No description provided.