node-a · scope=company · fact_recordHLC 7BFA0:42
$ ▌
v0.9.0a10 · preview alpha · Apache-2.0
Shared, scope-awarememory for agents.
Stigmem is a federated knowledge fabric where AI agents and humans write typed, traceable facts that travel across tools, platforms, and organizations. Every fact is an immutable record with full provenance, a hybrid logical clock timestamp, and a defined expiry. Nodes peer via signed handshakes; replication respects scope; contradictions never silently overwrite.
- Surface
- federated · scope-enforced
- Plugins
- 6 on PyPI · independent versioning
- Integrations
- MCP · 6 editor hosts
§ Primitives
Three durable, typed objects.
Everything in Stigmem composes from these. Each is queryable, signed, and bound to a node + scope.
fact_record
(entity, relation, value, source, ts, confidence, scope)
Immutable typed records with full provenance, an HLC timestamp, and a defined expiry. The atomic unit of every Stigmem operation.
peer_declaration
ed25519-signed
Signed handshake that establishes federation between two nodes. Defines which scopes the peer may pull and how often.
contradiction
first_class_record
When two facts conflict, the contradiction surfaces as its own queryable record instead of one fact silently overwriting the other.
§ Demo
Assert a fact. Replicate. Recall.
The full operator loop in one terminal. Watch a fact land on node-a, replicate under scope to node-b, and return on a recall — with provenance attached at every step.
§ Federation
Two nodes. One signed handshake.
Stigmem nodes federate via PeerDeclarations — Ed25519-signed records that establish which scopes a peer may pull. Replication is explicit, audited, and scoped. The cost of a peering decision is contained in the record.
§ Plugins
Six published plugins. Independent versioning.
Plugins extend node behavior without modifying the protocol. Each is its own PyPI package on its own release cadence. Install one, all, or none — the substrate works the same.
stigmem-plugin-multi-tenant
Multi-tenant scoping
Boot context, handoff, decision, and escalation become tenant-scoped on the node side. Foundation for shared deployments.
Readstigmem-plugin-source-attestation
Source attestation
Recalled facts carry source trust scores. Low-trust sources can be filtered or quarantined by the node before reaching agents.
Readstigmem-plugin-memory-garden-acl
Memory garden ACL
Membership controls which gardens the boot handshake reads from. Per-operator access boundaries on a shared substrate.
Readstigmem-plugin-tombstones
Tombstones
Hide retracted facts from recall and boot context. Audit-clean revocation without rewriting history.
Readstigmem-plugin-time-travel
Time travel
Historical handoff and decision queries against the node. Replay what an agent knew at a specific HLC.
Readstigmem-plugin-lazy-instruction-discovery
Lazy instruction discovery
Boot context resolves instructions on-demand instead of eagerly. Smaller boot payloads, faster cold-start.
Read
§ Editor integrations
MCP server. Six editor hosts.
Stigmem ships an MCP server so LLM-aware editors can read and write to a node directly. Validation tier reflects the depth of host UI smoke evidence on file.
Honest status
Pre-stable. Read LIMITATIONS.md before integrating.
Stigmem is at v0.9.0a10 — a preview alpha. Single-org, single-node deployments are the currently-supported pattern. Cross-org federation needs hardened-core work documented in the roadmap. The version label matches the validated stability posture; there is no v1.0 yet, and the implied chronology of earlier markers (v0.2 through v2.0) was reset.
Eidetic Labs
Spec, source, community.
The specification is the source of truth. The repository carries the reference node, the SDKs, and the conformance suite. The Discord is where adopters, contributors, and operators discuss installation, federation, and the spec.