# Runtime fallback · priority decision candidate

Source pin: `1ceae52c7896a59ac74a4429d410f3218f0b91c6`. Guide: `psyche-lilith`.
Slide: `psyche-runtime-fallback`. This extends the current composition pilot; it
is not an accepted benchmark.

Visual thesis: a compact, open decision ladder in cream, ink and terracotta
shows which signal owns the call, with a clear split between returned candidate,
error and unchanged mode. Conditional branches, not equal boxes or implied
consumer execution, carry the explanation.

Content plan: name the priority-versus-restrictiveness distinction; follow the
six source-ordered supplied/not-supplied decisions; gather supplied branches at
selected-signal validation; separate valid downgrade from thrown error and the
no-signal result. Keep the worked voice-versus-block counterexample and target
normalization details in notes. End with independent caller safety/capability
obligations. Read the diagram assuming a valid current mode; that input is
normalized before selection and invalid input throws earlier.

Interaction thesis: retain existing slide entrance, source disclosure and
workspace transition, with reduced motion. No reveal or animation is necessary
to understand this complete static decision. Narrow screens must preserve each
condition, true/false destination and terminal result in text, not collapse to
an unlabeled list.

The pinned `selectFallbackTrigger` order is kill switch, policy, accessibility,
provider, quality and latency. A supplied signal is validated immediately; a
failure does not fall through. Only absence proceeds to the next test. A valid
selection returns its target to forced downgrade normalization. No signal
returns the current mode. Lower-priority constraints are neither merged nor
validated. The actual caller must still apply independent safety and capability
requirements; this diagram does not endorse a weaker policy result.

A reusable priority-decision contract should allow a content-determined number
of tests, explicit entry and labeled destinations, exactly one selected
validation node, valid/error outcomes and a no-match result. Geometry belongs to
the renderer. Changing order, skipping a condition, cycling or swapping a
terminal role must fail source/semantic verification instead of silently
changing meaning. More general trees and ownership diagrams remain separate
repertoire work.

Before reader sessions, add neutral tasks: Which input decides the result when a
voice kill switch and blocking policy are both supplied? What happens when the
selected signal is malformed? What can the caller claim when no signal is
supplied? Assess the complete eleven-slide web/PWA sequence and other pilot
examples separately; this decision alone cannot establish full pilot rhythm or
comprehension.
