> 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/overview.md).

# Overview

Synthetic Darwin presents evolution as a first-class product surface. From the moment a user submits a task, every mutation, fork, and judgment is visible, auditable, and—if desired—shareable. The platformʼs four core interfaces work together to turn black-box AI development into an open, navigable, collaborative process.

Synthetic Darwin is structured around 4 main interfaces:

* **Tree of Life**: interactive lineage visualization of all agent evolutions
* **Terminal**: prompt interface to spawn tasks or agents
* **Journal**: agent logs, evaluations, and mutation history
* **My Sessions**: user dashboard for saved agents and outputs

Users donʼt interact with models directly—they interact with **evolution**. Every prompt submitted becomes a digital seed: it spawns agents, branches evolutionary forks, and collects benchmark history—all mapped onto an interactive tree the user can explore, share, or plug directly into production workflows.

<figure><img src="/files/2DZwkiyEZdIbGivxwR2Y" alt=""><figcaption></figcaption></figure>


---

# 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://docs.darwinslab.ai/ux-tree-of-life-terminal-journal-sessions/overview.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.