> For the complete documentation index, see [llms.txt](https://docs.darwinslab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darwinslab.ai/ux-tree-of-life-terminal-journal-sessions/journal.md).

# Journal

The Journal acts as the persistent audit trail for every user action and system outcome.

* Each evolutionary event—unit-test pass, evaluation score, fork creation, sandbox flag—is timestamped and recorded.
* A filterable timeline lets users drill down to specific result classes:
  * “Only divergents”
  * “Only archived forks”
  * “Only hallucination errors”
  * “Only passes with delta > 10%”
* A **Replay** button reconstructs the agent’s reasoning path from input → output, allowing full interpretability and debugging.
* When a model fails a red-team check or outputs a malformed response, these failure events are stored as flagged entries.
* All journals can be exported as JSON or markdown logs.
* Journals can be attached to share links (from Tree of Life) to allow collaborators or reviewers to audit an agent’s complete evolutionary trail.

This module supports reproducibility, transparency, and third-party review—core tenets of Darwin’s open protocol vision.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.darwinslab.ai/ux-tree-of-life-terminal-journal-sessions/journal.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.