/re0-decide

name: re0-decide
description: "Turn material submitted for a decision into a traceable, checkable instrument whose verdict is computed from the decider's own answers, never recommending an outcome."
disable-model-invocation: true

Turn material submitted for a decision into an instrument the decider can check, with the verdict computed from the decider's own answers.

Goal

The input is material somebody else submitted for a decision (a proposal, a spec, a request), and the person who holds approval authority invokes this skill on it. The output is an instrument the decider can check: it sets criteria and computes an outcome from the decider's answers. It never renders the decision, ranks toward an outcome, or states a preference.

The property it can defend is traceability, never neutrality. Classifying a sentence as a gate versus a judgment is itself a judgment, so every item cites its source location and the decider may edit the instrument before answering anything. It never claims neutrality.

The skill is user-invoked because only the person who holds the decision may turn submitted material into the instrument that will decide it. A version within the model's reach would bias the agent toward pre-deciding proposals.

Workflow

1. **Extract.** Extraction runs before any surface is built. Emit these eight elements from the material:

• **Material identity**: binds the instrument to one identified version of the material, by the commit, file hash, version label or URL with retrieval date the material carries. Always emitted.
• **Gates**: conditions the material states as required and that are true or false on inspection, and what breaks when each is false. Always emitted.
• **Judgments**: calls the material leaves the decider to weigh, and the condition each unmet call creates; met means the decider accepts it. Always emitted.
• **Forks**: values the decider must choose among named alternatives, with any fallback the material gives, shown as text and never preselected.
• **Human intervention points**: moments during execution that need the decider's time or authority.
• **Exclusions**: what approval does not authorize.
• **Admitted risks**: risks the material names, with its stated handling.
• **Verdict and decision record**: the rule-derived state plus text recording the decision with its conditions. Always emitted.

2. **Report what is missing.** Forks, human intervention points, exclusions and admitted risks are emitted only when the material contains them. Each absent one is reported as missing criteria, and so is a gate's consequence or a judgment's condition the material does not state. Missing criteria are output, never silence. 3. **Size to the material.** Size follows the material: one gate in means one gate out. There is no template and no size dial. Thin material must read as thin. 4. **Tag every item.** Every emitted item carries a citation to its source location (file and line, section heading, or a quoted fragment of pasted text), a mark saying evidenced when the material cites or attaches support for it and claim when it only asserts it, and an answerer tag from the closed set: `artifact` when the material or an attached artifact answers it, `submitter` for the person who submitted it, `delegate` for someone the material or the decider names to check on the decider's behalf, `decider` when only the decider can. Choose the least senior answerer who can answer from what they hold, so the decider's queue shrinks. A claim that no named answerer can check is stated as unverifiable, never dropped. 5. **Make each criterion checkable.** Every criterion is checkable by someone reading it, with a stated test instead of an unsupported quality judgment. 6. **Choose the output form.** Build a page only when it shows something a text reply cannot: an option names an image to compare, the decider has more than five answers to give, or the material names a reader the decision record is handed to afterwards. Otherwise the decider is in the conversation and answers faster from a short numbered list: number each decision, letter its options, ask for answers in the form `1B 2A`, carry the same eight elements in the list, and state the verdict rule in words. Read this from the extraction, never from the invoker. 7. **Put the decider's answers first.** The page gives each decision the decider answers its own screen, forks first, then judgments, then the gates the decider checks, and folds every item a non-decider answers into one counted section after them. Intervention points, exclusions, admitted risks and missing criteria render as tagged text with no control. 8. **Show the evidence on the item.** Give each item a short `title`, and copy into its `quote` the source lines the decider would otherwise open, word for word. Give a fork's option its `detail` and `consequence` only where the material states them, and its `image` when the option is a picture, downscaled to 1 MB or less with its metadata dropped; the original file stays untouched. Mark an option that postpones the decision with `defer`, so choosing it keeps the verdict open. Set `material.lang` to the material's language so the page speaks it. 9. **Render.** Write the items, with their tags and citations, to a decisions file and run `node scripts/render.mjs <decisions.json> [--out <file.html>]`, which writes the one-file surface beside the material (or at `--out`, where the decider names) and exits 2 naming the field of a schema violation or an unusable image, or 3 when a numbered list serves better. Give the surface path in the reply. The bundled [rendering contract](references/rendering-contract.md) owns the decisions schema and the judgment rules the script cannot decide. To correct a classification, the decider edits the decisions file or runs the skill again with the correction.

Rules

• Never invent a gate or any other item to make the shape look complete. An invented plausible criteri