File Store

File-based stores persist data as individual files in the .polpo/ directory. They are the simplest option and require no additional dependencies.

Stores

Store	Purpose	Location
`FileTaskStore`	Tasks and missions	`.polpo/tasks/<id>.json` + `.polpo/missions/<id>.json`
`FileRunStore`	Execution run history	`.polpo/runs/`
`FileMemoryStore`	Project memory	`.polpo/memory.md`
`FileLogStore`	Event log persistence	`.polpo/logs/`
`FileSessionStore`	Chat sessions	`.polpo/sessions/`
`FileApprovalStore`	Approval gate state	`.polpo/approvals.json`
`FileNotificationStore`	Notification records	`.polpo/notifications.json`

The FileTaskStore uses a multi-file layout: each task and mission is stored as a separate JSON file, plus a _meta.json metadata file.

.polpo/
├── tasks/
│   ├── <taskId>.json
│   └── ...
├── missions/
│   ├── <missionId>.json
│   └── ...
└── _meta.json

Pros: Zero config, human-readable files, easy to inspect and debug. Cons: No concurrent access safety, can degrade with very large task sets.

Scenario	Recommended?
Getting started / single user	Yes
Debugging / inspecting state	Yes
Multiple concurrent orchestrators	No — use SQLite
Large task sets (100+ tasks)	No — use SQLite

File is the default backend. No configuration needed. To be explicit:

{
  "settings": {
    "storage": "file"
  }
}