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.
What lives here
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.
.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
Adaptive workspace contract
Canonical sections, manifest, and the projection boundary.
Architecture
Where the workspace fits in the runtime topology.