TraceworkReport and replay agent work.

Generate useful work reports first, then capture key session evidence so later agents can query, recall, review, and roadmap the work.

Install

See the Loop

Trace the work

Preserve decisions, rejected paths, risks, artifacts, source refs, and next steps when a session is worth capturing.

Question the record

Ask why a path was chosen and get cited local evidence when the record supports it.

Carry it forward

Turn raw records and limited git coverage into recall context, briefs, reviews, and decision roadmaps without losing drill-down paths.

Keep it local

Store Markdown and JSON in your own vault. No hosted service, account, or remote database.

bash

codex plugin marketplace add KKenny0/Tracework
codex plugin add tracework@tracework

Public namespace: tracework. Config lives under .tracework; records stay in your own vault.

Work Trace Loop

text

report or query current work -> capture key sessions -> improve future reports and decisions

Tracework is built for agent work that needs a durable trace: choices made, paths rejected, evidence cited, risks carried, and next steps preserved. Coding sessions are the strongest fit, but the same record shape also fits research, writing, and product narrative work when the session has decisions and evidence. Daily and weekly reports can start from git-only fallback coverage, but those claims stay limited until raw entries explain the why.

Proof Chain

Layer	Question	Tracework surface
Report fallback	What can be reported now?	`/tracework:daily`, `/tracework:weekly`, `/tracework:monthly`
Raw record	What happened in a key session?	`/tracework:capture`
Decision evidence	Why this path, not another?	`/tracework:query`
Work context	What should the next session carry forward?	`/tracework:recall`
Brief or review	What changed, what is risky, what is next?	`/tracework:weekly`, `/tracework:monthly`
History	How did the decisions evolve?	`/tracework:roadmap`

Boundary

Tracework is not a meeting-notes tool, approval workflow, generic office suite, performance packaging layer, or employee-monitoring surface. It does not turn activity counts into outcomes. It preserves evidence so a later reader can check the work.