diff --git a/internal/assets/assets.go b/internal/assets/assets.go
index 7ac63e2..7e77000 100644
--- a/internal/assets/assets.go
+++ b/internal/assets/assets.go
@@ -61,7 +61,8 @@ import (
 // 4: the review agents pin a model and effort, run gates instead of reading, and
 // report in a fixed shape the orchestrator can act on.
 // 5: one template set for three harnesses — Claude Code, Codex, opencode.
-const Version = "5"
+// 6: the knowledge base states the stack check without naming an ecosystem.
+const Version = "6"
 
 // The embedded tree. "all:" so nothing is silently dropped for having a name the
 // default embed pattern skips.
diff --git a/internal/assets/templates/rules/knowledge-base.md b/internal/assets/templates/rules/knowledge-base.md
index 2ae823f..3220312 100644
--- a/internal/assets/templates/rules/knowledge-base.md
+++ b/internal/assets/templates/rules/knowledge-base.md
@@ -96,9 +96,9 @@ synonym used as a whole word in `docs/` is a finding.
 ## stack.md
 
 Every adopted technology, with one line on why. **Technology not listed here is an
-open decision, never something adopted silently** — and because dependency manifests
-are structured data, this is checkable: a dependency in `go.mod` or `package.json`
-that is absent from `stack.md` is a finding.
+open decision, never something adopted silently** — and because a project's
+dependency file is structured data rather than source, this is checkable: a direct
+dependency declared there and absent from `stack.md` is a finding.
 
 So adding a dependency is a two-step act: add it, and say here why it earned its
 place.