> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/databases-and-data/simulations/simulation-explore-results.md). # Exploring the simulation results When you run a simulation workflow, Fabricate adds a simulation results database to the project. The specific generated artifacts in the simulation results can vary based on the selected run mode. At a high level, the results include:

Entry in the project navigation for simulation results

* A **Simulation** page with details about the simulation. * For each content platform where simulation data was generated, links to the simulation user interface. For example, if the generated data includes email messages in Gmail, then the simulation results contain a link to Google Workspace, which in turn contains a link to the Gmail simulator. ## Information on the Simulation page The **Simulation** page can contain the following tabs. ### Overview The **Overview** tab provides a high-level summary of the simulation run. It includes: * The possible actions for the simulation. For example, for a completed run, you can regenerate the results. * The parameters that were used for the run. * The token usage and cost across all runs of the workflow. * The history of the run processing.

Overview tab on the Simulation page for simulation results

### Timeline The timeline is the full, detailed script of the simulation. The timeline is divided into acts and scenes. To display the details for an act or scene, in the timeline overview at the left, click the act or scene. For an act, the details provide a summary of the activity. For a scene, the details include the cast members and activity.

Timeline tab on the Simulation page for simulation results, with the details for a selected scene

### Cast The cast is the list of cast members for the simulation. Each cast member is given a name and description of their persona. **Point of View** lists the main persona for the simulation. The simulation is essentially from that persona's point of view. **Rest of the Cast** lists the remaining personas.

Cast tab on the Simulation page for simulation results

### Scenario The **Scenario** tab starts with a summary of the run processing. It then provides a summary of the scenario itself, including: * Timeframe * World * Themes * World rules

Scenario tab on the Simulation page for simulation results

### Services The **Services** tab contains the list of content platforms that were used in the simulation run. To navigate to the simulation artifacts for that content platform, click the platform.

Services tab on the Simulation page for simulation results

## Using the content platform simulators Each content platform for the generated data has an entry in the simulation run results. To display the simulated user interface with the generated items, click the content platform entry.

Content platform simulator showing a simulated Slack user interface with posts for the simulation

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tonic.ai/fabricate/databases-and-data/simulations/simulation-explore-results.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.