Watch the explanation. Practice the skill.
Capstone: ship something real
Build one small application that another person can inspect.
Captions appear here during playback.
Capstone: ship something real
Build one small application that another person can inspect.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based 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 · What you will learn
Build one small application that another person can inspect.
What appears on screen
Build one small application that another person can inspect.
0:06 · The idea
Choose the simplest pieces the task needs. Show how inputs are checked, results are verified and denied actions are handled. A useful demo does not need every AI feature.
What appears on screen
Choose the simplest pieces the task needs. Show how inputs are checked, results are verified and denied actions are handled. A useful demo does not need every AI feature.
0:20 · One useful term
Mock. A controlled stand-in used for testing instead of a live service.
What appears on screen
A controlled stand-in used for testing instead of a live service.
0:28 · A worked example
The record-to-draft demo needs input checks, a mock generator, source checks and a reviewer. It may need neither an agent nor document search. A denied record should produce no draft.
What appears on screen
The record-to-draft demo needs input checks, a mock generator, source checks and a reviewer. It may need neither an agent nor document search. A denied record should produce no draft.
0:44 · Your turn to think
Should the demo hide denied access to make it look successful? Pause and decide before continuing.
What appears on screen
Should the demo hide denied access to make it look successful? Pause the video if you need more time.
1:01 · Why this answer works
No. Show the failure path clearly. Label mocks and keep claims limited to what the offline demo proves.
What appears on screen
No. Show the failure path clearly. Label mocks and keep claims limited to what the offline demo proves.
1:11 · Check 1
Justify each component.
What appears on screen
Justify each component.
1:16 · Check 2
Include success and failure cases.
What appears on screen
Include success and failure cases.
1:22 · Check 3
Give a reviewer repeatable run instructions.
What appears on screen
Give a reviewer repeatable run instructions.
1:27 · Now try a different case
Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →