Docs / Provenance

Know where a record came from.

Provenance is carried by explicit record and payload fields. Optional fields are omitted when absent rather than filled with decorative values.

Required record and hit fields.

FieldMeaning
idRecord primary key generated or supplied on write.
collection_idOwning session or collection.
roleRole recorded at ingest.
record_typeRecord category recorded at ingest.
text_contentStored record text returned by recall.
tsRecord time in the public contract.
tagsString tags attached to the record.

Separate producer, path, and source key.

FieldMeaning
agentProducing agent identity when known; otherwise null.
entrypointHow the record entered the store, such as CLI or MCP.
source_typeThe source category recorded with the payload.
source_idOptional source-local key; omitted when the record does not carry one.

Recall adds result-state fields.

Each hit includes score, is_superseded, related, and tokens_estimate. Optional valid_until, explain, or provenance sections appear only on paths that supply them.

Important: score scale depends on retrieval mode and is not comparable across every query or mode. No score is presented here as a quality claim.

See provenance in a live record.

Follow the recorded round trip, open the machine-readable code-to-record fixture, or read the retrieval semantics.