SEIF Protocol

Install the SEIF CLI, initialize a workspace, and sign your first verifiable artifact in under a minute — or start in the Hub.

Prefer the browser?

If you were invited to seifprotocol.com, follow Web first touch (OAuth → onboarding → bind → Explore). The steps below are the CLI path.

This guide takes you from zero to a verifiable, signed artifact. It assumes a POSIX shell; no specific operating system or machine is required.

1. Install the CLI

macOS and Linux (arm64 or amd64). The installer detects your platform, downloads the signed binary, verifies its checksum, and puts seif on your PATH:

curl -fsSL https://get.seifprotocol.com/install.sh | sh
seif --version

Keep it current at any time — the client updates itself in place:

seif update

2. Initialize a workspace

Run this inside any project directory. SEIF creates a .seif/ store that holds your memory modules, signing keys, and governance records.

seif init

Portable by design

Throughout these docs, $SEIF_CONTAINER_ROOT refers to the root of your workspace — wherever you ran seif init. Nothing here depends on a specific path, hostname, or machine.

3. Sign your first artifact

echo "Hello, provenance!" | seif sign

This returns an Evidence URL. The artifact now carries an Ed25519 signature, a SHA-256 content hash, and an OpenTimestamps anchor.

4. Verify it

seif verify <evidence-url>

Expected output:

✓ Signature   VALID (Ed25519)
✓ Timestamp   OpenTimestamps anchored
✓ Hash        sha256:…
✓ Class       PUBLIC

5. Persist context

Add a decision to memory so your next session — on any machine, with any model — starts with it already loaded.

seif contribute decisions "Use Ed25519 over RSA: smaller keys, faster verify."

Next steps

Hub daily loop: Hub without CLI.
Bind Hub workspace to this clone: seif workspace bind <id_or_user/slug> — see Web first touch.
Wire SEIF into your editor: AI tool integration.
Understand the model: Core concepts.
Full command list: CLI reference.

Quickstart