Open format · version 0

The Crew Record

Crew Lens draws what a crew of coding agents did from one document, the Crew Record: who worked on what, who reviewed it, which messages went where, and the moments worth finding again. Its format is open, under CC BY 4.0, so other harnesses can write it and other tools can read it.

JSON Schema, version 0 See it replayed

What it holds

One JSON document per crew and stretch of time. Times are in UTC, and agents, work items and sprints keep the ids they have in the harness that wrote the record.

`agents`	The crew: each coding agent and the human operator, with its model family, model and reasoning effort, its roles (producer, reviewer, sprint master), its projects, and when it started.
`work`	Work items: who built each one and who reviewed it, its states and review rounds, its reports, and what it changed in git (files, lines added and removed, commits).
`sprints` `projects`	Sets of work items with one goal, their members, and how much code their scope covers.
`deliveries` `events`	The traffic: each message between agents and with the operator, as metadata (sender, recipient, kind, size, when it was sent, seen and answered), and the time-ordered stream the replay plays.
`fanouts` `stalls` `findings` `cyber` `models`	The moments worth finding again: sub-agent fan-outs, stalls, the Sentinel's findings of drift, the cyber classifier's warnings and holds, and the model and effort each agent asked for against the ones it was served.
`nudges` `glow`	The operator's nudges, and a coarse activity series for each agent.

What it leaves out

Message bodies, prompts, code and diffs. A message is in the record as who sent it to whom, when, of what kind and how large; what it said is not. A work item can carry its title and its commit subjects, and optionally its brief and its producer's last progress note. A harness that wants to keep its work private can leave all of these out.

Where it runs

Crew Lens is an app, not a hosted service. It runs next to your coding agents, reads the Crew Record where your harness writes it, and draws it in your browser. It does not send the record, or anything else about your crew, to RAIVEN or to anyone else. Your agents are yours, and so is their track record.

The coding agents themselves are another matter. Claude Code, Codex and their peers send your prompts and code to their vendors to do the work, under those vendors' terms, with or without the lens. The lens adds nothing to that traffic.

Where it comes from

Today one harness writes the Crew Record: RAIVEN's own, which runs a crew of Claude and Codex agents, from its store of work items, reviews and messages. That is where the format started, not a limit on it. It is open so that other harnesses can write it too.

Next, the series for each agent (how full its context window is, when it compacts, how busy it is) are to come from the coding agents' own session files, read on the same machine: Claude Code's session transcripts and Codex's session rollouts. After that, adapters for plain Claude Code and Codex setups, with no RAIVEN harness in between.

Real, derived or synthetic

Each row can say where it came from, in its source field. A row read from a primary record, such as the harness's store or an agent's transcript, is real. A row computed from real ones is derived, such as the lines of code under a sprint's scope. A row made up for a demo is synthetic, and says so.

A part that is absent was not recorded; it does not mean that nothing happened, and a reader must not count it as zero. A crew with no stall feed has not been shown to be free of stalls.

The record behind the timeline figures on this site is of the mixed kind: its work items, reviews and convergences are real; 1,068 of its messages are real but were moved in time into their work windows (synthetic, with the recorded time in retimed_from); and its incident marks are synthetic data, though each kind of incident is real and observable in the source crew.

Versions

Version 0 is the format Crew Lens reads today. Files written by current builds may carry the earlier identifier raiven.crew_lens_fixture.v1, which names the same format.

Version 1 is planned to add:

for each agent, context window use and compactions, activity and liveness, in place of the coarse activity series;
token usage per turn, with the model and effort served, and a dated price table, so that cost is computed rather than carried;
the operator's pending decisions (approvals);
a required provenance field on every row: real, derived or synthetic;
ingest as NDJSON or OpenTelemetry (OTLP), so that a harness can stream the record as it goes;
a mapping to OpenTelemetry's conventions for generative AI (its agent conventions are still marked Development), with crew extensions for messages, reviews and sprints;
a validator, test records, and adapters for Claude Code and Codex.

The schema

The format is written down as a JSON Schema (draft 2020-12). Fields it does not name are allowed, and a reader that does not know them ignores them. A shortened example:

{
  "schema_version": "crew-record.v0",
  "generated_at": "2026-08-31T09:00:00Z",
  "agents": [
    { "id": "c2", "family": "claude", "model": "fable-5.1", "effort": "max",
      "roles": ["producer", "reviewer"] },
    { "id": "x4", "family": "codex", "model": "codex-sol", "effort": "extra",
      "roles": ["producer", "reviewer"] }
  ],
  "work": [
    { "id": "W3c", "producer": "c2", "reviewer": "x4",
      "created_at": "2026-08-30T19:02:11Z",
      "work_state": "completed", "review_state": "converged", "round": 2,
      "git": { "files": 7, "insertions": 312, "deletions": 41, "commit_count": 3 } }
  ],
  "events": [
    { "at": "2026-08-30T21:14:05Z", "type": "delivery", "kind": "review request",
      "from": "c2", "to": "x4", "size": 1840, "work": "W3c" }
  ],
  "cyber": [
    { "agent": "x4", "work": "W3c", "action": "hold",
      "classifier": "model vendor's cyber classifier",
      "started_at": "2026-08-30T23:05:12Z", "ended_at": "2026-08-31T08:52:30Z",
      "source": "synthetic" }
  ]
}

Licence

The Crew Record, this description of it and its JSON Schema, is licensed under Creative Commons Attribution 4.0 (CC BY 4.0). Use it, share it and adapt it, commercially too, as long as you credit it (“Crew Record by RAIVEN”, with a link to this page), link the licence and say what you changed.

Design partners

RAIVEN is looking for design partners: teams that run long-horizon coding agents (Claude Code, Codex or others, in a harness of their own) and want to watch their crew in Crew Lens. Design partners bring a real crew and its records, help shape version 1 of the Crew Record and its adapters, and are the first to see their own crew in the lens.

To take part, to write the Crew Record from your own harness, or to comment on the format, write to info@agenticobservability.app.

Last updated 26 September 2026.