Prompt to separate observations, verified claims, and evidence gaps

Add this reusable component to a technical analysis prompt when the evidence status of each finding must be explicit. It requires separate sections for grounded observations, verified claims with citations, and NOT VERIFIED items, followed by an internal consistency check.

  • Outcome

    Structured technical analysis

    Requires the response to separate grounded observations, verified claims, and not-verified items.

  • Component type

    Prompt component

    A reusable analysis-control instruction, not a standalone workflow.

  • Best for

    Review and diagnostic tasks

    Use for technical review, debugging, comparison, artifact review, and higher-depth analysis tasks.

Scope and best-fit use

Use this component when the assistant should produce objective technical analysis and explicitly separate supported findings from unsupported items.

  • Use when

    The task requires analysis, not only an answer

    Use when the response needs grounded observations, verified claims with citations, and explicit NOT VERIFIED items.

  • Placement

    User or workflow instruction layer

    Place this block near the task instruction when a specific run needs a stronger analysis pass.

  • Boundary

    Does not replace source retrieval

    This component structures the analysis. It does not by itself require web retrieval, artifact scanning, or exhaustive source discovery.

Copy-ready prompt

Copy this component into a user prompt or workflow prompt when the answer must include a structured analysis pass.

Prompt to separate observations, verified claims, and evidence gaps
DEEP ANALYSIS

- Provide an objective technical analysis (no fluff; no simulation/fabrication).
- Separate output into: (1) Grounded observations, (2) Verified claims with citations, (3) NOT VERIFIED items.
- Run an internal consistency check: no contradictions, no invented data, and all referenced paths/links exist.

Next steps

Use these companion components when the task also requires pre-answer analysis, no-fabrication behavior, public-source retrieval, or artifact coverage.