Storage Documentation

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

AIWG stores project artifacts on the local filesystem by default. These pages explain when to keep that default, when to route a subsystem to another backend, and how to verify storage behavior before relying on it.

Start with Overview if you are choosing a backend. Use Security before adding external services or credential-backed configuration.

Pages

• Overview — what the storage system does, quick start, CLI surface, what's implemented vs deferred
• Security — credential handling, path traversal rejection, atomic writes, doctor validation
• Migration — the agent-owned storage operation command walkthrough
• Direct PostgreSQL — advanced canonical backend, roles, TLS, migration, and qualification
• PostgreSQL through PostgREST — optional HTTP transport, RPC boundaries, RLS, and limits
• Scalable backend contract — versioned capabilities,

data classes, consistency, and backend maturity

• Scalable migration protocol — checksum-backed

offline/online migration, approval, cutover, and rollback

• Qualification evidence — correctness-first concurrency, fault, recovery, and benchmark reports

Per-backend pages

Backend	Page	Status
`fs`	backends/fs.md	READY (default)
`obsidian`	backends/obsidian.md	READY
`logseq`	backends/logseq.md	READY
`fortemi`	backends/fortemi.md	READY (alpha; legacy for search)
`notion`	backends/notion.md	STUB (#959)
`anythingllm`	backends/anythingllm.md	STUB (#960)
`s3`	backends/s3.md	STUB (#962)
`webdav`	backends/webdav.md	STUB (#963)

Reference

• Live backend status: the agent-owned storage operation
• Fortemi Core index/search packaging: Fortemi Core prebuilt indices