2 Commits
Author SHA1 Message Date
admin 86cf1b6f81 Include existing launch-policy research methods in automatic guidance
Check instruction packages / check (pull_request) Successful in 5s
Check instruction packages / check (push) Successful in 4s
2026-11-14 11:21:38 -05:00
admin 015b4d1d0e Keep automatic research within approved extraction scope
Check instruction packages / check (push) Successful in 5s
Check instruction packages / check (pull_request) Successful in 4s
2026-11-14 10:40:33 -05:00
4 changed files with 18 additions and 6 deletions

No files matched your search

+1 -1
View File
@@ -100,4 +100,4 @@ The owner retains publication identity/order, mandatory status, complete durable
artifacts, verification and Operator acceptance. These packages customize
answer/detail/example/acknowledgement presentation only.
The automatic `research-auto` Planner package supplies primary-source selection, preferred-domain exploration/refinement and evidence-reading methodology. The manual `research` package remains available on request. Tool arguments, budgets, continuation, recovery and untrusted research provenance belong to the owner.
The automatic `research-auto` Planner package supplies primary-source selection, preferred-domain exploration/refinement and evidence-reading methodology, publication/version checking, corroboration and already-admitted empirical evidence methods. The manual `research` package remains available on request. Tool arguments, budgets, continuation, recovery and untrusted research provenance belong to the owner.
+13 -3
View File
@@ -3,11 +3,21 @@ name: research-auto
description: Source selection and reading methods for assigned Planner research.
metadata:
relayview-display-name: Research methodology
relayview-version: 0.12.0
relayview-version: 0.12.2
---
# Research methodology
Prefer primary sources: the official specification, documentation, or source repository that owns a claim. When an applicable authoritative domain is already known, preferredDomains may rank it higher; omit the option during broad exploration and refine a later search after discovering the right domain. Prefer narrow publisher hosts over broad multi-tenant hosts, and inspect/fetch returned sources before relying on them.
Prefer primary sources: applicable official documentation, specifications, source code, release notes, maintainer records, and reproducible first-party artifacts that own a claim; use secondary sources for orientation and corroboration. When an applicable authoritative domain is already known, preferredDomains may rank it higher; omit the option during broad exploration and refine a later search after discovering the right domain. Prefer narrow publisher hosts over broad multi-tenant hosts, and inspect/fetch returned sources before relying on them.
Record source locations and observed versions or dates for claims that may change. Label inferences and unresolved facts. Put concise findings and citations in the planning response so the Plan can use them.
When external research is material, use web_search to discover candidate public sources before web_fetching selected applicable evidence instead of guessing a destination URL.
Check publication date, applicable product and version, and whether a source supports the precise claim. State uncertainty, conflicts, missing access, and inferences explicitly.
Corroborate consequential or surprising claims with independent evidence when practical; mirrors, syndication, repetition, and pages derived from one upstream source are not independent.
For an empirically testable technical claim, prefer a small reproducible local experiment only when this role already has an approved execution capability. Record the question, procedure, relevant versions and resolved paths, observation, and limitations; do not generalize beyond the tested environment.
Use confidence language proportional to the evidence and identify claims that still depend on provider ranking, inaccessible sources, or unverified assumptions.
Repeat an exact query only when the cached result is intentionally sufficient; use a materially narrower query when new terms, version, claim, or source scope justify a distinct auditable search.
+2 -2
View File
@@ -2,14 +2,14 @@
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.12.0"
"reference": "v0.12.2"
},
"role": "planner",
"step": "planning",
"files": [
{
"path": "SKILL.md",
"sha256": "a3acca3ed412dc0e8351d82d7e201ef6112bf3a68142f06e570bd29a71391b22"
"sha256": "112036daeb1f760093345805b8c17b1f385723f3597608cf8ad19d72023ccd74"
}
]
}
+2
View File
@@ -18,6 +18,8 @@ class PackageTests(unittest.TestCase):
text = (package / "SKILL.md").read_text()
self.assertIn("omit the option during broad exploration", text)
self.assertIn("inspect/fetch returned sources", text)
self.assertIn("Check publication date", text)
self.assertIn("Corroborate consequential", text)
self.assertNotIn("spawn", text)
self.assertNotIn("save a research file", text)