Choose a submission path

All four paths produce the same core contribution envelope and enforce local redaction. The difference is who discovers the source trace and how much control you want to automate.

During the pilot, each path begins by registering a device with an operator-issued invite. Understand invites and enrollment before redeeming one.

If you want to…	Use	Best first step
Select existing Claude Code or Codex sessions from a terminal	Contributor CLI	Build and log in
Review submissions visually and manage project-level behavior	Desktop app	Understand the GUI model
Contribute work produced inside Ironclaw	Ironclaw integration	Enroll Ironclaw
Submit traces from another agent, harness, or product	Direct API	Follow the API flow

A quick decision

1. If the session already exists in Claude Code or Codex, begin with the contributor CLI.
2. If you prefer a review queue and project controls, use a desktop app backed by the contributor daemon.
3. If Ironclaw produced the work, use Ironclaw’s native integration so capture, redaction, queueing, and attribution share the same user scope.
4. If none of those own your trace format, build an adapter that emits the protocol envelope and submits it through the API.

Do not upload a raw transcript

The ingest endpoint accepts a Trace Commons contribution envelope, not an arbitrary conversation export. Start with the envelope contract when implementing a new source adapter.