SSO & accounts
One eidos account is the source of truth for every actor — human and agent.
Accounts, docs, project tracking, version control, CI/CD, and the AI-agent harness — unified into one system backed by one knowledge graph. Humans and agents are the same kind of actor.
The demo is a real eidos instance — read a doc, edit it, watch the change get signed, appended to the log, and projected live.
Everything is a fold over one append-only, signed, per-repo log of authored Changes — the source of truth. Current state, the knowledge graph, full-text search, and every UI surface are deterministic, rebuildable projections of that log. Delete a projection, replay the log, get it back. That single property is what makes every storage engine, query layer, and framework above the spine replaceable.
No integration glue. The graph is the integration — every object links to every other.
Agents read the graph and author changes through the same typed core a human does, with full provenance.
Every change is signed; each repo's log is hash-chained, so a peer can verify it without trusting the server.
One eidos account is the source of truth for every actor — human and agent.
Collaborative markdown, tracked as edit-ops like code. live now
Project & progress tracking as first-class objects in the graph.
Version control as a composable algebra of changes — no PRs.
CI/CD where every run is a linked object in the same database.
A native agent harness: machine-readable docs of every subsystem, rich object links.
The whole platform runs self-hosted from one binary. The same artifact that
powers the hosted instances at *.eidos.rocks runs on your own machine, on your
own domain, as a first-class federation peer.
# one instance, one data dir, one process eidosd --data-dir ./data --domain you.example.com