Features
What Stigmem is
An open, federated knowledge protocol — a layer where AI agents and
humans store typed, traceable facts that travel across tools,
platforms, and organizations. Each fact is an immutable record
(entity, relation, value, source, timestamp, confidence, scope)
written once, queryable forever, with full provenance and a defined
expiry.
This page describes v0.9.0a1 and the active alpha extraction line.
The canonical version line of stigmem begins at v0.9.0a1
per ADR-001
- ADR-019.
Earlier version markers labeled internal development checkpoints, not
tagged releases. Many features that earlier docs described as
"Stable" were deferred per ADR-002
— the v1 critical-path scope cut. Those features remain in the
codebase as opt-in or deferred surfaces. Migrated feature truth now lives in
features/<feature>/; implementation packages that still live underexperimental/<feature>/remain gated and off by default.
How to read this page
features/<feature>/ once migrated; implementation may remain under experimental/<feature>/. Not in the default install.features/<feature>/status.md, while unmigrated rows still use experimental/<feature>/STATUS.md.No calendar dates. Stigmem is phase-gated, not time-gated. Phase progression is documented in ROADMAP.md.
Why pick Stigmem over a vector-RAG product?
Stigmem retrieves typed atomic facts, not opaque chunks.
Each embedding has an explicit (entity, relation, value)
contract. Recall in v0.9.0a1 covers basic typed-fact retrieval;
advanced recall (graph BFS, vector embeddings, MMR packing, memory
cards) is deferred per ADR-002 and ships incrementally as plugins.
Read the spec at
spec/stigmem-spec-v0.9.0a1.md.
Core memory model (v0.9.0a1 critical path)
local / team / company / public)valid_until, retraction)Recall (v0.9.0a1 critical path)
POST /v1/recall basic typed-fact retrievalquery_facts operationassert_fact operationFederation (v0.9.0a1 critical path)
/.well-known/stigmem-manifest.jsonAuthentication & authorization (v0.9.0a1 critical path)
interpret_as)main; future cert/validation pending (ADR-003)Observability (v0.9.0a1 critical path)
Storage, embedding, SDKs, adapters, operations
nomic-embed-text-v1.5 embeddingsstigmem-py)@eidetic-labs/stigmem-ts)stigmem-go)features/sdk-go; package alignment remains future alpha work.stigmem-openclaw)features/mcp-adapter; @eidetic-labs/stigmem-mcp is independently versioned and installs the stigmem-mcp binary.features/openai-tools-adapter; packaged as stigmem-plugin-openai-tools-adapter for v0.9.0a10; live LiteLLM, OpenAI SDK, and Ollama validation remains operator-owned for v0.1.0.features/paperclip-adapter; live Paperclip validation remains future alpha work.features/ollama-litellm-adapter; compatibility identity for the OpenAI-compatible tools adapter.features/gemini-adapter; packaged as stigmem-plugin-gemini-adapter for v0.9.0a10; live Gemini validation remains operator-owned for v0.1.0.features/zep-adapter; packaged as stigmem-plugin-zep-adapter for v0.9.0a10; live Zep validation remains operator-owned for v0.1.0.features/letta-adapter; packaged as stigmem-plugin-letta-adapter for v0.9.0a10; live Letta validation remains operator-owned for v0.1.0.features/cognee-adapter; packaged as stigmem-plugin-cognee-adapter for v0.9.0a10; live Cognee validation remains operator-owned for v0.1.0.features/obsidian-adapter; CLI, plugin, and live-vault validation remain future alpha work.make demo, make demo-attack.features/deploy-helm; live cluster validation remains future alpha work.features/deploy-fly; live deployment, persistence, dashboard validation, and secrets review remain future alpha work.features/deploy-grafana; live stack validation, metric review, alert review, and packaging remain future alpha work.features/deploy-paas; live platform validation, persistence, secrets, and scaling review remain future alpha work.features/deploy-systemd; live distro validation, installer review, hardening review, and upgrade/rollback remain future alpha work.Plugin infrastructure (alpha-series foundation)
stigmem plugins inspection.Experimental & deferred features
The following features are not in v0.9.0a1's default install. Migrated
feature records own the product truth under
features/<feature>/.
Implementation code may still live under experimental/<feature>/. Unmigrated
future-alpha adapters, SDKs, deployments, dashboards, and tooling still carry
experimental/<surface>/STATUS.md tracking.
Alpha extraction is NOT ADR-008 graduation.
Across the v0.9.0a2..a8 alpha series, cross-cutting features are extracted into opt-in experimental plugin packages per ADR-011. Graduation into the supported surface happens later, after the ADR-008 five-gate process.
as_of queriesas_offeatures/multi-tenant/experimental/<feature>/STATUS.mdfeatures/dashboard/features/eval-harness/experimental/<surface>/STATUS.mdSee the full deferred-features list and source locations at Experimental Features.
v0.9.0a1 architecture in flight (Option A acknowledgment)
The v0.9.0a1 default install ships with feature-specific code in
node/src/stigmem_node/ for several deferred features
(tombstones.py, instruction_migrate.py, card_materializer.py,
source_trust.py, etc.). The routes are mounted but the features
are dormant unless explicitly configured. Per ADR-019 iteration
semantics, each v0.9.0aN extracts one cross-cutting feature into a
plugin per ADR-011's C1 plugin architecture; after v0.9.0a8, default
install will be true to ADR-011's commitment.
Main now includes the hook-registry foundation and stable 22-hook
surface, with manual/core handler registration, minimum
manifest/context/capability APIs, hook-site wiring, registry
observability, test helpers, benchmark coverage, entry-point package
discovery, startup registration, operator inspection commands, and
production signing/trust gates. Lazy instruction discovery,
time-travel queries, RTBF tombstones, advanced Memory Garden ACLs,
source attestation, and multi-tenant isolation have been extracted
as opt-in experimental plugin source packages; signed/package
artifact evidence remains deferred until the plugin launch train. The ADR-003 instruction-handling
core is also present on main: interpret_as, instruction:write,
instruction quarantine, channel-separated recall output, MCP/OpenClaw
channel framing, instruction audit events, and same-session
provenance controls. Plugin authors can start from the
Plugin Author Guide.
See LIMITATIONS.md §11 — v0.9.0a1 architecture in flight for the full architectural-gap acknowledgment.
What's coming next
The phase progression is in ROADMAP.md.
- v0.9.0a2 through v0.9.0a8 — incremental plugin extraction per ADR-011. Lazy instruction discovery, time-travel queries, RTBF tombstones, advanced Memory Garden ACLs, source attestation, and multi-tenant isolation are extracted on
mainas opt-in experimental source. CIDs remain core. - Future hardened-core line — complete the remaining hardening evidence around the landed capability redesign, finish ADR-015 model-certification runner/results, federation hardening, OpenClaw audit closeout, storage immutability stack per ADR-016, 30-day external operator soak.
- Future release-candidate and GA lines — Sigstore-signed releases, reproducible builds, SBOM, 3+ external operators in production. Wire format frozen.
Out of scope — explicit non-targets
A hosted/SaaS Stigmem product
Reference deployments only; operators run their own nodes.
A competing agent runtime
To OpenClaw / Claude Code / LangChain etc.
A multi-agent orchestration layer
Stigmem is a memory substrate — it makes existing agent frameworks more capable, not redundant.
An in-house GRC / compliance product
Stigmem provides provenance primitives; compliance application logic is out of scope.
A vertical agent product
Support agent, bookkeeping agent, etc. — until post-v1.0.0.
A chatbot of any kind
This page is regenerated each release to reflect actual ship-state.
The previous "Spec v2.0 — in flight" framing was retired during the
v0.9.0a1 reset. For the development history, see
spec/EVOLUTION.md.