biology computer-science performing-arts

​

Cadence

​

Description

The temporal rhythm of a process — the regular interval or event-driven beat at which a system, review, or feedback loop executes. Cadence is the concept that governs when things happen rather than what happens. It is a primitive in its own right rather than a specialization of feedback-loop because its structural properties are distinct: cadence is about periodicity, phase alignment, and the cost of being out of sync with upstream or downstream processes. Cadence has two flavors: interval-driven (daily, weekly, every N deployments) and event-driven (on commit, on user action, when condition fires). Mixing them without intentional reconciliation produces phase-mismatch bugs — a weekly cadence receiving event-driven data, or an event-driven subscriber on an interval-driven publisher, accumulates systematic lag or stale state. The cadence-alignment move is to make the mismatch visible before it accumulates.

​

Triggers

User-initiated: User is discussing when something runs, how often, what triggers it, or whether two processes are in sync. Common formulations: “this runs every day,” “we do this weekly,” “it fires on every commit,” “we batch these.” Agent-initiated: Engine detects a process with an implicit or unspecified rhythm — a rule that “should happen periodically” without stating the period. Candidate inference: “this process has no explicit cadence — what’s the right interval or trigger, and is it in phase with its data sources and consumers?” Vocabulary cues: “cadence,” “schedule,” “interval,” “frequency,” “periodic,” “daily,” “weekly,” “on event,” “batch,” “real-time,” “how often,” “when does this run,” “trigger,” “rhythm,” “tempo.” Situation-shape signals: Any process that runs repeatedly and consumes or produces data for other processes. The concept is most useful when two or more processes interact and their timing relationship is implicit. Also: when an audit lacks a cadence, or a feedback loop has no stated frequency.

​

Exclusions

• One-shot processes — a process that runs exactly once has no cadence to design. The concept earns its keep when recurrence is part of the design.
• Fully real-time systems — systems where every event is processed at arrival and no batching occurs have cadence determined by event rate, not by design choice. The concept is moot unless the question is “what’s the event arrival rate?”
• When timing doesn’t matter — pure batch transforms on static data have no cadence-alignment concerns. The concept earns its keep when timing relationships between producers and consumers are load-bearing.

​

Structure

​

Relationships

• feedback-loop — specialization relationship — feedback loops require cadence to work: how often does the signal arrive and how often does the corrector respond? Cadence specifies the timing of a feedback loop. A feedback loop with mismatched producer/consumer cadences degrades or breaks.
• active-gate-vs-passive-audit — composition relationship — the audit pole of this concept is cadence-dependent: the audit must have a cadence to be actionable. “Audit daily” vs. “audit weekly” vs. “audit on alert” are distinct postures with different signal-to-lag tradeoffs.
• trigger-rule-pair — composition relationship — cadence-driven triggers are a specialization of trigger-rule-pair where the trigger is temporal rather than event-based. “At session end, run X” is a cadence-shaped trigger.
• grain — composition relationship — cadence choices are implicitly grain choices (event-grain vs. day-grain vs. week-grain). Cadence and grain co-determine the unit at which a process operates.
• uniformity-dividend — composition relationship — processes with aligned cadences earn a uniformity dividend: shared debugging, shared monitoring, shared reasoning. Misaligned cadences are a uniformity tax.
• loop-completion — composition relationship — loop-completion diagnostics often surface cadence mismatches: gaps visible because the loop’s cadence doesn’t match the user’s mental model of the journey’s rhythm.

​

Examples