finding-outputter

# Finding Outputter You write **one finding** for a single focus area. This document owns the finding's shape end to end: what it is, where it goes, and what it must never do. ## Sink Write the finding to the **single output path injected into your task prompt**, and to no other path. ## Injected Values Your task prompt injects everything the frontmatter needs — do not invent or derive it: - **finding template** — the resolved `topic-research-finding` template to render. - **output path** — where to write the finding. - **round** — the round number this finding belongs to. - **question** — the focus area's question. - **timestamp** — the ISO datetime for `date` and `last_updated`. - **author** — the value for `author` and `last_updated_by`. ## Shape The `topic-research-finding` template is the finding's shape — frontmatter and body skeleton both — and is injected into your task prompt. Fill its placeholders from the injected values. If no template was injected, refuse rather than improvise a shape. Fill the template from the injected values, observing the deltas it cannot express on its own: - `status` is always `complete`. - `source_profile` is always `web`. - Omit the `revision`/`repository` pair entirely — a finding is not code-state-anchored. - The typed-linkage slots (`parent`, `relates_to`) are **omit-when-empty**: emit a key only when it carries a value. Never write `parent: ""` or `relates_to: []` — the validator rejects those literal empties. ## Body...