Help Center

Course overview

Come back tomorrow

Open the saved task and pick up where you left off.

This full-text reading copy does not save answers. Open the interactive lesson for saved browser notes.

Open the saved task

Use the same practice project and Harness environment from lesson 2.

In the terminal from lesson 2, run this command to open the current briefing for your saved task.

saved task status

macOS/Linux — Bash or Zsh

"$COURSE_PYTHON" -m attune_harness status "$PRACTICE/task" --format markdown

Windows PowerShell 5.1 or 7

& $COURSE_PYTHON -m attune_harness status "$PRACTICE/task" --format markdown
Start from a new terminal

Open a terminal in the extracted course folder that contains practice.py. Use the path commands for your shell below before checking status. In the interactive lesson, select your shell in Command shell. These select the existing environment; they do not reinstall packages or run a build.

saved course paths

macOS/Linux — Bash or Zsh

COURSE_WORK="$(pwd -P)"
COURSE_PYTHON="$COURSE_WORK/.venv/bin/python"
PRACTICE="$COURSE_WORK/practice"

Windows PowerShell 5.1 or 7

$COURSE_WORK = (Get-Location).Path
$COURSE_PYTHON = Join-Path $COURSE_WORK ".venv\Scripts\python.exe"
$PRACTICE = Join-Path $COURSE_WORK "practice"

If you selected your own compatible environment, set COURSE_PYTHON to that interpreter instead. If you used a different practice directory in lesson 2, set PRACTICE to its saved full path instead of the default practice folder before checking status.

Find Next useful step. For a completed build, it points you to the saved checks and reviewer findings. Copy the text under Your reply to the assistant into your conversation if you want help picking up the task.

Finish Build your first report to create a task. For a preview, read the archived 1.7.0 check summary.

Find the information you need

Find the saved task, the report and your lesson notes in their respective places.

Task and checks
$PRACTICE/task holds the saved scope, execution and checks.
Input and result
Open $PRACTICE/project/data/activity.csv and $PRACTICE/activity-report.html.
Lesson notes
These stay in the same browser profile and site while local storage is available.

Read the current briefing

Check that the task and report match the project you meant to reopen.

  1. Read Goal and Current position.
  2. Check the project, task ID and revision under Snapshot identity.
  3. Follow Next useful step. If the task path is missing, find the original practice/task folder and run the status command again.
Optional assistant prompt to locate the task

saved-task inspection prompt

Help me find the saved reporting task from lesson 2. Confirm its path and revision, then show me its current status and next useful step. Stop after inspection.

Read the checks and findings

Use the evidence saved with this run.

Find probe:change and probe:final under Host checks. Read their recorded outcomes and check Reviewer findings for open concerns. The two probes exercise the same reporting tests at different points in the build.

Use the saved outcomes to decide whether to inspect the report or look into a reported problem.

A saved task is completed and its chosen checks passed. What should your return brief say?

State which checks passed, inspect remaining findings and retain the limits of that evidence. A completed workflow and passing selected checks are useful evidence. They do not erase findings or establish untested behavior.

State that all possible report behavior is correct, because completed means no further concern is possible. Completed describes the recorded workflow. Read its checks, findings and limits before deciding whether any further action is needed.

Add context if it helps

Start with the generated briefing. Add a short note for a decision or observation that lives outside the task.

For example, record “Check the Orion subtotal before handing off the report” beside the task path in your project notes. The next session can then find the task and understand what you wanted to check.

Optional assistant prompt for a stopping note

stopping-note prompt

Draft a short note for this task and revision. Include the decision or observation I want to retain, its evidence and the next action. Show me the note before saving it.

For a structured note tied to a task revision, see the pause-and-return procedure.

Choose the next action

Use the result to decide what you need next.

Read the existing report to find the Orion total. If you need a report containing only Orion rows, save that idea for Make it work for your needs.

For the completed practice task, continue by checking the report against its input.

Record your next decision

Capture one next step if you want to keep it with your lesson notes.

Your current position, evidence and next decision

Write your answer in your own notes, or use the interactive lesson.

This optional note stays in your browser profile and site. For context you want the assistant to use later, include it with the task path in your project handoff.

Continue with the report review

Bring the saved briefing and the HTML report to the next lesson.

Keep $PRACTICE/activity-report.html and the latest briefing open. If you still need a result, return to Build your first report.

Next: Open Decide whether to trust the report.