← Files Argovance Skill OSARCHIVED FILE
skills/control-deep-research/references/research-protocol.md
3.21 KB · Oct 2, 2026 · 00:34 UTC
# Research protocol ## Claim ledger Track material claims with: | Field | Meaning | |---|---| | Claim | Exact proposition being supported | | Status | VERIFIED / SUPPORTED_INFERENCE / DISPUTED / UNVERIFIED / UNKNOWN / OUTDATED | | Source | Direct page or record actually consulted | | Authority | Primary / institutional / secondary / community | | Date | Publication and relevant event/effective date | | Scope | Jurisdiction, population, product version, or conditions | | Confidence | High / medium / low with a brief reason | | Verification tests | Entailment, authority, scope, freshness, independence, contradiction, completeness | | Independent corroboration | Independent source/evidence lineage or not available | Status and confidence are separate. High confidence cannot promote an inference or unverified claim to `VERIFIED`. Use the canonical definitions and source-admissibility rules in [evidence-integrity-gate.md](evidence-integrity-gate.md). ## Research stopping criteria Stop when: - every decision-critical question has sufficient evidence or is explicitly unresolved; - important claims have current authoritative support; - major contradictions are represented; - additional sources repeat known evidence without changing the decision; - the user’s requested depth and time constraints are met. ## Production-method research When the research will inform a material method decision, classify the reference evidence as `REFERENCE_QUALITY`, `MECHANISM_VERIFIED`, `APPLICABILITY_TO_PROJECT` and `EVIDENCE_LIMITS`. Pass those fields, source/guidance version, actual verification date and first-party guidance type into the existing scoped method record owned by the shared [decision-authority model](../../../shared/expert-system/decision-authority-model.md). Persist or explicitly deliver that record with a stable ID/revision for later reuse and targeted revalidation. Do not label an interesting reference as a verified mechanism, and do not decide or reopen the method from research evidence alone. For freshness-triggered research, use the canonical method-freshness fields and comparison loop in that same decision-authority model. Identify the changed claim, scoped source/version/date and observed validation context separately from vendor documentation. Return whether material change is evidenced, applicability, unresolved limits and the authorized next step; preserve the closed method when no material change is established. Persist only under existing write authority, with prior revision retained. Do not stamp a whole method/toolchain CURRENT from one checked page or create a new production-knowledge register. ## Red flags - Undated pages for fast-changing facts. - Vendor claims presented as independent evidence. - A secondary article contradicting a newer primary source. - Citations that support a nearby topic but not the actual claim. - Precise numbers without methodology, population, currency, tax basis, or date. - “Latest” conclusions without an explicit research date. - Multiple pages that all repeat the same original report but are counted as independent confirmation. - Official commercial claims presented as independently proven performance or quality. - The requested conclusion determining which evidence is admitted.
SHA-256: 470045bde388f2cf6f47e6f30708e486e85a8d9f9100fe87a8f23738e0a0c04f