Expand description
Tick policy under load — drop / coalesce / tear (T68).
When tick events arrive faster than the engine can process them, the system must have an explicit policy. Without one, animation and sensor fusion lie — they report stale data as if it were current, or drop frames silently.
§Three policies
-
Drop: discard ticks that arrive while a previous tick is still being processed. The next tick after the current one completes is processed normally. Simple, but loses information.
-
Coalesce: merge pending ticks into a single tick that carries the latest timestamp and a count of dropped ticks. Preserves temporal recency at the cost of intermediate states.
-
Tear: emit a
TopologicalTeardiagnostic when ticks are dropped, so the principal knows the system is overloaded. The tear carries (μ, λ) evidence: μ = how many ticks were dropped, λ = the latency of the last processed tick.
The default is Coalesce — it preserves the most information while preventing unbounded queue growth. The policy is a host constant, not a language constant (per T46 design principle).
Reference: docs/vibescript-full-impl-PLAN.md §8.14 T68,
excellence-first §3.9.
Structs§
- Tick
Decision - The result of applying a tick policy to a queue of pending ticks.
- Tick
Event - A tick event — a timestamped signal from the host’s tick loop.
- Tick
Queue - A tick queue with a policy. Bounded — never grows unboundedly.
Enums§
- Tick
Policy - The tick policy — what happens when ticks arrive under load (T68).