Harness Kit

skill

trace

Capture agent-session work records as local JSONL audit evidence. Links a backlog/spec, branch, commits, review verdicts, QA/demo evidence, transcript refs, and shipped ref without storing raw private transcripts. Use when: "trace this work", "write work record", "agent session trace", "journal this delivery", "link transcript evidence". Trigger: /trace, /journal.

/trace

Source: skills/trace/SKILL.md

What it does

Capture agent-session work records as local JSONL audit evidence. Links a backlog/spec, branch, commits, review verdicts, QA/demo evidence, transcript refs, and shipped ref without storing raw private transcripts. Use when: "trace this work", "write work record", "agent session trace", "journal this delivery", "link transcript evidence". Trigger: /trace, /journal.

Workflow role

Support primitive in the Harness Kit operating loop.

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Capture the work record, not the raw conversation.

`/trace` is the durable session-lifecycle primitive. It writes sanitized JSONL
records that link a unit of work to its backlog/spec, branch, commits, reviewer
verdicts, QA evidence, demo evidence, transcript refs, and shipped commit/ref.
The default store is `.harness-kit/traces/work-records.jsonl`.

## Delegation Floor

Trace append/preview commands are usually mechanical and may run direct solo.
Delegation floor applies when the trace requires substantive evidence
classification, provenance judgment, redaction-risk review, or conflicting
artifact synthesis: probe the roster first; dispatch two or more providers;
direct solo only for mechanical, emergency, user-forbidden, or
fewer-than-two-providers cases. See `harnesses/shared/AGENTS.md` (Roster).

Local lane guidance: Use specialized lanes for evidence classifier,
redaction-risk critic, and provenance verifier. Store refs and receipt ids,
not raw provider transcripts.

## Contract

- Local-first. No hosted transcript database and no network writes.
- Append-only. Do not rewrite commit history to add trace evidence.
- Store refs, not raw transcripts. Use `/agent-transcript` to render a scoped,
  redacted transcript excerpt before attaching it.
- Persist a transcript ref or a clear waiver reason. "No transcript available"
  is acceptable only when the work record says that plainly.
- Fail closed on obvious secrets: token/API-key/password/credential names,
  bearer strings, private customer-data labels, or secret-like metadata.
- Link evidence by path, PR section, Git note ref, receipt id, or URL. Do not
  paste raw provider transcripts into the JSONL row.

## Helper

```bash
python3 skills/trace/scripts/trace_record.py append \
  --backlog 056 \
  --branch "$(git branch --show-current)" \
...

What to verify