Stigmem compatibility

2 min readReferenceUpdated 2026-05-19

What you'll find here

The minimum Stigmem HTTP surface Craik v0.1.0 targets — endpoints, error mapping, and capability detection.

Minimum compatibility, optional extensions.

The required endpoints are baseline; optional endpoints unlock ranked recall and contradiction import.

Endpoints

Endpoint	Required	Craik use
GET /healthz	Yes	Reachability check.
GET /.well-known/stigmem	Yes	Capability and auth discovery.
POST /v1/facts	Yes	Direct fact writes when policy grants memory.write.
GET /v1/facts	Yes	Fact query and search fallback.
GET /v1/facts/{fact_id}	Yes	Load one fact by id.
GET /v1/facts/{fact_id}/provenance	Yes	Load fact provenance for evidence and case files.
POST /v1/recall	Optional	Future ranked recall path.
GET /v1/conflicts	Optional	Future contradiction import path.

Error mapping

Stigmem response	Craik error
401	StigmemAuthError
403	StigmemPermissionError
Other HTTP failure	StigmemRequestError
Missing local config or incompatible response shape	StigmemCapabilityError

Capability detection

craik connect stigmem verifies the node can answer health, metadata, and authenticated fact-query requests.

Node URL

Node id

Whether auth is required

Required endpoint support

Optional recall / conflict / federation / source-attestation hints

Check timestamp

What's next

GuideConnecting StigmemThe operator-facing setup.ReferenceMemory backendsThe interface every backend implements.ReadStigmem integrationThe full boundary, fact mapping, and contradiction strategy.