P6 retrieval-discipline reflex: /kg for discovery, never substrate grep (BRO-1426)

[broomva]

Why

Agents reflexively find/grep/cat over research/entities/ instead of /kg, bypassing the routing layer. Two observed failure modes (the find-vs-/kg incident):

1. Silent miss — a guessed slug that doesn't exist returns nothing, usually swallowed by 2>/dev/null / if [ -n "$f" ]. The agent believes it loaded N entities when it loaded fewer and reasons over a false-complete context. (Real incident: agent hand-picked 4 slugs; 1 was a doc not an entity; never noticed.)
2. Recall miss — hand-picked slugs are bounded by agent memory; they miss the relevant entities the catalog routing surfaces. /kg surfaced 2 highly-relevant entities the agent never named; /kg --terms recovered the union.

Change

A P6 retrieval-discipline sub-rule — the read companion to the existing substrate-edit write rule — added to:

• references/primitives.md §P6 (canonical spec)
• assets/templates/AGENTS.md.template §P6 (so bstack bootstrap/repair propagate it on install — this is the "install bstack updates the rules" mechanism)

Rule: knowledge-graph discovery → /kg load <topic> (+ --terms for paraphrase/jargon); Read only on a catalog-confirmed slug; never find -name "$slug.md" as discovery.

Reasoning-enforced reflex (no hook/gate), consistent with the P6/P9 reflexive-trigger pattern. No primitive-count change (sub-rule, not a new primitive) — 20 primitives intact in both files.

Evidence

research/entities/pattern/substrate-grep-bypasses-routing.md + the BRO-1425 benchmark. Workspace AGENTS.md §P6 updated in lockstep (Self-Documenting Standards: same reflex across all three surfaces).

Closes BRO-1426 (bstack/governance half)

🤖 Generated with Claude Code

[linear]

BRO-1426

[coderabbitai]

Warning

Review limit reached

@broomva, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 51 minutes and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dc695c87-28bc-49ac-b899-d8205dbee6ab

📥 Commits

Reviewing files that changed from the base of the PR and between 1538732 and 3e63cc4.

📒 Files selected for processing (2)

• assets/templates/AGENTS.md.template
• references/primitives.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/bro-1426-p6-kg-discovery-reflex

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}