Decision Evidence Trace
Record public reasons and observable evidence for consequential task decisions.
Workflow
- Confirm the task boundary, audience, retention need, and whether the trace stays in chat or may be written to a named file.
- Default to an in-chat trace. Require explicit file authority before creating or appending to a repository artifact.
- Record only decision-relevant entries with
timestamp, phase, decision, public basis, evidence references, outcome, and supersedes.
- Link to stable evidence rather than copying logs, prompts, source files, or private conversations into the trace.
- Append corrections as new entries. Do not silently rewrite earlier entries when the trace is designated append-only.
- At checkpoints, reconcile open decisions, invalidated assumptions, deviations, and the evidence needed next.
Knowledge lifecycle handoff
When the trace supports a knowledge-contract.v1 lifecycle, map observable research notes to note objects and externally supportable assertions to claim objects. Preserve stable project-scoped IDs, evidence status, editorial status, visibility, limitations, source relationships, and correction links. A correction appends a linked replacement version; it never rewrites a designated append-only entry.
Do not turn private reasoning into a claim object or treat a trace entry as source authority. Route the complete research-to-publication sequence to research-to-publication-lifecycle when that skill is installed.
Boundaries
- Do not record hidden chain-of-thought, internal deliberation, raw model reasoning, or private scratch work.
- Do not include secrets, credentials, personal data, proprietary text, raw transcripts, or unrelated user activity.
- Do not create a surveillance or activity log. Record only the named task's material decisions.
- Do not treat a trace entry as proof that the referenced action succeeded; verify external state separately.
Output
Return the current entries, unresolved evidence needs, and the trace location if a file was explicitly authorized. If a knowledge-lifecycle handoff was requested, include proposed note or claim IDs and relationships separately from the trace.
1---2name: decision-evidence-trace3description: Maintain a bounded decision and evidence trail for a long-running task without exposing hidden reasoning, raw transcripts, secrets, or unrelated activity. Invoke explicitly when the user wants an auditable task log in chat or an authorized append-only file.4license: MIT5---67# Decision Evidence Trace89Record public reasons and observable evidence for consequential task decisions.1011## Workflow12131. Confirm the task boundary, audience, retention need, and whether the trace stays in chat or may be written to a named file.142. Default to an in-chat trace. Require explicit file authority before creating or appending to a repository artifact.153. Record only decision-relevant entries with `timestamp`, `phase`, `decision`, `public basis`, `evidence references`, `outcome`, and `supersedes`.164. Link to stable evidence rather than copying logs, prompts, source files, or private conversations into the trace.175. Append corrections as new entries. Do not silently rewrite earlier entries when the trace is designated append-only.186. At checkpoints, reconcile open decisions, invalidated assumptions, deviations, and the evidence needed next.1920## Knowledge lifecycle handoff2122When the trace supports a `knowledge-contract.v1` lifecycle, map observable research notes to `note` objects and externally supportable assertions to `claim` objects. Preserve stable project-scoped IDs, evidence status, editorial status, visibility, limitations, source relationships, and correction links. A correction appends a linked replacement version; it never rewrites a designated append-only entry.2324Do not turn private reasoning into a claim object or treat a trace entry as source authority. Route the complete research-to-publication sequence to `research-to-publication-lifecycle` when that skill is installed.2526## Boundaries2728- Do not record hidden chain-of-thought, internal deliberation, raw model reasoning, or private scratch work.29- Do not include secrets, credentials, personal data, proprietary text, raw transcripts, or unrelated user activity.30- Do not create a surveillance or activity log. Record only the named task's material decisions.31- Do not treat a trace entry as proof that the referenced action succeeded; verify external state separately.3233## Output3435Return the current entries, unresolved evidence needs, and the trace location if a file was explicitly authorized. If a knowledge-lifecycle handoff was requested, include proposed note or claim IDs and relationships separately from the trace.
JovaniPink