Watch the explanation. Practice the skill.
Same model, different harness
Explain how tools, permissions and checks change a workflow.
Captions appear here during playback.
Same model, different harness
Explain how tools, permissions and checks change a workflow.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Illustrated teaching example • Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · The surrounding system changes the work.
Two systems can use the same model and still behave differently. Context selection, tools, permissions, retries, and verification all affect the workflow. This illustrated comparison uses constructed behavior. It is not a measured comparison of provider quality or a live model benchmark.
What appears on screen
Constructed comparison · same model assumption
0:22 · Configuration A: drafting only.
In the first configuration, the system receives supplied text and drafts an answer. It has no file tools and cannot create a workbook. If asked to save a spreadsheet, it can explain a plan or produce text, but it must not claim to have written a file.
What appears on screen
Available: Supplied text + generated answer Unavailable: File reads, writes and execution An instruction does not create a missing capability.
0:41 · Configuration B: bounded tools.
In the second configuration, the harness exposes an approved read tool and a narrowly scoped output tool. It validates arguments, enforces access, and checks the resulting artifact. These capabilities add useful work and new failure modes. The model still cannot legitimately bypass the application’s permission rules.
What appears on screen
Model request Validate arguments Authorize scope Execute tool Check artifact Tool availability is not unrestricted authority.
1:06 · Observe the actual action.
A request to write a report is not proof that the report exists. Inspect the tool result and the output path, then check the artifact’s content. A tool error must remain an error in the final response. Describe partial completion accurately rather than converting it into a success claim.
What appears on screen
REQUEST: write_report: approved output path CHECK: arguments and scope accepted RESULT: artifact produced in fixture VERIFY: content checked against source Simulated trace · fictional fixture
1:27 · Tools do not remove the need for verification.
Suppose the file exists but contains an invented savings number. The write succeeded while the task still failed. Verify both the action and the content. A correct artifact needs supporting evidence, and a correct summary must distinguish successful steps from unresolved requirements.
What appears on screen
File exists → therefore the task passed? Execution: File created Content: Invented savings Decision: Repair before completion
1:49 · Compare complete workflows.
For a real comparison, hold the task and source fixed and record model configuration, tool permissions, checks, retries, latency, cost, and human correction. Use representative repeated cases. Do not attribute all differences to the model when the surrounding system changed.
What appears on screen
Inputs: Same task and source Controls: Tools and permissions recorded Evidence: Artifact and failure checks Costs: Tools, retries and human review
2:11 · Run the offline workflow lab.
Use the downloadable offline lab in the curriculum. Compare the drafting policy with the bounded tool policy, inspect denial and failure cases, and explain what each setup can actually produce. The lab is a teaching simulator. It is not a production sandbox or a live same model benchmark.
What appears on screen
What changed because of the harness? Permitted actions. Visible tool results. Independent artifact checks. Your evidence: a configuration comparison with limitations.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →