Consensus Summary HTML

Create one HTML page that helps a reader understand a council result in under a minute, then inspect the evidence without opening the raw transcript.

Outcome spine

• Result: one self-contained .html file with inline CSS and JavaScript.
• Next consumer: the person who must adopt the recommendation, challenge it, or hand it to the next workflow step.
• Done: the output exists, the bundled validator exits 0, every visible claim has a source or an explicit evidence gap, and the page contains no template tokens.
• Intent: build a decision surface. A decision surface leads with the outcome, then lets the reader descend from claims to evidence, disagreement, confidence, and action.

When you describe your work, use the leitwort: “The decision surface leads with the outcome and keeps unresolved evidence visible.” Use lead with the outcome as the first layout rule, not as a late summary note.

Input contract

Use the completed models-consensus result. Do not run another council and do not revise the council decision.