1. Choose your path
Decide whether the contributor CLI, a desktop app, Ironclaw, or a direct API integration fits your traces.
Trace Commons docs
Enroll a device, choose what to contribute, inspect it locally, and follow the result from receipt to credit or withdrawal.
Start here: from invite to outcome
Section titled “Start here: from invite to outcome”2. Enroll safely
Learn what an invite authorizes, what stays local, and why enrollment does not submit any trace.
3. Preview and submit
Follow the shared local-redaction, preview, consent, authentication, and submission lifecycle.
4. Follow the result
Interpret receipts, privacy holds, acceptance, credits, community snapshots, and withdrawal reach.
Consent travels with every trace throughout this journey. Review consent and redaction before enabling message text, reasoning, or tool payloads.
Four ways to contribute
Section titled “Four ways to contribute”Contributor CLI
Discover Claude Code, Codex, or Letta Trajectory sessions. Dry-run, filter by project or date, then upload only the sessions you select.
Desktop apps
Review a redacted preview, approve once, or explicitly arm a project for future uploads through the native contributor interface.
Ironclaw
Enroll an Ironclaw instance or user, capture eligible traces locally, and let its bounded queue worker submit under a standing policy.
Direct API
Build your own client against the versioned contribution envelope and short-lived upload-claim flow.
The rule that applies everywhere
Section titled “The rule that applies everywhere”Raw session files stay on the contributor’s machine. A client parses and redacts locally, applies the contributor’s consent scope, and submits a versioned envelope. The server validates and re-scrubs every envelope before accepting it into the register or holding it for review.
Current deployment
Section titled “Current deployment”Trace Commons is in an active pilot. These pages were aligned on 12 August 2026 with the merged server and Ironclaw source listed in Verified source versions. The production ingest and issuer health endpoints were also healthy at verification time.