Daily Workflow

An investigation rhythm you can run every day

TraceMind pays off when it becomes a habit, not a last-resort tool. Here is a professional loop that keeps investigations tight and repeatable.

The investigation habit¶

The loop runs continuously. Follow the flow on the left, track your position in the step list, and read the detail for the active stage below.

01 Frame the question
02 Reuse the Scenario
03 Record a clean take
04 Explore with intent
05 Capture on MindBoard
06 Decide the next move

Step 1 of 6

Frame the question

Write the question before you press record, such as what writes currentAmmo after reload cancels. A clear question keeps Scenarios tight and Reports readable.

Choose the right surface¶

Each question has a home. Open the surface that answers it, instead of touring every panel.

Where did this happen in the hierarchy? Tree How did execution travel? Flow When did it spike? Timeline What did this value do? Watch Studio Why did this write happen? Causal Flow What did the environment do? Probe Map How did this method get called? Method Flow How did this exception unfold? Exception Flow

Team practices that scale¶

Name and organize

Name Scenarios after systems, not ticket IDs alone. Keep one MindBoard per investigation theme when possible.

Share and tighten

Export HTML or Markdown when a Report must leave Unity, use Scenario Console export for instrumentation messages, and prefer tightening the Scenario over recording longer.

Shared playbooks

A good Scenario is a reusable lab setup. After a few investigations, new team members can reproduce and inspect without reinventing instrumentation.

Use Home as your launchpad¶

Continue

Jump straight back into the last useful surface.

Recent Reports

Reopen recordings you were just working with.

Signals

See activity density on your recent work.

Recent Activity

Keep momentum across sessions.