agent-ops
OPS-52
memory-lint §12/§9 vs global CLAUDE.md: per-agent identity + dates in memory/ — Elazar decision
Done high
bwbin-whey-cc
Activity
-
wi cli
-
q#29 to=elazar: memory-lint enforces evolutiva-memory-discipline.md across ALL ~/.claude/projects/*/memory dirs, but two of its rules collide with the global CLAUDE.md and produce hard-fails on memories that exist by
-
awaiting elazar
-
Fleet identity-filename data points for the §12 sub-question: bin-whey-cc uses session-identity.md (hyphen); nw-venus-cc uses session_identity.md (underscore, session_ prefix); llmmsg-srv-cc uses agent_identity_<name>.md. Three distinct patterns - 1(A) needs Elazar to also pick the canonical filename.
-
memory-lint.sh v1.6 shipped sh.git 9e25ecb. Per agent-maintainer ruling (relayed by nw-venus-cc 2026-05-22): §9 body-date FAIL removed; §12 per-agent-identity FAIL removed. §3 filename-ban unchanged. Verified WARN-only on basquetWi + ~/.local/bin memory dirs (both previously hard-failing). Combined with WI 500, the KPI escalation loop on those dirs is now broken: next memlint-cron run exits 0 and deletes the stale _lint-report.md.
-
ANSWERED (recovered from the close event, not decided now). Per the agent-maintainer ruling relayed by nw-venus-cc 2026-05-22, shipped as memory-lint.sh v1.6 (sh.git 9e25ecb): CONFLICT 1 resolved as option A-equivalent — the §12 per-agent-identity FAIL was removed outright rather than carved out, so session-identity.md no longer hard-fails. CONFLICT 2 resolved as option A-equivalent — the §9 body-date FAIL was removed, so dates may appear as event provenance. §3 filename-ban unchanged. Verified WARN-only on the basquetWi and ~/.local/bin memory dirs.
-
backfill: blockedReason cleared on a closed row; it described a dependency discharged before the item closed and pre-dated the d6153e2 fix that now clears it automatically (Elazar decision 1b, 2026-08-19)
question
2026-05-21
2026-08-19
2026-05-23 01:37