Read the explanation
Publish Flight Deck initially displays three checked verification gates: human diff review, rollback snapshot, and links and claims checked. It also displays a score of one hundred out of one hundred. The two bars both span three hundred pixels, but use distinct units: one hundred pixels per checked gate and three pixels per displayed score point. These are static initial values. The saved local page lacks its referenced app script, so clicking Load risky case leaves the score and permission scope unchanged. The display does not prove a risk calculation, a reviewed diff, or deployment approval. The permission slider presents three positions. Zero is draft, one is edit, and two is publish. Moving from zero to two traverses two scope steps, drawn at one hundred fifty pixels per position as bars of zero and three hundred. These ordered labels describe increasing intended authority, not a probability or a quantitative risk scale. In this offline copy the slider can move natively, but the missing script does not regenerate the decision or packet. Do not treat a changed input and an unchanged readiness badge as successful authorization or evidence that a site was published. If human review is unchecked while rollback and claims remain checked, the visible checked-box count falls from three to two. At one hundred pixels per checked box the bars shrink from three hundred to two hundred. Counting boxes is possible from the markup; assigning a risk penalty would require the unavailable engine and is not inferred here. A rollback declaration does not prove that a known-good copy exists, and checked claims do not prove a source verification. The intended durable output is an approval and rollback packet, but this local copy cannot demonstrate packet generation or JSON export. It remains planning UI rather than operational evidence.