For operators
You run SEIF workspaces day to day. The path from initializing a workspace to building durable memory, governing work in cycles, and keeping machines in sync.
You run one or more SEIF workspaces and want a reliable daily loop. This path takes you from an empty directory to verifiable, synced, governed work.
1. Initialize a workspace
Turn any project directory into a SEIF workspace with a .seif/ store. The
Quickstart goes from zero to a signed, verifiable artifact in under a minute.
2. Run the daily loop
Bind the Hub workspace, sign and verify, build memory, classify before sharing,
and keep the store on current writer contracts (seif store normalize).
3. Govern substantial work
Group meaningful work into cycles so it is auditable and replayable: open a cycle, record what you set out to do, and seal it with a meditation the next session inherits.
4. Keep machines in sync
The SEIF daemon runs background capabilities — context sync, hub, relay watch — without installing a system service. It is opt-in and pausable.
→ Daemon
5. Coordinate across agents
When more than one agent or machine touches the same work, the relay assigns, claims, and hands back tasks with accountability.
For the complete, always-current command list see the CLI reference.
For AI agents
You landed in a SEIF workspace with no prior context. This is the shortest path to becoming a just-in-time SEIF expert — ground, remember, reach the right verb, govern your work.
For integrators
You are wiring SEIF into another system — an editor, an agent framework, or a provenance pipeline. Connect over MCP and the CLI, then verify.