Skip to main content

Truth and verification

The SOP turns "don't guess" into a workflow. A claim is either verified, labeled unknown, or not used.

This page is the verification contract behind implementation summaries, setup claims, reviews, and handoffs.

Mental model

SOP sectionContract
2.0 Compatibilityclassify and state compatibility before edits; no unrequested shims, aliases, wrappers, or deprecation paths
2.1 External Truthinspect local source, binaries, versions, docs, and locally-verifiable guesses before relying on behavior; hypotheses cannot gate downstream steps
2.2 Runtime Truthsetup questions require source config → rendered config → consumer → safe live probe
2.3 Completionstop only after locally-verifiable unknowns are resolved
2.4 Complete Artifactscompacted/sliced/capped output is an index; recover raw context before relying on content or composing human-visible output
2.5 Self-Report Skepticisma model's own rationale, chain-of-thought, done, status, and plan are hypotheses about the process, not evidence

Self-report skepticism also applies to any sub-agent, reviewer, or verifier report. Verify the outcome against an independent signal.

Using it

Unknowns are resolved in this order:

  1. local probes.
  2. local source/tests.
  3. official docs fetched live.
  4. user questions.

When a public cloneable codebase can answer a web/source question, inspect it locally with rg, file reads, and git log.

Compacted output without full recovery is a hypothesis, not a fact.

Evidence ladder

Question typeRequired evidence
CLI behaviorbinary path and provenance, then --version, --help, or source
Library behaviorexact package/version from lockfile, import path, and local implementation when available
External claim (web/docs)primary-source URL and exact supporting quote; numeric literals verbatim in the quote; per-claim verification before multi-source synthesis
Runtime setupsource declaration, applied config, consumer implementation, safe live probe
Build/test failurefull output when compacted markers or capped lists appear
Review judgmentbase truth, change truth, and smallest safe repro/probe when needed
Freeform completioninline evidence by default; ,proof only for a requested receipt, auditable security/auth, data-migration, or destructive effect, or named handoff/resume consumer; never as a late wrapper

Reference: compatibility line

Every implementation summary includes one of:

ValueMeaning
noneno compatibility path added/removed
removed (requested)user asked to remove/replace old behavior
kept existing (requested)user explicitly asked to preserve old behavior