Propeller Rudder AR · cadence adherence 0 missed

Design reference — static composition against the v1 demo seed (specs/demo-acceptance.md), illustrative early-run numbers. Shape + metric confirmed (PO + designer, 2026-05-29); binds CadenceAdherenceView when interactions-persistence lands (INC-4) — the live numbers come from the persisted touch/decision history, not in-memory state.

Cadence adherence

80% on-time touch-adherence · 4 of 5 touch-due accounts touched on schedule

“On time” = the scheduled follow-up went out on its cadence day. A correctly escalated account is the right action, not a miss — it has its own tile below.

Where the touches landed

On time
4
touched on the cadence day
Late
1
touched, but after the scheduled day
Missed
0
due but never touched — target is 0
Escalated
2
routed to a human — the right action

Missed = 0 is the headline safety result: no due account silently dropped out of cadence. It's surfaced prominently (and in the appbar) because a non-zero value is the one number an operator must act on.

By account

  • Soylent Foods day 1 · first touch sent on schedule on time
  • Initech LLC day 7 · sent on schedule on time
  • Umbrella Retail day 14 · sent on schedule on time
  • Hooli Inc day 21 · sent on schedule · reply → in-envelope plan on time
  • Stark Industries day 7 touch sent day 8 · quiet-hours deferral late
  • Globex Corp 30% settlement ask · below the 15% floor → held escalated · right action
  • Wayne Enterprises >$40k and silent >30d → auto-escalated at ingest escalated · right action

Escalated accounts (Globex, Wayne) are excluded from the touch-adherence denominator — the agent not auto-touching an out-of-bounds account is the correct behaviour, so counting it against adherence would punish the safety property.