Architect's Field Kit 07
The Direction Record
Show how the builder directed, checked, changed, and understood the work
- Audience
- Builders, parents, and future reviewers
- Format
- 11 minute field read
- Use
- Capture at each milestone, not as a scramble after the build is finished.
Field purpose
A practical guide to capturing prompt trails, decision notes, check records, and understanding evidence without exposing unrelated personal information.
Field panel 01
evidence
The four-part record
A finished artifact shows what exists. The direction record shows who understood and steered it.
- Brief
The intended outcome
Who it was for, what useful meant, and the limits set before building.
- Trail
The prompt trail
The key prompts, AI outputs, pushback, and corrections that changed the work.
- Checks
The check record
Tests, sources, user reactions, caught errors, and what changed because of them.
- Voice
The builder's explanation
A short explanation of choices, failures, and what they would do next.
Field panel 02
steps
Capture the prompt trail
Save only the exchanges that materially directed the build.
- Mark
Flag turning points
When a prompt changes direction, fixes an error, or creates a useful decision, mark it immediately.
- Export
Use the provider's current export or print option
A PDF, text export, or clear screenshots can work. Interface names change, so use the provider's live help if needed.
- Trim
Remove unrelated material
Keep the build trail. Remove private chats, unrelated projects, names, account details, and other people's information.
- Label
Add a one-line reason
For each turning point, say what changed and why the builder accepted, rejected, or revised it.
Field panel 03
framework
Write the decision notes
A direction record becomes meaningful when the builder's judgment is visible between AI outputs.
- Decision
What did I choose?
Name the route, scope, wording, design, tool, or boundary selected.
- Reason
Why this route?
Connect the choice to the user, finish line, evidence, or constraint.
- Alternative
What did I reject?
Name one plausible alternative and the tradeoff that made it weaker here.
- Change
What would change my mind?
State the test, user reaction, or new information that would trigger a rethink.
Copy, adapt, direct
Ask me to explain one build decision in my own words. Challenge me on the strongest alternative, the evidence I used, and what result would make me choose a different direction. Do not supply my explanation.
Field panel 04
matrix
Build the check record
Every important output needs a check that another person can understand.
- Accuracy
Is it true or technically correct?
Open primary sources, recalculate, inspect code, or compare with a known case.
- Usefulness
Does it solve the real need?
Ask the named user to try it and describe where they got stuck.
- Safety
Can it cause harm or expose data?
Try strange inputs, remove private data, check permissions, and keep a human approval point.
- Fit
Is it clear and appropriate for the audience?
Test on the intended device and ask someone in the audience to explain what they think it does.
Field panel 05
checklist
Pass the interrogation
The builder should be able to explain the work without an AI window open.
- Why
Why this build and this user?
Explain the need in plain language.
- Break
What broke first?
Describe a real failure and how it was isolated.
- Check
How do you know it works?
Name the test and evidence, not a feeling.
- AI
What did AI do and what did you do?
State the division honestly and specifically.
- Next
What would you change next?
Show that the builder can see beyond the finished version.
Keep it in the field
Print it, mark it, return to the build.
The PDF carries the same source edition as this web guide and is designed with A4 and US Letter-safe print margins.