Trust is a runtime property
A policy that says harmful content never surfaces without review is enforced by a latency number, not by the document that states it. Drag the slider.
The trust question for AI systems gets asked at the wrong time — during design review, red-teaming, model evals — and by the time the system is live it feels settled. It isn't. Take a safety classifier: content passes through it before surfacing, and a flag routes to human review. The logic is sound; the failure is runtime. Chat has a 50ms latency budget, feed has 200ms, and those numbers mark where a response stops feeling like a response. If the classifier finishes inside that window you get synchronous review. If it misses, you've silently changed your policy — not in a document, at runtime — to either show flagged content anyway or hold it for async review. I built a slider to make this concrete: drag it and the classifier's latency crosses 50ms, and the review path flips from synchronous to async with no smoothing, because the flip is sudden in production too. This matters because latency gets treated as an infrastructure problem engineers optimize, not a policy variable the safety team signed off on. Cross-org model integration makes it worse — a classifier that runs at 40ms alone runs at 70ms waiting on an upstream service. The slider doesn't fix the gap. It just makes the tradeoff visible, which is where the honest conversation has to start.