Conciseness

Prose is telegraphic and fact-dense (paths, event names, commands) with zero padding or explanation of known concepts, but inline dates ('Since the 2026-07-17 fix', 'taste bench (2026-07-17)') sit outside the retirement/deprecated sections and the top blockquote duplicates the 'Retired and parked surfaces' section, leaving minor trims. Anchor 4 fits better than 5.

Actionability

Commands are copy-paste ready and cover the common cases: 'jq --arg slug "<slug>" '.sent[] | select(.slug == $slug) | {slug, outcome}' ~/.joelclaw/observer-neat-memories.json', 'bun scripts/backfill-session-index.ts' with dry-run then --apply, 'bun scripts/messaging-visible-delivery-canary.ts' with an exit-0 success criterion, plus concrete emoji-to-outcome mappings. Fully executable guidance matching anchor 5.

Workflow Clarity

Recipes are ordered symptom-to-fix with validation gates on risky operations (--dry-run promotion, dry-run backfill, 200-check before sharing, exit-0 canary) and a forked decision path ('Chain alive → ...; Chain dead → ...'). However, most recipes stop at verification without an explicit fix-and-retry loop if the check fails, matching anchor 4 rather than 5.

Progressive Disclosure

No bundle files exist, so this is scored on body structure: clear section headers (location table, debug recipes, usage, retired surfaces, doctor) with one-level-deep external pointers clearly signaled ('read it before deep debugging'). The location table and behavior-card detail could arguably live in separate reference files, so anchor 4's 'minor organization gaps' fits better than 5.

Specificity

"Debug, maintain, and use" are broad verbs, but the description enumerates six concrete subsystems ("observer capture/dreams, Brain .svx stores, neat-memory curation, Telegram delivery, reaction grading, wiki rendering"). It lists several specific capabilities but doesn't break out the action per subsystem, matching anchor 4 rather than 5.

Completeness

Both halves are explicit: a clear what ("Debug, maintain, and use the joelclaw memory system — ...") and an explicit trigger clause ("Load whenever work touches the memory system, the curator, dreams, observations, grading, or a memory surface misbehaves") with concrete trigger phrases, matching the anchor-5 example structure.

Trigger Term Quality

The when-clause carries natural phrases ("memory system, the curator, dreams, observations, grading, or a memory surface misbehaves") a user would plausibly say. A few natural terms from the what-half (wiki, recall, Telegram/DM, Brain) are missing from the trigger list, so anchor 4 fits better than 5.

Distinctiveness Conflict Risk

The named "joelclaw memory system" plus niche triggers (curator, dreams, neat-memory) form a clear proprietary niche with minimal chance of firing for an unrelated skill, matching anchor 5.