Skip to the document

Start here

Neotoma gives agents a shared record of changing facts, with a way to inspect the evidence behind the current value.

Source: docs/topics/start.md · Read Markdown · 08598d0

Start with supplied material, maintain an entity, and let an agent read its selected fields.
Start with supplied material, maintain an entity, and let an agent read its selected fields.

What it is for

An agent can write an observation, retrieve the resulting entity, and follow that value back to its source. A correction adds new evidence about what should be current; the earlier observation remains available for inspection. The same record is exposed through MCP, the CLI, and the HTTP API.

Neotoma is the system of record for agent-held state. It does not replace an application's own business database, and it does not decide what an agent should do next. How the record works explains that boundary.

Decide whether it fits

It is useful when multiple agents or tools need to share facts that change, or when a current answer needs a visible source. A single agent working in one narrow domain may not need a separate record. Start with one concrete workflow and check whether the current value and its provenance are both retrievable.

Next steps

  1. Choose an installation path for the tool you actually use.
  2. Choose an interface for that tool or application.
  3. Read the full repository overview for scope and development context.

The agent-facing installation protocol includes evaluation, installation, activation, and tooling configuration. It is a longer operational reference, rather than a substitute for the human install chooser.

InstallChoose a supported setup pathHow the system of record worksUnderstand the architecture: sources, observations, identity, field rules, and shared access.InterfacesChoose MCP, CLI, or REST API for your client.