Workflows

Practical investigation workflows

These guides are end-to-end playbooks for common TraceMind investigations. Each follows the product as it exists today: no theoretical steps, only surfaces and actions you can perform in the Editor.

Choose your workflow

Situation	Guide
A value changed and should not have	Investigating a Value Change
Scene/object/coroutine/animator timing looks wrong	Investigating Runtime Object Behavior
An exception was thrown	Investigating an Exception

The shared spine

Every workflow follows the same backbone:

flowchart TD
    S[Scenario] --> R[Record]
    R --> REP[Report]
    REP --> V{Question type?}
    V -->|Value| WS[Watch Studio / Causal Flow]
    V -->|Environment| PM[Probe Map / Timeline]
    V -->|Failure| EF[Exception Flow]
    WS --> MB[MindBoard]
    PM --> MB
    EF --> MB

Before any workflow

1. Frame the question in one sentence (write it in a MindBoard Note if helpful).
2. Reuse an existing Scenario when the system is the same. Duplicate only when you need a fork.
3. Validate the Scenario before a long reproduction (recording requires at least one tracked method/type, Watch, or enabled Probe).
4. Record one clean take: start at a known state, stop right after the symptom.

After any workflow

1. Pin evidence on MindBoard (Reference nodes + relationship links).
2. Set board status (Investigating → Confirmed → Resolved) when appropriate.
3. Export (HTML/Markdown) if the conclusion must leave Unity.

Daily Workflow Best Practices Getting Started