Context and prompts

What must the model see to produce an acceptable answer?

Make the model's instructions, sources, history, tools, and output rules visible before tuning words or examples, so missing context is not mistaken for a prompt problem.

AI VISTA / DECISION01 / 03
WORKING DECISIONSeparate missing facts from unclear instructions; they need different fixes.
01INPUT
02CHECK
03BOUNDARY
RETURN TO THE REAL TASK

DECISION BRANCH

Do not begin with the tool name.

  1. ASK FIRST

    Is the missing piece a fact, a standard, or model capability?

  2. IF

    The result is verifiable and the failure cost is bounded, expand carefully.

  3. OTHERWISE

    Narrow the action, keep the human handoff, and preserve recovery.

WORKED CASE

A contract summary keeps missing renewal terms in the annex.

The model receives a master agreement, two amendments, and an internal review policy, but file versions and precedence are unstated. The output looks complete while a renewal term comes from a superseded annex.

WORKING ARTIFACTA context-flow map connecting source, selection, precedence, and output fields.
01WEAK SHORTCUT

Keep lengthening the prompt with ‘be accurate’ and ‘do not omit anything,’ then place every file into one undifferentiated context.

02BETTER JUDGMENT

Map the context first: current agreement, valid annexes, internal policy, user question, and output fields. Declare precedence, missing states, and the source location expected for each conclusion.

03ACCEPTANCE

Test 12 agreements containing version conflicts. Amount, date, renewal, and termination fields point to valid clauses; uncertainty is explicitly held for review.

ENTRY & EXIT SIGNALS

Know when to enter—and when the decision is good enough to leave.

A topic is not an endless knowledge directory. Entry signals tell you whether the problem belongs at this layer. Exit signals decide whether to continue instead of substituting time spent reading for work completed.

AI VISTA / DECISION STATUSContext and prompts
01ENTER HERE
  • The same task omits different content across inputs
  • Source conflicts produce unexplained choices
  • A longer prompt does not reduce consequential failures
02LEAVE WHEN
  • Every output field maps to required context
  • Source precedence, missing states, and format are declared
  • Failure is no longer summarized as a bad prompt

BOUNDARY

What this topic page will not do

This page makes inputs and instructions visible. It cannot supply facts that were never provided or replace source governance.

01Do not hide missing material with a longer prompt02Do not treat citation-shaped text as evidence03Do not build RAG before source precedence and version rules exist
When every output field maps to an input, rule, or explicit missing state, turn the context map into evaluation cases.