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 run-research-workflow 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
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
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.
Example
Synthetic example; not an observed client result.
Input: Record the decision to keep the old endpoint until client migration completes.
Output: Decision: retain the endpoint. Status: approved for this task. Evidence needed for removal: current client migration completion; no removal authority is implied.
1---2name: trace-decisions3description: "Maintains a decision log when explicitly asked to record choices, evidence, and unresolved work across a task; excludes hidden reasoning, raw transcripts, and unrelated private context."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/trace-decisions7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "explicit"11 provenance: "original"12 risk_class: "bounded-execution"13---1415# Decision Evidence Trace1617Record public reasons and observable evidence for consequential task decisions.1819## Workflow20211. Confirm the task boundary, audience, retention need, and whether the trace stays in chat or may be written to a named file.222. Default to an in-chat trace. Require explicit file authority before creating or appending to a repository artifact.233. Record only decision-relevant entries with `timestamp`, `phase`, `decision`, `public basis`, `evidence references`, `outcome`, and `supersedes`.244. Link to stable evidence rather than copying logs, prompts, source files, or private conversations into the trace.255. Append corrections as new entries. Do not silently rewrite earlier entries when the trace is designated append-only.266. At checkpoints, reconcile open decisions, invalidated assumptions, deviations, and the evidence needed next.2728## Knowledge lifecycle handoff2930When 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.3132Do not turn private reasoning into a claim object or treat a trace entry as source authority. Route the complete research-to-publication sequence to `run-research-workflow` when that skill is installed.3334## Boundaries3536- Do not record hidden chain-of-thought, internal deliberation, raw model reasoning, or private scratch work.37- Do not include secrets, credentials, personal data, proprietary text, raw transcripts, or unrelated user activity.38- Do not create a surveillance or activity log. Record only the named task's material decisions.39- Do not treat a trace entry as proof that the referenced action succeeded; verify external state separately.4041## Output4243Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.4445Return 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.4647## Example4849Synthetic example; not an observed client result.5051Input: Record the decision to keep the old endpoint until client migration completes.5253Output: Decision: retain the endpoint. Status: approved for this task. Evidence needed for removal: current client migration completion; no removal authority is implied.