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

# Agent workspace

> Tour of agent-workspace/ — Fleet Pi's repo-local home for durable agent memory, execution plans, skills, evals, artifacts, and installed Pi resources.

`agent-workspace/` is Fleet Pi's living directory. It is the repo-local home for the durable context that lets Fleet Pi behave like an adaptive, self-improving coding system instead of a stateless chat window.

<Tip>
  For the accepted canonical workspace contract, manifest and section boundaries, and projection rules, see the [adaptive workspace contract](/fleet-pi/adaptive-workspace).
</Tip>

## What lives here

| Path                         | Purpose                                                               |
| ---------------------------- | --------------------------------------------------------------------- |
| `agent-workspace/memory/`    | Durable project knowledge                                             |
| `agent-workspace/plans/`     | Explicit execution plans and backlogs                                 |
| `agent-workspace/skills/`    | Repo-local agent skills                                               |
| `agent-workspace/evals/`     | Quality and regression checklists                                     |
| `agent-workspace/artifacts/` | Reports, traces, and reusable outputs                                 |
| `agent-workspace/scratch/`   | Safe temporary working files                                          |
| `agent-workspace/pi/`        | Workspace-installed Pi skills, prompts, extensions, and packages      |
| `agent-workspace/indexes/`   | Non-canonical projection storage (search, health, query acceleration) |

## Why it matters

Fleet Pi keeps important agent context in normal repository files so that:

* Project memory can be reviewed and refined over time.
* Plans stay visible to humans and agents.
* Newly installed Pi resources are discoverable instead of hidden in transient runtime state.
* Self-improvement remains part of the repository's change history.

## Relationship to `.pi/` and `docs/`

* `docs/` is the human-facing documentation surface.
* `agent-workspace/` is the agent-facing operational surface.
* `.pi/` contains committed project Pi configuration and built-in runtime bridges.
* `agent-workspace/pi/` is the canonical home for chat-installed Pi resources.

Root `.pi/settings.json` remains a compatibility bridge that points Pi at the workspace-native resource directories.

## Durable self-improvement

Fleet Pi is intentionally opinionated:

* Durable improvements belong in reviewable Git diffs.
* Canonical memory should live in the smallest relevant file.
* Ad hoc notes should stay temporary unless they are later synthesized.
* Transient runtime or session state should not be treated as the source of truth.

## Next steps

<CardGroup cols={2}>
  <Card title="Adaptive workspace contract" icon="file-contract" href="/fleet-pi/adaptive-workspace">
    Canonical sections, manifest, and the projection boundary.
  </Card>

  <Card title="Architecture" icon="sitemap" href="/fleet-pi/architecture">
    Where the workspace fits in the runtime topology.
  </Card>
</CardGroup>