Tracking Implementation

Keep execution state visible in an Implementation Record alongside the selected executor. The executor chooses and performs implementation work; Tracking records it and maintains the evidence, commit and acceptance contracts. Its Tracking Home is the source of truth for the implementation unit.

Activation

Activate when the user requests tracking, or resumes an existing tracked implementation from a ticket, spec, plan, prototype, prompt, or conversation. Read every source the user provides before shaping the implementation.

If the user asks to resume tracked implementation, use resume.md.

Skip tiny one-shot edits unless the user asks for tracked implementation.

Optional Audit Trail

For an explicit Audit Trail or Show Me Your Work request, read and follow Audit Trail. Resume it when the active record already selects it. Ordinary tracking uses no separate decision log.

Artifact presentation

Create new local Implementation Records as HTML unless the user explicitly requests Markdown or another format. When resuming an existing record, retain its format unless the user requests a conversion.

Before creating or updating the Implementation Record, read and follow Show Me. Let it organize the artifact around the work being tracked, choosing representations that make changes, evidence, review findings and continuation context easy to inspect. The record fields below define required content; use them within the chosen presentation rather than as a repeated prose template. Preserve structured state and complete, inspectable evidence within the selected Tracking Home; secondary views follow its synchronization agreement. Use the host’s available file-opening mechanism for HTML artifacts. Distinguish explanatory sketches from verified runtime results.