Skip to content

docs(assets): state the stack rule without naming an ecosystem, in the rule too #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
protonspy merged 1 commit into from
Aug 2, 2026
Merged

docs(assets): state the stack rule without naming an ecosystem, in the rule too #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion internal/assets/assets.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
6 changes: 3 additions & 3 deletions internal/assets/templates/rules/knowledge-base.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading