# Agent Trace 0.1.0: the trace-record schema

`trace-record.schema.json` is the JSON Schema of an Agent Trace record, **unmodified**, as
the Agent Trace specification publishes it. flowRS's Agent Trace export
(`flowrs_core::graph::provenance::agent_trace`) is validated against it by
`crates/flowrs-core/tests/agent_trace.rs`.

| | |
|---|---|
| Specification | Agent Trace, version 0.1.0 (status RFC, January 2026), <https://agent-trace.dev> |
| Schema `$id` | `https://agent-trace.dev/schemas/v1/trace-record.json` |
| Pinned copy | <https://web.archive.org/web/20260312181455id_/https://agent-trace.dev/schemas/v1/trace-record.json> (Wayback capture of 2026-03-12) |
| Fetched | 2026-10-22, from the live `$id` URL and from the pinned capture: byte-identical |
| SHA-256 | `f86ded10e845445a21093283092752192b6c614093168035da93a47f696ca5eb` |
| Wayback digest | SHA-1 (base32) `KFOXFIGHG3PQ2UWCKHUD7LK5HEUWKYDC` |
| Licence | CC BY 4.0 (`LICENSE-CC-BY-4.0.txt`) |

**Licence.** The specification page states: "This specification is released under CC BY
4.0." The schema is the specification's section 6.1 ("Trace Record Schema") in its
machine-readable form, so it is carried here under that licence, with attribution to the
Agent Trace specification authors (Cursor and contributors), <https://agent-trace.dev>.
No changes were made. The specification's GitHub repository (`cursor/agent-trace`, linked
from the page) answered 404 on 2026-10-22, which is why the pin is a Wayback capture
rather than a repository commit.

**One thing the schema and the specification disagree on.** The schema requires
`version` to match `^[0-9]+\.[0-9]+$`, while the specification's examples write
`"version": "0.1.0"`, which that pattern rejects. flowRS writes `"0.1"`, the version the
schema accepts (`provenance::AGENT_TRACE_VERSION`). The published schema is also stricter
than the prose in section 6.1: every object is `additionalProperties: false`, and `tool`
requires both `name` and `version`.