Provenance flow
Sign artifacts into verifiable Evidence, check them anywhere, and anchor them in an independent transparency log.
Provenance is what makes SEIF work trustworthy to someone who wasn't there. You sign an artifact; SEIF emits an Evidence frame — a signature, a content hash, a timestamp anchor, and a classification — that anyone can verify, independent of the tool that produced it.
seif sign <artifact> → Evidence frame (signature + hash + anchor)
│
seif verify <ref> → anyone confirms it, anywhere
│
seif log verify <id> → independent inclusion proof in the transparency logSign
seif sign ./report.md
cat report.md | seif sign # a string, a file, or stdinThe result is an Evidence URL that resolves to the signed record.
Verify
seif verify <evidence-url> # public engine proof
seif verify ./signature.json # or a local frameVerification needs only the public record — not your keys and not the original tool.
Anchor independently
seif log list # recent transparency-log entries
seif log get <id> # one entry
seif log verify <id> # independently verify its inclusion proofThe transparency log gives Evidence a second, independent witness: even if you distrust the issuer, the inclusion proof stands on its own.
Where to go next
- Provenance & governance — the mental model.
- Governance flow — recording the decisions behind what you sign.
Governance flow
Defer work as pendings, record decisions, and amend signed artifacts append-only — the ledger that keeps a workspace accountable over time.
Inter-AI sessions
A session records who worked, on what, and what was said — split into a governance contract and a shareable conversation payload that multiple agents can contribute to.