Skip to main content
Version: v0.9.0a2
Operator

Experimental Features

4 min readOperator · Curious userOutside v0.9.0a1 default

What this page covers

Features that exist outside the v0.9.0a1 default surface. Experimental does not mean "almost stable" — it means the feature is opt-in, unsupported for production reliance, and must pass the ADR-008 reintroduction gates before it can graduate into the supported surface.

Start with the feature matrix for the supported v0.9.0a1 surface. Use this page when you need to inspect what was deferred, where it lives, and whether it has a protocol spec.

Status model

Status
Type
Meaning
Spec-XN experimental protocol
protocol
Has real protocol/design substance. Migrated records own the canonical source under features/<feature>/spec.md; compatibility pointers remain under experimental/<feature>/spec.md where needed. Rendered spec pages live under the Specification section.
Experimental implementation surface
impl
Has code, docs, deployment recipes, adapter code, SDK code, or operational tooling under experimental/<feature>/, but no protocol spec yet. Migrated product truth lives under features/<feature>/.
Dormant
paused
Preserved for future work, but no active ADR-008 gate progress.
Blocked
gated
Cannot progress until another roadmap item lands first.

Every feature should have one visible status owner.

A Spec-XN assignment is reserved for protocol-bearing features; migrated features use features/<feature>/status.md, while unmigrated adapters, SDKs, dashboards, deployment recipes, and tooling continue to use experimental/<surface>/STATUS.md. Do not assign fake specs unless a surface later defines protocol behavior.

Protocol features

These features have a Spec-XN-* experimental spec. They are not part of the supported default install.

Feature · Spec
Status
Notes
Lazy instruction discovery · Spec-X1
extracted · ADR-008 blocked
Source extracted behind plugin registration. Requires ADR-003 capability redesign before supported reintroduction; signed artifact evidence deferred until the plugin launch train.
RTBF tombstones · Spec-X2
extracted · ADR-008 blocked
Plugin-loaded validation covers default/plugin behavior and hook ordering. Regulatory-impact graduation still needs threat-model, conformance, soak, and operator-runbook gates.
Time-travel queries · Spec-X3
extracted · ADR-008 blocked
Default installs reject as_of fail-closed; registered plugins require explicit operator gates; a4 validation covers fact query, recall, tombstone/legal-hold safety, CID interaction, hook ordering, and plugin-required conformance.
Memory Garden advanced ACL · Spec-X5
extracted · ADR-008 blocked
Default installs keep advanced ACL inactive while preserving basic garden CRUD, membership, and direct garden_id guards in core.
Source attestation · Spec-X6
extracted · ADR-008 blocked
Default installs keep source-attestation behavior inert; plugin-loaded validation covers assertion source checks, recall trust-rank contribution, and federation inbound guards without proving release provenance or locally re-attesting federated facts.
Subscriptions · Spec-X7
dormant
Push delivery waits for pull federation validation.
Intent envelope · Spec-X8
deferred indefinitely
Preserved design intent; no active reintroduction path.
Decay semantics · Spec-X9
dormant
Deferred memory-hygiene feature.
Synthesis · Spec-X10
dormant
Deferred snapshot/commercial-path feature.
Recall graph · Spec-X11
dormant
Advanced recall, graph traversal, embeddings, MMR packing, and memory cards.

Cross-cutting features without Spec-X

Feature
Status
Notes
Multi-tenant isolation
source-available
Adds an opt-in tenant boundary above scopes through stigmem-plugin-multi-tenant. Default installs collapse to default; v0.9.0a9 does not claim shared-node readiness or tenant-aware non-default federation. Feature record: features/multi-tenant; no Spec-X yet.
Async jobs
dormant
Deferred async execution surface for long-running jobs.
Fuzzy resolver
dormant
Convenience resolver, not critical-path protocol behavior.
OIDC SSO
dormant
Adds an external identity-provider trust boundary.
Billing hooks
dormant
Commercial/operational concern; not part of the OSS default surface.

Storage and embedding surfaces

Surface
Status
Notes
Storage backend family
Experimental, opt-in
features/storage-backends/; non-default backends remain outside the stable default surface.
libSQL/Turso storage
Experimental, opt-in
features/storage-libsql/; adds third-party service trust and backend-specific behavior.
Cloud embedding providers
accepted risk
R-20 accepted with operator warnings; local embeddings remain the supported default.

Adapters and SDKs

MCP adapter

features/mcp-adapter — experimental external adapter; package metadata is aligned, but publication remains held pending live connector smoke and security certification.

Go SDK

features/sdk-go — experimental external SDK; package alignment and live-node validation remain future alpha work.

Obsidian adapter

features/obsidian-adapter — experimental external adapter; package, plugin, and live-vault validation remain future alpha work.

Cognee adapter

features/cognee-adapter — experimental opt-in plugin packaged as stigmem-plugin-cognee-adapter; live Cognee runtime validation remains operator-owned for v0.1.0.

Letta adapter

features/letta-adapter — experimental opt-in adapter packaged for v0.9.0a10; live Letta validation remains operator-owned for v0.1.0.

Zep adapter

features/zep-adapter — experimental opt-in adapter packaged for v0.9.0a10; live Zep validation remains operator-owned for v0.1.0.

Gemini adapter

features/gemini-adapter — experimental opt-in adapter packaged for v0.9.0a10; live Gemini validation remains operator-owned for v0.1.0.

Ollama-LiteLLM adapter

features/ollama-litellm-adapter — superseded compatibility identity; behavior lives with the OpenAI-compatible tools adapter.

OpenAI tools adapter

features/openai-tools-adapter — experimental opt-in adapter packaged for v0.9.0a10; live LiteLLM, OpenAI SDK, and Ollama validation remains operator-owned for v0.1.0.

Paperclip adapter

features/paperclip-adapter — deferred lifecycle/event adapter; live Paperclip validation remains future alpha work.

Deployment, UI, and evaluation

Curator dashboard

features/dashboard — deferred internal tooling; live-node and deployment validation remain future alpha work.

Eval harness

features/eval-harness — active internal evaluation tooling for adversarial and recall validation; standalone package publication remains future alpha work.

Helm deployment

features/deploy-helm — deferred Kubernetes deployment recipe; live cluster validation remains future alpha work.

Fly.io deployment

features/deploy-fly — deferred Fly.io deployment recipe; live deployment, persistence, dashboard validation, and secrets review remain future alpha work.

Grafana deployment

features/deploy-grafana — deferred observability deployment seed; live stack validation, metric review, alert review, and packaging remain future alpha work.

PaaS deployment

features/deploy-paas — deferred managed-platform deployment recipes; live platform validation, persistence, secrets, and scaling review remain future alpha work.

systemd deployment

features/deploy-systemd — deferred bare-metal deployment recipe; live distro validation, installer review, hardening review, and upgrade/rollback remain future alpha work.

Promotion path

ADR-008 defines the five gates for any experimental feature.

  1. Threat-model delta.
  2. Accepted ADR or amendment.
  3. Positive, negative, and adversarial conformance vectors wired into CI.
  4. External operator soak with public bug reporting.
  5. Documentation parity across Learn, Build, Operate, and Secure.

Gate progress lives in each feature's STATUS.md. Public pages summarize status; they do not promote a feature by themselves.