PM-EVT-0030

An implementation MUST NOT provide any transition trigger other than an inbound Event. In particular it MUST NOT provide timers, schedules, expiries or any wall-clock-driven transition.

Non-normative: DESIGN, because this is an absence in the sources rather than a statement by them, and an absence cannot carry a quote. The evidence is a search: the words timer, time-triggered, scheduled, elapsed, timeout, temporal, periodic, clock and duration do not occur anywhere in the 70,276-word patent file. Method and scope in docs/reading/patent/description-read-2026-09-08.md; the open question is Q-G-0011, answered negative.

This is recorded as a MUST NOT rather than as an observation because the absence is almost certainly deliberate and is worth defending. A wall-clock trigger is precisely the ambient input PM-DET-0020 forbids, and it would make PO-0004 — bit-identical replay — unachievable. "After 30 days, expire" is expressible: something outside the domain notices the 30 days and sends an Event. That keeps the clock outside the replay boundary, where it belongs.

Adding a timer later would not be a feature. It would be a change to the determinism contract, and it should cost an ADR.