Conciseness

The body is a dense, imperative protocol that assumes Claude's competence and explains no known concepts; only minor trims are possible (redundant emphasis in AFTER COMPACTION — 'IMMEDIATELY call' plus 'Do not skip step 1' plus the loss explanation — and the Codex session-binding section restating identity rules twice).

Actionability

Concrete guidance throughout: exact tool names, a field-by-field mem_save format with examples, numbered search and compaction sequences, and a runnable fallback command ('engram setup codex'). Minor gaps keep it from 5: no worked example of a complete mem_save call and fuzzy conditions like 'significant explicit closure'.

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation and error recovery: search-before-write, full read with mem_get_observation before update, 'On ambiguous identity or failed lookup, do not overwrite', 'If memory work fails... still send the answer', and a concrete repair path when tools are unavailable. The topic-update flow is a checklist with feedback loops for the write path, so the destructive/batch cap does not apply.

Progressive Disclosure

No bundle files exist; all content lives in one well-sectioned ~110-line file with clear headers, which is defensible for an always-active protocol. However, detail-heavy material like the Codex session-binding internals could sit in a reference file, leaving minor organization gaps rather than the fully split structure of a 5.

Specificity

The description names the domain ('Selective persistent memory') and 1-2 concrete actions ('preserve verified, durable knowledge', 'safe topic updates'), but 'worth reconstructing' and 'host-owned lifecycle' are design principles rather than actions, and capabilities the body actually covers (search/recall, session summaries, compaction recovery) are omitted.

Completeness

Both 'what' (selective preservation, topic updates, lifecycle) and 'when' ('ALWAYS ACTIVE', an explicit activation clause equivalent to 'Use when...') are present, but the 'when' is a blanket always-on statement without concrete trigger phrases, so it is not a 5.

Trigger Term Quality

'persistent memory' and 'knowledge' are relevant keywords, but the natural phrases a user would actually say ('remember', 'recall', 'what did we do') and their variations are missing, matching the 'some relevant keywords but missing common variations' anchor.

Distinctiveness Conflict Risk

'Selective persistent memory' with topic-update and host-lifecycle semantics carves a mostly distinct niche with only minor overlap risk against other memory/notes skills; it is more specific than a bare domain claim (3) but lacks distinct named triggers for a 5.