decision-synclisted

# Decision sync The `aim` → `cross-check` → `own` skills produce a `discernment-<slug>.md` in whatever directory you were working in. That file is where the reasoning lives while the decision is open. This skill moves the finished record into the vault, where it survives the repo it was made in. Run it once a decision is actually made — after `own` has written its section. A decision still in progress belongs in the working directory, not the vault. ## Where records go | Situation | Destination | |---|---| | Decision is about a specific active project | `Projects/<project>/decisions/` | | Everything else — tooling, workflow, standing policy | `Areas/Decisions/` | Ask which project only when the working directory doesn't make it obvious. Never invent a project folder; if no match exists, use `Areas/Decisions/`. ## Workflow 1. **Find the source.** Look for `discernment-*.md` in the working directory. If several exist, ask which one. If none exists, say so and stop — don't reconstruct a decision record from the chat. 2. **Check it's finished.** The file needs a populated `## Own` section. If `## Own` is missing or empty, tell the user the decision isn't captured yet and offer to run `own` first. 3. **Read it and write the vault note.** Preserve the reasoning verbatim — the Aim framing, the rubric result, the confidence calibration, the case against, and the final call. This record's value is that it shows the thinking, not just the outcome. Do not summarize