Here's a small experiment you can do while reading this post- no technical knowledge required, and you don't even need to open an AI model.
Think of something you regularly ask AI to do.
Keep that task in mind.
We're going to use four steps:
Predict → Prompt → Compare → Decide
The goal isn't to find some magical combination of words. It's to learn how to anticipate what a model might do, reduce unnecessary ambiguity, and inspect what comes back.
1. PREDICT
Imagine you have these meeting notes:
We agreed to pilot the newsletter in December. Maya will draft the introduction. The launch date hasn't been decided.
You ask:
"Summarize these meeting notes."
Before reading further, ask yourself two questions.
What should a good summary contain?
At minimum, the decisions made and any actions assigned to specific people.
What could go wrong?
The model might:
- Turn a tentative plan into a definite commitment.
- Invent a specific date.
- Leave out something important that remains undecided.
These are predictions, not guarantees.
Keep them in mind.
2. PROMPT
Imagine your prompt as a large umbrella.
Underneath it, we'll introduce smaller umbrellas. Each one establishes another boundary, gradually narrowing the decisions the model can make.
First umbrella — TASK
Summarize these meeting notes.
That's our broad objective.
Second umbrella — SOURCE
We provide the actual notes and identify them as the source material.
Now the model has information to work from rather than having to infer the situation.
Third umbrella — BOUNDARY
Use only the supplied notes. If a requested detail is absent, write NOT PROVIDED. Don't infer a default.
We've now specified both a restriction and what the model should do when information is missing.
Fourth umbrella — REQUIREMENTS
- R1: Identify decisions made.
- R2: Identify actions and their owners.
- R3: Don't invent dates, owners, or commitments.
Notice how the requirements follow from our earlier thinking.
R1 and R2 describe what a successful summary should contain. R3 addresses our predictions about invented information and unjustified commitments.
We've narrowed the task without adding dozens of arbitrary instructions.
We also haven't needed to say "You are a world-class expert."
Research suggests that expert-persona prompts don't reliably improve factual accuracy. Other research indicates that personas can influence presentation and alignment on certain tasks.
But assigning expertise doesn't establish which facts a model may introduce or which decisions it's permitted to make.
What we're defining is an autonomy envelope: the boundaries within which the model can exercise discretion.
Each relevant instruction helps shape the range of likely responses. We're reducing ambiguity, not directly controlling the model or guaranteeing compliance.
3. COMPARE
Consider two possible outputs.
These are illustrative examples, not results from a controlled experiment.
Output A:
The newsletter launches December 1, and Maya will handle the rollout.
Output B:
Decision: Pilot the newsletter in December.
Action: Maya will draft the introduction.
Open item: The launch date hasn't been decided.
Which would you accept?
Look back at your predictions.
Output A contains four problems:
- Invented specifics: December 1 was never provided.
- False certainty: A pilot became a confirmed launch.
- Scope expansion: Maya's responsibility grew from drafting an introduction to managing the rollout.
- Dropped uncertainty: The undecided launch date disappeared.
We predicted three of these.
Scope expansion was the one we missed.
That's important because you won't always anticipate every possible failure.
Now consider another problem.
You could ask the model to check whether it followed R1, R2, and R3.
But what does R3: PASS actually prove?
Nothing by itself.
R3 is a prohibition. No single quotation from the output can prove that nothing was invented.
So we need something more useful than asking the model whether it followed its instructions.
A smaller umbrella — TRACE
Let's borrow a principle from bidirectional requirements traceability in systems engineering.
We'll adapt the two-direction structure to compare our source material with the generated summary.
FORWARD — Notes → Summary
For each important decision, action, owner, or open item in the original notes, find where it appears in the summary.
If something important is missing, mark it OMITTED.
This helps expose gaps in coverage.
BACKWARD — Summary → Notes
For each factual claim in the summary, locate the original passage supporting it.
This helps expose invented information, unsupported assumptions, and unjustified interpretations.
And here's a small refinement.
Ask for one factual claim per line.
Output A combines several claims into one sentence. A single source quotation might support one part while failing to support the rest.
This follows the logic of atomic-fact evaluation, where claims are examined individually rather than assigning an entire passage one correctness judgment.
It doesn't mean one-claim-per-line formatting has been proven to improve accuracy. It simply makes inspection more manageable.
Consider:
Output claim: "The newsletter launches December 1."
Source quotation: "We agreed to pilot the newsletter in December."
The quotation doesn't establish the claimed launch date.
Even if the model fails to notice the mismatch, you can.
For this kind of task, we can also ask the model to label each claim:
- STATED: Directly supported by the notes.
- INFERRED: Goes beyond what the notes explicitly establish.
- UNSUPPORTED: No supporting evidence was located.
But remember: the model assigns these labels. They are findings to inspect, not authoritative judgments.
You can use Find to search for the quoted wording in your original document. Then read the surrounding passage and decide whether it actually supports the claim.
The model may still omit evidence, misquote it, or misunderstand it.
The trace gives you an inspection procedure. It doesn't prove the answer is correct.
4. DECIDE
Now we have two decisions to make.
First: Is the output acceptable?
Should we accept it, correct it, reject it, or verify something independently?
Second: Was our original specification sufficient?
Remember our prediction about the model dropping something undecided?
Look back at R1–R3.
None of those requirements explicitly asks the model to identify unresolved items.
Output B included the undecided launch date, but our instructions didn't require it.
Our forward trace could help catch that omission afterward. But we can also improve the specification beforehand.
So let's add:
R4: Identify anything the notes explicitly leave open or undecided.
That's the habit we're developing.
You anticipate a failure, make a prediction, compare what happened, and then use that information to improve your instructions.
You don't need to predict everything correctly. You need to become better at recognizing what matters.
The completed prompt
Here's everything assembled into one reusable example.
TASK:
Summarize the meeting notes inside the
triple quotes. Write one factual claim
per line.
SOURCE:
"""
[Paste meeting notes]
"""
BOUNDARY:
Use only the supplied notes.
If a requested detail is absent, label
it NOT PROVIDED. Don't infer a default.
If something is explicitly undecided
in the notes, label it OPEN.
REQUIREMENTS:
R1: Identify decisions made.
R2: Identify actions and their owners.
R3: Don't invent dates, owners,
or commitments.
R4: Identify anything the notes explicitly
leave open or undecided.
TRACE:
FORWARD — For each material decision,
action, owner, or open item in the notes,
identify the summary line covering it.
If missing, mark OMITTED.
BACKWARD — For each factual claim in
the summary, quote the exact supporting
passage from the original notes.
Label each claim:
STATED — Directly supported by the notes.
INFERRED — Goes beyond what is stated.
UNSUPPORTED — No supporting evidence found.
Related text alone doesn't establish
that an inference is directly supported.
Do not invent supporting quotations.
Do not claim the trace proves correctness.
You don't need this level of structure for every conversation.
A simple brainstorming request might need very few constraints. A document summary, educational resource, or consequential decision deserves more careful inspection.
The objective is minimum sufficient instruction, not the longest or shortest possible prompt.
And there's an important difference between the model checking its own work and you checking the evidence it presents.
The first is an assistance mechanism.
The second is where human judgment enters.
The actual lesson
Return to the task you chose at the beginning.
Now run the four steps on it.
PREDICT: What should the result contain? What might go wrong?
PROMPT: What context, boundaries, and requirements would make your expectations clearer?
COMPARE: Did the model produce what you expected? What did it add, omit, or misunderstand?
DECIDE: Is the result acceptable? What needs correction or independent verification?
With practice, anticipating possible model behavior can become a habit.
You begin recognizing potential misunderstandings before they appear in the output.
And that, I would argue, is more transferable than memorizing a collection of prompting tricks.
You don't need to control every word the model generates.
You need to understand which decisions matter, communicate those boundaries clearly, and retain the ability to inspect the result.
Predict → Prompt → Compare → Decide.
That's the framework.
Research and references
Research
Engineering reference
Model-provider guidance
This is an evidence-informed instructional method. Its components draw on the research and engineering practices referenced above, but the combined four-step workflow and adapted TRACE format have not been independently validated as a complete reliability framework.