TRACE Learning Journal Foundations

Objectives

• Explain the five parts of TRACE
• Record one focused learning or troubleshooting difficulty briefly
• Bring the record to class, office hours, or tutoring for focused help
• Distinguish a TRACE journal from a separate learning check

Why Keep A Brief Journal?

• Difficult moments are easier to revisit when the details are still clear
• A short record shows the issue you encountered, the sources you reviewed, and what happened next
• The record gives a helper a useful starting point instead of only "it does not work"
• TRACE supports learning and troubleshooting; it is not proof of authorship
• It is not a tool for policing AI use or tracking every tool interaction

TRACE: Five Connected Steps

Keep The Entry Useful And Brief

• Choose one focused difficulty, not an entire project or week
• Write enough detail to restart the work or explain the issue to someone else
• Create an entry when a difficult problem would benefit from a record
• There is no daily or weekly entry quota
• Bring the entry to class, office hours, or tutoring when you want focused help
• Leave out passwords, access keys, and unnecessary personal information

Journal And Learning Check Are Different

One does not replace the other

TRACE Example: A File Upload Is Rejected

• Target: Why does the course site reject my report with Unsupported file type?
• Research: Read the exact message, review the submission instructions, and confirm that the required format is PDF
• Attempt: The instructions require PDF, so export the document, open the exported file locally, and upload that file
• Consult: The PDF still fails after the researched attempt, so ask, "Which file detail should I inspect next?"
• Evaluate: Check that the corrected file uploaded and a receipt appeared, explain the relevant file requirement, and apply it next time; begin a new TRACE if another uncertainty remains

The entry preserves the evidence and result without becoming a full activity log

Turn A Vague Problem Into Focused Help

Instead of:

My upload does not work. What do I do?

Bring three useful details:

• The focused question created from the problem or uncertainty
• The credible sources you reviewed
• How you interpreted that research, the action you tried, and its result

Then ask one question about the remaining uncertainty

Knowledge Check 1/2

Knowledge Check 2/2

TRACE Ex. 1: Optional Git Push Walkthrough

Practice turning a rejected Git push into a five-part journal entry

• Optional practice: 5 minutes total
• Keep each response to one or two useful sentences
• See the optional slides below for Target, Research, Attempt, Consult, and Evaluate
• Do not create a real Git problem just to practice this example

Optional Practice: Target

Turn the encountered issue into a focused, researchable question:

Why did Git reject my push, and what needs to happen before I can push safely?

• Start from the specific problem, issue, or uncertainty
• Keep the question narrow enough to investigate

Optional Practice: Research

Explore credible sources connected to the question and interpret what they mean:

• Use the exact message as one source of evidence
• Note what the sources answer and what remains uncertain before attempting a fix

Optional Practice: Attempt

After interpreting the research, record the smallest reasonable action and its result:

• Git says the remote branch has newer work, so update the local branch before retrying the push
• If Git reports a conflict, resolve that separately before the final push

Optional Practice: Consult

Consult after the researched attempt does not resolve the issue or leaves a meaningful uncertainty:

git pull origin main reported a conflict in README.md. Which version should the final file keep?

• Share the useful Target, Research, and Attempt details
• Record the focused help you receive

Optional Practice: Evaluate

Evaluate the whole path: check the result, explain what it showed, and apply it next time:

The rejected push led to a pull, conflict resolution, and a successful final push. GitHub shows the commit. This shows why remote work must be integrated before a push. Begin a new TRACE if another focused question appears.

• State how you checked, explained, and applied the result
• If it reveals a new focused question, begin a new TRACE

Key Terms And Further Learning

• Target: The focused question formed from a specific difficulty.
• Attempt: A small action based on research, with its observed result recorded.
• Evaluate: A check of what worked, why, and what question remains.

Further Learning:

• Open the TRACE journal
• Download the Word journal template
• Download the Google Docs import-ready journal

Summary

• TRACE turns an encountered issue into a focused question, then moves through Research, Attempt, Consult when needed, and Evaluate
• One brief entry captures one focused difficulty; there is no daily or weekly quota
• The journal supports learning, troubleshooting, and focused help rather than proving authorship or policing AI use
• Evaluation checks, explains, and applies the result; it can also identify the next focused question for a new TRACE