Export and Storage
Investigations are valuable only if the evidence can travel. Here are the export formats and where TraceMind keeps your project data.
Export formats¶
JSON
Structured interchange for tooling, pipelines, and archives. Choose this when another system needs to read the recording.
HTML
Readable sharing with teammates or stakeholders who do not have the project open. Choose this when the audience just needs to read the story.
Markdown
Tickets, design docs, and pull request notes. Choose this when the evidence belongs in your existing written workflow.
When to export¶
Filing a bug
When the report needs evidence that lives outside Unity.
Requesting review
When a reviewer does not have the same Play Mode setup.
Archiving a resolution
To keep a baseline for later regression comparison.
Attaching proof
When a design decision needs supporting evidence.
Export the conclusion, not only the raw data
Pair an export with a short MindBoard summary: what you believe, what supports it, and what remains open.
Other useful exports¶
Depending on the surface, TraceMind also supports a Scenario Console export for instrumentation messages, and a Method Flow graph image export for visual call structure. Use these when the story is easier to show than to describe.
Where TraceMind stores data¶
TraceMind uses a per-project SQLite database, which keeps investigation data with the project while staying outside normal Assets churn.
| Stored data | Notes |
|---|---|
| Scenarios | Your reusable recording playbooks |
| Reports | Every recording you have captured |
| MindBoard | Boards, items, relationships, and groups |
| Board state | Sketch strokes, tab selection, and persisted workspace chrome |
Storage maintenance¶
Compact
Use compact on long-lived projects after many recordings to keep storage tidy.
Reset
Reset is a hard clean slate for TraceMind data in that project. Export first if anything must survive.
The database is investigation memory
Unity's Library folder is often local and regenerable, but this database holds your reasoning. Export key Reports before machine migrations, mirror important conclusions in tickets, and treat Scenario playbooks as valuable team assets.