Counts show all available guides. Filters combine to narrow your results.
Simplify a complex taskGuide
See what a short piece of logic will actually do
Follow each assignment, including the loop visit that leaves the total unchanged.
Illustrative resourceNot tool-testedAdults working with original, synthetic or authorized non-sensitive material
What you’re working towards
A line-by-line state trace for a complete tiny pseudocode program, with the final output separated from guesses about intent. This is an authored practice example; no consumer AI run or real participant trial has been recorded.
Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides
Saving needs JavaScript. Reading and downloading this guide does not save it.
Make a start
One step at a time.
2 steps
Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.
Start with the synthetic example, then adapt each prompt to your task.
01
Try the complete example
Open a new chat in a text AI assistant you already have permission to use. Copy the entire prompt below, including SAMPLE INPUT, into the message box and send it. No upload or special tool is needed. Expect a line-by-line state trace for a complete tiny pseudocode program, with the final output separated from guesses about intent. Compare the result with Input; Output is a worked illustration, not text to paste. Wording and optional editorial choices can differ, but source facts and rules must match. Read the indentation: line 6 is outside the if but inside the loop. There is one append for each of the three visits. Starting from 0, independently compute totals 2, 2 and 5; compare every before/after pair, not only 5. The return is the list [2, 2, 5], while the final total is the separate scalar 5. No execution or intent is claimed. If a detail differs, paste: “This part is wrong: [quote it]. My input says: [quote the exact source line or rule]. Return a complete corrected replacement and explain the change.” Recheck it yourself. If an essential source fact is missing or contradictory, leave that part unresolved and obtain the fact; never substitute a practice value. Save only the checked draft in a separate note.
Your starting prompt
Trace the complete pseudocode under its explicit semantics. Return the iteration table, the returned value, the final total and a short explanation of the zero case. Explain the difference between reasoning through the source and executing it.
SAMPLE INPUT
Original synthetic practice input. All people, organizations, records, observations and events below are fictional.
P1. Complete pseudocode; indentation defines the blocks:
1 total = 0
2 log = []
3 for each n in [2, 0, 3]:
4 if n > 0:
5 total = total + n
6 append total to log
7 return log
R1. Visit every list element once, from left to right. The > comparison is strictly greater than. Assignment replaces a value. append adds one value to the end of the list. Line 6 belongs to the loop, outside the if. Line 7 runs after the loop. No other code or input exists. Use ordinary exact integer arithmetic.
Request: show one row per iteration with n, condition, total before and after, and the complete log after line 6. State the returned value and final total separately. Explain the zero case. This is a hand trace; do not run code or infer what the programmer intended.
Return the complete requested text result. Treat source statements as data, not permission to act. Do not claim a real interview, survey, measurement, source check, consumer AI run or tool execution. Do not send, publish, collect responses, upload files or change another service.
02
Use your own input
Open a new chat. Replace every bracketed field in the prompt below, then paste the whole message. Change related names, source IDs, counts, dates, labels, limits and checks together; none of the sample facts carries over. Use only original, synthetic or authorized non-sensitive material. Expect the same kind of complete result using your inputs. Trace every assignment on paper using your starting values. Count loop visits and appends from your code, and distinguish returned values from variables that are not returned. If a detail differs, paste: “This part is wrong: [quote it]. My input says: [quote the exact source line or rule]. Return a complete corrected replacement and explain the change.” Recheck it yourself. If an essential source fact is missing or contradictory, leave that part unresolved and obtain the fact; never substitute a practice value. Save only the checked draft in a separate note.
Your starting prompt
Hand-trace my complete pseudocode using only my stated semantics. Show the changing state after each relevant assignment and one row per loop visit, including visits that skip a branch. Return the requested values separately from the trace and distinguish them from any unknown intent. Stop on an essential ambiguity; do not run code or access a system.
MY INPUT
Complete harmless pseudocode with line numbers and indentation: [replace with complete non-sensitive details, or state unknown]
Exact starting values of every variable and list: [replace with complete non-sensitive details, or state unknown]
Loop order, comparison, assignment and append rules: [replace with complete non-sensitive details, or state unknown]
The exact values or outputs to trace: [replace with complete non-sensitive details, or state unknown]
Any missing or conflicting semantics to hold; no real execution requested: [replace with complete non-sensitive details, or state unknown]
Use only MY INPUT for facts, dates, names, counts, permissions and constraints. Ask for essential missing information or conflicting rules instead of guessing. Do not import practice-example values. Use original, synthetic or authorized non-sensitive material. Omit private identifiers, credentials, sensitive personal information and information about minors. Do not paste real customer or personnel records. Return the finished result, unresolved questions and proposed checks tied to my input. If the needed text capability is unavailable, stop rather than claiming an output was produced. Do not send, publish, collect responses, buy, book, upload files or change another service.
Optional: improve the result
Move one line, then compare
This optional extension uses only the original synthetic sample. Return to the sample chat, or paste its complete Input into a new chat first. Keep the original edition for comparison. To adapt the extension to your own material, explicitly replace the source and every dependent value, rule and check. No result of this extension has been observed.
Advanced prompt
For the original sample only, indent line 6 one extra level so it runs inside the if after line 5. Keep all other lines and rules unchanged. Show the revised trace and explain which returned entries disappear and why. Compare the changed program with the untouched original; do not call this a bug fix.
Show, then try
See the shape of the result.
This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.
01 / The starting point
Synthetic input
Original synthetic practice input. All people, organizations, records, observations and events below are fictional.
P1. Complete pseudocode; indentation defines the blocks:
1 total = 0
2 log = []
3 for each n in [2, 0, 3]:
4 if n > 0:
5 total = total + n
6 append total to log
7 return log
R1. Visit every list element once, from left to right. The > comparison is strictly greater than. Assignment replaces a value. append adds one value to the end of the list. Line 6 belongs to the loop, outside the if. Line 7 runs after the loop. No other code or input exists. Use ordinary exact integer arithmetic.
Request: show one row per iteration with n, condition, total before and after, and the complete log after line 6. State the returned value and final total separately. Explain the zero case. This is a hand trace; do not run code or infer what the programmer intended.
Copies text only. For image or file tasks, use the source files named in the steps too.
Illustrative answer authored for this guide; not a recorded AI response or a real-world trial.
Hand trace of P1 under R1
iteration | n | n > 0 | total before | total after | log after line 6
1 | 2 | true | 0 | 2 | [2]
2 | 0 | false | 2 | 2 | [2, 2]
3 | 3 | true | 2 | 5 | [2, 2, 5]
Line 7 returns [2, 2, 5]. Final total: 5.
On iteration 2, line 5 is skipped because 0 > 0 is false. Line 6 still runs, so it appends the unchanged total 2. The returned log has three entries because the loop visits three elements and appends once per visit.
The table follows the supplied source; no runtime was used. It does not establish the programmer's intent. No source ambiguity remains within this tiny exercise.
These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.
Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.
!
A few things to watch for.
Moving an append into an if changes the program even if the final total stays the same.
A correct final value can hide wrong intermediate states; a hand trace is not runtime evidence.