Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Since March 2026, TRACE has recorded my AI-assisted engineering as structured, attributable records. In a snapshot taken Nov 1, 2026, the records from 5 project workspaces hold 267 sessions, 430 decision records (who proposed, who resolved), 584 contribution records (who had the idea, who did the work), and 68 annotations tagged correction. Of the 335 decision records the agent proposed, 32 were rejected or revised by a human.

TRACE is the open-source MCP server I built to record, during AI-assisted work, who proposed each decision, who resolved it, and who had the idea and did the work for each artifact. proofpress ingests these records; I co-founded Continuara Labs, the company building it.

The evidence: decision chains →

Twelve real chains from these records, drawn as linked graphs: an agent’s proposal and how I ruled on it, or a mistake and the correction that points back at it.

By project

ProjectSessionsSession startsDecision recordsRejected or revisedContribution recordsTagged correction
TRACE137Mar 18 to Oct 14, 20261721926631
proofpress5Sep 30 to Oct 15, 202661111
proofpress experiments45Sep 23 to Oct 29, 20261641413618
COEQWAL56Jun 5 to Oct 29, 202654312513
RSI-Exam provenance study24Sep 3 to Sep 10, 2026341465
All projects267Mar 18 to Oct 29, 20264303858468

Session starts by week

Stacked bar chart of recorded TRACE session starts per week, March to November 2026, by project.Stacked bar chart of recorded TRACE session starts per week, March to November 2026, by project.

One session can run for days, so a quiet week is not a week without work.

Who had the idea, who did the work

In most contribution records, the idea is human and the execution is AI.

Horizontal stacked bars showing, for each project, the share of contribution records by direction and execution.Horizontal stacked bars showing, for each project, the share of contribution records by direction and execution.
Table view
ProjectHuman idea, AI builtShared idea, AI builtAI idea, AI builtHuman or shared executionTotal
TRACE18351248266
proofpress1001011
proofpress experiments7252111136
COEQWAL982430125
RSI-Exam provenance study4051046
All projects403132409584
Methods and limits
  • Self-logged. The agent and I write these records during the work. Each entry is attributable (it names who proposed, resolved, or did the work), but the records are not independently checked.

  • Scope. Five project workspaces: TRACE, proofpress, proofpress experiments, COEQWAL (contract client work), and the RSI-Exam provenance study. Other projects and all meeting recordings are excluded.

  • Human entries. Mine, except in the co-owned and client workspaces, where a few come from collaborators.

  • Counting unit. Counts are records, not distinct choices: a decision that is revised and then accepted can appear as more than one record. Rejected or revised counts decision records with that stored disposition. Counts measure recorded activity, not output or quality.

  • Snapshot. Generated 2026-11-01 01:06 UTC. A session whose latest recorded timestamp is on or after 2026-10-31 (UTC) may still be in progress and is left for the next snapshot. A later snapshot can restate earlier weeks.

  • Coverage. 267 sessions across TRACE format versions 0.3.0 (36), 0.4.1 (76), 0.5.0 (76), 0.5.1 (79). 128 sessions lack a canonical project key and were matched to their project through the TRACE alias registry.

  • Status. 18 counted sessions are not marked completed; their events are counted as recorded.

  • Resolution. 109 of 430 decision records still have the stored disposition proposed, and 109 have no recorded resolver. They are counted, not dropped.

The aggregates are published as evidence.json. The code that computes them reads my local TRACE store read-only and is part of this site’s repository.