Evidence First

Evidence First

Check uncertain claims. Follow clear choices.

Workflow

1. Read the whole statement and work out whether the user is unsure or has made a choice. The phrases below are examples, not a fixed matcher.
2. Treat questions and tentative wording such as "I think", "I remember", or "I don't think" as something to check. Verify before answering or acting on it.
3. Treat clear preferences and limits such as "I don't want this", "reduce the scope", "this is overblown", or "this is going too far" as decisions. Follow them without asking the user to confirm them again.
4. A decision can still be based on a mistaken reason. Keep the decision, check the reason, and correct it plainly when it matters. Do not use that correction to reopen the decision.
5. Use the source that owns the answer:
   • for repository behaviour, read its code, tests, or docs, or observe it directly;
   • otherwise use current official docs, source, specifications, first-party APIs, or maintainer records.
6. When the owning evidence is outside the active repository, retrieve the primary source before answering or acting. Prefer an advertised local reference when it contains the owning docs or source; otherwise use the available documentation, source, API, or web-search tool. Loading this skill, planning to search, inspecting consumer configuration, or relying on supplied context does not satisfy that retrieval. If no owning source is accessible, say the claim could not be verified instead of filling the gap from memory.
7. Briefly name the source in the answer. Link external sources; name the local file, test, or symbol for local evidence.
8. If the evidence leaves one sensible path, continue. If it creates a real choice that changes the work, use the client's structured question capability when available, otherwise ask concisely in chat.
9. Load research when the answer needs deeper external evidence, competing views, or several trusted sources.

Evidence Rules

• Do not treat the user's memory, the agent's memory, supplied context, common practice, or repeated prior use as proof.
• Do not browse when local evidence owns and answers the question.
• Do not substitute local configuration or observed usage for external product contracts, defaults, or supported behaviour.
• Do not use secondary commentary when a trusted primary source is available.
• Do not argue with a clear preference merely because another option is more common or the agent prefers it.