Record Verdict

Record a human's explicit lifecycle verdict on a single thread artifact by setting the one set-once status latch that matches it, inside the artifact's YAML frontmatter status: map. The skill resolves the artifact, detects its type, confirms the verdict is one the artifact's vocabulary allows, captures a UTC stamp, writes the latch nested under status:, and reports the artifact's new derived condition. It edits ONLY the frontmatter status latch — never the body — and it NEVER decides the verdict itself.

This skill restates the rules it relies on inline; it does not depend on any document outside its own folder.

It Records a Decision; It Does Not Make One

This skill is human-gated. It records a verdict the user has already reached — it never forms, infers, or rubber-stamps one.

• It NEVER reviews or judges the artifact's content. Whether the proposal is sound, the spec handoff-grade, or the review's findings correct is not this skill's question. Recording a verdict is a clerical act layered on top of a decision that already happened.
• It NEVER infers approval (or rejection, or acceptance) from context, from the artifact looking finished, or from the user's general enthusiasm. The verdict must be explicit.
• If the verdict is not explicit, or which artifact it applies to is unclear, ASK — do not guess. There is no "approve the obvious one" and no "most recent lineage" fallback.

If the user asks this skill to evaluate the artifact and then record the result, decline the evaluation half: surface that the verdict is the user's to make, and record only once the user states it.

Inputs

Two inputs, both required before anything is written: