# Team (https://docs.neuralisapp.com/agent-core/team)

A **team member** is a ready-made agent character a package ships under
`team/<slug>/`: a `member.json` with the create-agent shape, plus identity
files copied into the agent when it is created. The contract — fields,
placeholders, what reaches a model — is on
[package-system team](https://docs.neuralisapp.com/package-system/team.md). This page covers what agent-core
ships and how an agent's identity behaves once it exists.

## What agent-core ships [#what-agent-core-ships]

| Member | Role | What it is for |
| --- | --- | --- |
| `admin` | `admin` | An operations coworker for one project: coordinates work, verifies outcomes, and governs access, schedules, spend and incidents. It acts only with the authority of the person it works for, routes specialist work to subagents, and keeps privileged changes attributable. |

The member ships three identity files — `SOUL.md`, `USER.md` and
`HEARTBEAT.md` — and runs with the full tool set its caller's role allows. Pick
it from the team catalog when you create an agent, or batch-create it with the
`manage-agents` skill.

## Living identity files [#living-identity-files]

A provisioned agent owns its `SOUL.md`, `USER.md` and `HEARTBEAT.md` in its own
private data folder. The package's copies are **seeds, not mirrors**: an
ordinary resync of files and configuration from the template keeps the identity
the agent has grown, and replacing it takes an explicit identity reset.

The files stay small but living. After meaningful work an agent may add, replace
or prune direct links to focused memories, plans, commits, workflow reports,
sources or READMEs — it does not copy those artifacts, and it does not force
every link through one master memory index. `SOUL` changes rarely, with durable
craft; `USER` tracks current person-scoped collaboration links; `HEARTBEAT`
changes most often, as a resume index.

### Resync and reset are separately authorized [#resync-and-reset-are-separately-authorized]

- An ordinary resync needs the right to **update** the agent.
- An identity reset overwrites the files that open the agent's every prompt, so
  it needs full agent-management rights **and** either ownership of that agent
  or authority at least as strong as both an administrator and the agent's own
  role. A manager may reset the agents it owns and no others. The strength
  comparison is a number, never a role name, so a custom role behaves exactly as
  its configured strength says.
- A reset runs as preview → apply. The preview records a backup, so a failure
  midway rolls the whole identity group back, and a stale preview is rejected at
  apply.

The result is truthful: `applied`, `preview` or `partial`, and a partial
file/config failure answers `207`.

### What the platform guarantees about the block [#what-the-platform-guarantees-about-the-block]

Each identity file is injected as its own labelled block at the head of the
prompt. A file's contents cannot close its own block or open another one naming
a different agent, its name cannot inject an attribute, and a symbolic link
dropped into the folder is skipped rather than followed. The number of files
injected is bounded by a platform setting, and when the bound is reached the
prompt says so rather than dropping files silently.

What the platform does **not** claim is that the block cannot be *influenced*:
the identity folder is writable by the agent and by members with write access
to it, which is what makes a living identity possible in the first place. The
guarantee is that whatever is written stays inside its own block, attributed to
the agent that owns it. An agent evolves its own identity through the
filesystem tools and cannot rewrite another agent's.

A subagent does not inherit its parent's identity files — see
[agents](https://docs.neuralisapp.com/agent-core/agents.md).
