Forcing Functions Calendar · 8 active
The deadlines the system
optimizes against.
Workshops, launches, weekly releases. Each biases producer dispatch decisions during the classifier cross-reference phase. When a drop arrives within the window of an active function, the matching platform's persona gets prioritized.
Source: data/forcing-functions.json
How the calendar feeds production
Calendar is not a to-do list. It's a bias function.
When `content-intake-classifier` reads a new capture, it walks 5 cross-reference signals in order. The forcing-functions calendar is the first signal — the highest-leverage context for "what should this content prioritize."
A voice memo dropped 3 days before NLDigital biases toward LinkedIn + newsletter variants. A travel photo dropped on a Friday biases toward Instagram + Spotify-companion cross-promo if a music release is also scheduled. The classifier readsforcingFunctionsInWindow(7)and weights accordingly.
When a forcing function passes, it auto-marks `state: completed` (or moves to next occurrence for recurring). The bias falls off. The system stays current without constant manual upkeep.