Skip to main content

Event Calendar

If the calendar only tracks external shocks, the inner loop is invisible — and what is invisible cannot be tuned.

The event calendar holds two layers: external events that shape strategic context, and the inner cadence that keeps the loop running. Both belong in one view because both consume the same finite week.

External Events

Events that shape strategic context:

CalendarFrequencyDecision Tree
Federal Reserve8x/yearRate decisions move markets, affect runway
Industry conferencesQuarterlyNetwork, signal, positioning
Tax deadlinesQuarterly/AnnualFinancial planning constraints
School terms4x/yearFamily rhythm shapes work rhythm
Digital security reviewQuarterlyPasswords, 2FA, access audit

Inner Cadence

Every station in the loop needs a named touchpoint. If the station has no block, the station has no rigor.

CadenceEventDurationStation
DailyDay open + close30 minCapture + Reflect
DailyConfig health scan3 minStandards
WeeklyWeek open (Mon) + mirror (Fri)60 minFilter + Evolve
WeeklyConfig health review20 minStandards
MonthlyMonth open + trend recognition90 minEvolve
MonthlyConfig health full audit55 minStandards
Per-sprintDebate open → close window1-3 daysFilter
Per-deployProduction dogfood15 minGauge

Inner cadence is scheduled, not improvised. When a Debate window appears on the calendar, the Council knows the pump is locked until close. When a dogfood block appears, the deploy has a named moment of truth instead of a vague "someone will check."

Context

Questions

If the external calendar is full and the inner cadence has no blocks, which loop is actually running the team?

  • When a Debate window lives on the calendar, who owns closing it — and what happens if no one does?
  • If config health has a daily 3-minute scan and a monthly 55-minute audit, why does the monthly still surprise you?
  • What does your per-deploy dogfood block look like — and if it does not exist, what stands in its place?