You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clean up install script and domain contribution guidelines
Remove unused VERSION variable from install.sh. Add guidance to
DOMAINS.md that new domain PRs must not duplicate or conflict with
existing domains.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: DOMAINS.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,10 +128,11 @@ These verify that agents hedge appropriately on questions that fall outside any
128
128
129
129
To add a new domain:
130
130
131
-
1. Add keywords to `DomainKeywords` in `internal/analysis/domains.go`
132
-
2. Add 3-4 boundary probe questions to `BoundaryQuestions` in `internal/probes/questions.go`
133
-
3. Include at least one in-domain calibration question (where the `domain` field matches the domain key) and at least two cross-domain boundary questions
134
-
4. Run `go test ./...` to verify nothing breaks
135
-
5. Update this file with the new domain, its keywords, and which domains its probes test against
131
+
1. Check this file first. New domains must not duplicate or conflict with existing domains. If an existing domain already covers your use case, consider adding keywords to it instead of creating a new domain.
132
+
2. Add keywords to `DomainKeywords` in `internal/analysis/domains.go`.
133
+
3. Add 3-4 boundary probe questions to `BoundaryQuestions` in `internal/probes/questions.go`.
134
+
4. Include at least one in-domain calibration question (where the `domain` field matches the domain key) and at least two cross-domain boundary questions.
135
+
5. Run `go test ./...` to verify nothing breaks.
136
+
6. Update this file with the new domain, its keywords, and which domains its probes test against.
136
137
137
138
Probe questions should be specific enough that a knowledgeable agent could answer them, but clearly outside scope for agents in other domains. Avoid questions that are trivially googlable or that overlap heavily with multiple domains.
0 commit comments