Skip to main content
Every memory entry in AMFS carries provenance — metadata about who wrote it and when. This creates an audit trail and enables agents to assess the trustworthiness of information.

Provenance Fields


Automatic Provenance

Provenance is recorded automatically. You don’t need to set it manually:

Pattern References

Use pattern_refs to cross-reference related entries:
Pattern refs are free-form strings. Use them to build a web of related knowledge that agents can follow.

Agent Identity

In the MCP server, agent identity is auto-detected from the environment: Override with the AMFS_AGENT_ID environment variable:

Provenance Tiers

AMFS computes a provenance tier for each entry based on the agent ID and outcome history. This enables downstream systems to prioritize production-validated knowledge over manually seeded assumptions.
The tier is a computed property — it derives from provenance.agent_id and outcome_count, not stored as a separate field.

Querying by Provenance

Search for entries written by a specific agent: