> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synheart.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Synaptic Mesh

> A map of how your organization's decisions, code, documents and people connect, as a timeline or a network. My Mesh and Org Mesh, restricted items, and where human state appears

**Synaptic Mesh**, under **Ask** at [synapse.synheart.ai](https://synapse.synheart.ai), shows the story behind your code: which decisions shaped it, what came from each one, and who did the work. It's built from your organization's indexed [knowledge sources](https://docs.synheart.ai/synapse/knowledge-sources.md) and connected work.

Everyone with a seat can open it.

## My Mesh and Org Mesh

* **My Mesh** shows your own work and what it connects to. Everyone sees it.
* **Org Mesh** shows the whole organization. It's for Synapse Leads and Admins, and the organization owner. Members don't see the switch.

## Two views

**Timeline** tells the story of one piece of code or one decision through time: what it was built because of, what was added under it, and what replaced it.

**Network** is the whole map. Drag nodes, pan and zoom, or use **Fit to view**. Select a node to read its details. A trail of the nodes you've opened runs through both views, so something you read in the timeline can be found on the map and back.

Search for code or a decision with **Find code or a decision**. The legend turns categories on and off: decisions, code, documents and notes, issues and tickets, pull requests and commits, and people.

## What the links mean

Each link says how two things relate, for example:

* **Built because of** and **Added under**: code that follows a decision.
* **Replaces** and **Replaced by**: a decision that superseded another.
* **Addresses**, **Fixed by**, **Caused by**: work tied to an issue or incident.
* **Written by**, **Top contributor**: who did the work.

Decisions are drawn bigger when more code follows them. A decision with nothing linked says *No code follows it yet*. Code links to a decision when a commit mentions its id, such as `ADR-0006`, or when the decision is saved in the code's folder. Items linked to nothing are marked as gaps, so you can see what still needs a decision or an owner.

## Ask your agent about a node

A node's details include **Ask your AI (MCP)**. **Ask "Why was this created?"** and **Find related context** copy a prompt that names the node. Paste it into Claude Code, Cursor or another agent connected to Synapse, and it answers from the same memory. See [Connect your agent](https://docs.synheart.ai/synapse/connect-agents.md).

## Restricted items

Some documents are restricted at their source, or by an admin. A restricted item keeps its place on the map so the shape of the story stays true, but its title and content are never shown. It appears as **Restricted item**. You can hide restricted items from the legend.

Restricting or un-restricting a document is recorded in the [audit log](https://docs.synheart.ai/synapse/audit-log.md).

## Human state on the map

If you've connected Life by Synheart, your own nodes can show **Your state across this work**: your readings near the time you did it. Human state appears only on your own nodes, for every role. A teammate's node never carries their human state, whoever is looking, including Leads, Admins and the owner.

If your organization has turned off human state, or you haven't connected Life, the map says so and shows no readings. See [Team views and privacy](https://docs.synheart.ai/synapse/team-views.md).

## On Synapse Free

On Synapse Free, the map covers the last 30 days of history.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.