Chronicle is the workspace authority for Fabric when versioned file access, content-addressed storage, and workspace sync are required. It is written in Rust and can be used with a FUSE mount or in no-FUSE modes depending on the task and host capability.
Chronicle is optional in the root Fabric PM2 stack unless a task explicitly needs workspace authority.
What It Does
- Tracks file iterations and metadata.
- Stores content by BLAKE3 hash in a content-addressed store.
- Supports sync and replication between workspace locations.
- Can expose Fabric workspace/sync routes behind
--fabric-port. - Integrates with Podium-managed agents when versioned workspaces are enabled.
Current Implementation Notes
| Area | Current shape |
|---|---|
| Language | Rust |
| FUSE crate | fuser 0.17 |
| Mount path | Uses spawn_mount2 in current code |
| Notifications | Uses the current notifier path |
| Storage | SQLite metadata plus BLAKE3 content-addressed storage |
| Fabric surface | Optional workspace/sync server via --fabric-port |
How Agents See It
Agents should continue to use normal file operations:
const workspace = process.env.AGENT_WORKSPACE;
await Bun.write(`${workspace}/output.ts`, generatedCode);Chronicle provides versioning and sync underneath when it is mounted or otherwise attached. Agents should not need to know the storage implementation.