> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/ecosystem-components/case-files.md).

# Case Files

Case Files are saved scan results inside the PRIVAI OS. They help users keep track of findings, summaries, reports, and evidence gathered during investigations.

## Current Tools

| Tool                     | Purpose                                                                                   | Status     |
| ------------------------ | ----------------------------------------------------------------------------------------- | ---------- |
| **scan\_case.report**    | Shows the current dashboard report and saved scan context.                                | MVP active |
| **risk\_history.export** | Downloads saved scan history and evidence as a JSON export pack from the current browser. | MVP active |

## What A Case File Can Contain

* Target details such as wallet, token, domain, username, email, or phone context.
* Module outputs and risk signals.
* AI summaries and action plans.
* Timestamps and scan metadata.
* Exportable evidence history.

## Local-First Model

Case Files are currently **local to the browser**.

This keeps the MVP lightweight and avoids creating unnecessary account infrastructure before the core workflow is proven.

## Planned Improvements

* Server-side account database.
* Cloud sync across devices.
* Team workspaces.
* Richer timeline exports.
* Shareable reports.
* Watchlist and alert history.

## User Responsibility

Case Files may include sensitive investigative context. Users should store exports carefully and avoid sharing reports that include private or identifying information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.privai.cloud/ecosystem-components/case-files.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.