CLI workflow
A day in the life of the SEIF CLI — bind, sign, remember, store normalize, push, and seal cycles.
The seif CLI is the primary client for the protocol. This guide walks the
everyday loop. For every flag, see the CLI reference.
Browser-first path: Web first touch.
Install and update
curl -fsSL https://get.seifprotocol.com/install.sh | sh
seif --version
seif updateBind before you trust push / log
Hub workspaces and local clones must share identity:
seif init
seif login
seif workspace bind <workspace_id_or_user/slug>
seif doctorWithout bind, seif log list can look empty even after Hub writes.
Sign and verify
seif sign ./report.md
cat report.md | seif sign
seif verify <evidence-url>Build durable memory
seif contribute decisions "Adopt OpenTimestamps for all release artifacts."
# or governance path:
seif gov memory add <name> --content ./scratch.md
seif status
seif recapClassify before sharing
seif classify ./notes.md
# -> PUBLIC | INTERNAL | CONFIDENTIALStore hygiene — normalize writer contracts
CAS-allowlisted trees under .seif/ must match current CLI writer contracts.
Dry-run by default:
seif store normalize
seif store normalize --kinds memory,cycles,memos
seif store normalize --apply # rewrite fixable files
seif store normalize --json # machine report| Outcome | Meaning |
|---|---|
ok | Already canonical |
fixable | Will rewrite with --apply |
quarantine | Review by hand before push |
Kinds covered: memory, evidence, debates, cycles, seeds, memos, pending, sessions, coherence, observations. Host-local trees (relay, claims, archive) are skipped.
Sibling verbs:
seif store hygiene # retention sweeper (dry-run)
seif store inventory # JSONL inventory of .seif/
seif store move … --dry-run # relocate module artifactsSync across machines
seif push --dry-run
seif push
seif pull
seif status --deltaLocal coherence maestro (diagnose/plan; not a push synonym):
seif sync # dry-run plan
seif sync --apply # apply cures
seif sync --apply --push # heal then mirrorNo machine lock-in
Every command here works the same regardless of host or OS. Paths are relative
to the workspace you initialized (seif init).
Seal substantial work
seif gov cycle open c1-my-feature
seif gov cycle set-manifest --title "…" --vision "…"
# …work…
seif gov cycle close-ritual c1-my-featureThe Hub can open deliveries; close-ritual stays in CLI/IDE. See Hub without CLI.
Next
- Intent → verb map: Capability map
- Full catalog: CLI reference
Access and roles
Workspace membership (read · contribute · maintain · admin), the Access tab, and invite-via-grant — without inventing org/teams.
Intent → verb map
The compact, measured capability map an AI reaches for at the moment of need — plain intent on the left, the exact SEIF verb on the right, plus the multi-step workflow recipes.