Immutable Decision Trace Store
The OSSexplain() only works within the active session and captures enriched trace data (query events, error events, session timing, state diffs). Pro builds on this with persistent, cryptographically signed, immutable traces — the full causal chain is queryable forever.
OSS Trace Enrichment
Everycommit_outcome automatically captures:
- Session timing —
session_started_at,session_ended_at,session_duration_ms - Query events — every
search()andlist()call with parameters, result counts, and per-operation latency - Error events — any errors during reads, writes, or tool calls
- State diff — entries created, updated, and confidence changes during the session
- Full entry snapshots —
value,memory_type, andwritten_bycaptured at read time
Pro Immutable Traces
Pro adds:- Cryptographic integrity — HMAC-SHA256 content hashing with Merkle chain linking across sessions
- LLM call spans — model, provider, prompt/completion token counts, cost, latency, temperature, finish reason
- Write events, tool calls, agent interactions — full record of every action
- Token and cost aggregates —
total_llm_calls,total_tokens,total_cost_usdper trace
OpenTelemetry Export
Export AMFS decision traces as OpenTelemetry spans for integration with existing observability stacks (Jaeger, Grafana Tempo, Datadog, Honeycomb). Traces are mapped to hierarchical spans following GenAI semantic conventions — each LLM call becomes agen_ai span, and memory operations become amfs spans.
