Evidence boundary
No external sources or prior knowledge
This procedure is restricted to the files, logs, screenshots, or excerpts you provide.
Answer from the files you provide only (no external sources) — procedure
Step-by-step guide for answers based only on files you provide, with file references for each factual claim.
Use this procedure for files-only answers
Choose this procedure when the answer must come only from files, logs, screenshots, or excerpts you provide in the current request.
Traceability
Every factual claim needs a file reference
Each factual claim must point to a file and a location.
Fail closed
Missing evidence stops the answer
If required evidence is missing, the assistant must return the exact fail-closed response.
Canonical links
Open the linked policy, prompt file, and adjacent references that implement this procedure.
Related
Policy and prompt files for this guide
Open the policy linked to this guide and any prompt files used with it.
Prompt files (2) Hide prompt files
Common uses
These are the most typical tasks for an artifacts-only answer flow.
Explain a failure from uploaded logs
Use this path when the evidence already exists in the logs you attach.
Review an attached draft or screenshot
Use this path when the answer must stay inside the uploaded material only.
Analyze a repo snapshot or ZIP
Use this path when the repository or archive itself is the only admissible evidence boundary.
What you need before you run it
Prepare the evidence and traceability inputs before asking for work.
Input
Relevant files or excerpts
Provide the relevant files, logs, screenshots, or excerpts in the same request.
Locator
A way to cite exact locations
Provide filenames plus line range, page, or section references so the answer can cite exact locations.
Optional for large inputs
A full-scan component first
If you provide many files such as a repo or ZIP, you can add a full-scan component before asking for work.
Run the procedure
Follow these steps in order.
Step 1
Install the system prompt file
Copy and paste the linked system prompt file into your runtime.
Step 2
Provide the evidence in the same request
Attach or paste the files, logs, screenshots, or excerpts in the same request where you ask the question.
Step 3
Add deep scan for large repos or ZIPs
If you provided many files such as a repo or ZIP, optionally add this scan component at the top of your user message before asking for work:
Step 4
Require file + location references
Ask the question and require file + location references for factual claims.
Step 5
Fail closed when a core claim is unsupported
If a core claim cannot be supported by your files, the assistant must respond with the exact sentinel below.
Expected output
A correct run ends in one of these two outcomes.
Evidence-backed answer
An answer where each factual claim includes a file + locator reference.
Exact fail-closed sentinel
If support is missing, the answer must return the exact fail-closed sentinel instead of continuing.
Common mistakes
These are the most common failure points for this procedure.
Missing evidence
Asking for conclusions without attaching the relevant logs or files.
No locator system
Providing files but not providing any way to cite locations such as line numbers, pages, or sections.
Mixed evidence boundary
Mixing this procedure with web-browsing or public-citation requirements.