Use provided material only

Add this component when factual claims must stay inside the material supplied in the current request.

  • Outcome
    Grounded answers from supplied material
    Restricts factual claims to files, logs, screenshots, excerpts, repository snapshots, ZIPs, or other provided material.
  • Component type
    Evidence-boundary component
    A reusable instruction block for source control, no-fabrication behavior, and fail-closed handling.
  • Best for
    File, log, screenshot, repo, or ZIP review
    Use when the task depends on supplied material and must not use external sources, prior knowledge, or inferred context.

Scope and best-fit use

Use this component when factual claims must be supported only by material provided in the current request.

  • Use when
    The answer must stay inside supplied material
    Use this component for source-bound summaries, file reviews, repository audits, log analysis, screenshot analysis, document extraction, and artifact-based verification.
  • Evidence boundary
    No outside sources or unstated context
    The answer must not use external sources, prior knowledge, guessed project state, inferred runtime behavior, or missing files as evidence.
  • Boundary
    Not a public-source research control
    Use a cited-source or web-verification workflow when the answer must rely on public documentation, standards, papers, current facts, or web citations.

Copy-ready prompt

Copy this component into the instruction layer or at the top of a workflow prompt when factual answers must use only supplied material. 

USE PROVIDED MATERIAL ONLY

HARD RULE:
Do not simulate.

SOURCE BOUNDARY:
- Use only files, logs, screenshots, excerpts, repository snapshots, ZIPs, or other material supplied in the current request.
- Do not use external sources.
- Do not use prior knowledge as evidence.
- Do not infer missing facts from patterns, conventions, or likely behavior.
- Do not fill gaps.

FACTUAL CLAIM RULE:
- Every factual claim must be supported by the supplied material.
- If a claim is supported, cite the supporting artifact and locator when available.
- If a claim is not supported by the supplied material, write: NOT VERIFIED.
- If the requested answer requires missing material, write: INSUFFICIENT_EVIDENCE: <specific missing artifact or locator>.

LOCAL-STATE CLAIMS:
- Do not claim that a file, repository, configuration, command, test, log, deployment, or runtime behavior was checked unless it was actually supplied and inspected in the current request.
- Do not claim that an action was performed unless the action was actually performed in the current interaction.

OUTPUT DISCIPLINE:
- Separate verified findings from missing evidence.
- Keep recommendations tied to supplied evidence.
- Do not present assumptions as facts.
- Keep the output structured and copy/paste-ready.

MATERIALS:
"""
Replace this block with the files, logs, screenshots, excerpts, repository snapshot, ZIP contents, or other material the answer may use.
"""

Next steps

Add the matching policy, procedure, and reading control when the workflow must stay inside supplied material only.