Shared Cycle Calendar¶
Artifact — instantiates Cycle Phase Alignment
A calendar or visual artifact that shows recurring cycles, phases, usable windows, and dependency points across actors.
Before anyone can fix a phase mismatch, they have to be able to see it — and the mismatch is usually invisible precisely because each cycle lives in a different team's separate calendar. Shared Cycle Calendar is the artifact that draws every interacting cycle on one surface: each cycle's recurrence and phase, its usable windows and blackout periods, and the dependency points where one cycle's output must meet another's window. Its defining idea is that it represents rather than acts — it changes nothing about timing itself; it makes the relative timing legible so that people and other mechanisms can reason about it. It is the map, not the move. Its whole value is that a mismatch which was diffused across a dozen private schedules becomes a single obvious gap that anyone can point at.
Example¶
A university runs on a tangle of recurring cycles that nobody sees together: the academic calendar (terms, exam weeks, breaks), the athletics season (home games, travel), facilities (an annual HVAC shutdown, resurfacing cycles), and the events office (conferences, admitted-student days). Every year they collide — a conference is booked into a week the HVAC is off, or a facilities closure lands on a home game — because each office plans against its own calendar alone.
The shared cycle calendar puts all four on one wall (and one live dashboard). Each cycle is a lane; its recurrence and current phase are drawn to a common timeline; usable windows and blackout periods are shaded (the HVAC-off week is a hard blackout for indoor events); and dependency points are marked where one cycle needs another's window — event bookings must fall inside facilities-available windows and outside exam weeks. The artifact doesn't decide anything, but the moment it exists the collisions are obvious months ahead, and the offices can negotiate. It is what every alignment procedure in the building reads from.
How it works¶
- One surface, many lanes. Each interacting cycle is a lane on a shared timeline so phases can be compared at a glance rather than reconstructed from separate calendars.
- Draw phase, not just dates. Show where each cycle is in its recurrence and how far its output sits from the cycle that needs it, so offsets are visible as gaps.
- Shade the windows. Mark usable windows and blackout periods explicitly, because usability — not the due date — is what alignment is judged against.
- Mark the dependency points. Flag exactly where one cycle's output must land inside another's window; those marks are where mismatch will show.
Tuning parameters¶
- Granularity — day-level versus week- or month-level lanes. Fine granularity exposes tight collisions but clutters the view and demands constant upkeep; coarse granularity stays readable but hides short windows.
- Scope — how many cycles are drawn. Broad scope reveals cross-institution mismatch but risks an unreadable wall; narrow scope is clean but can miss the cycle that actually matters.
- Refresh cadence — how often the artifact is updated to current phase. Frequent refresh keeps it trustworthy but costs stewardship; a stale calendar is worse than none because it misleads confidently.
- Annotation richness — how much window and dependency detail is shown versus bare dates. Richer annotation supports real alignment but raises the maintenance burden.
When it helps, and when it misleads¶
Its strength is making relative timing a shared, glanceable object — a classic information radiator whose value is that everyone sees the same picture without asking.[n1] It is the substrate the acting mechanisms consume: budget sequencing, release trains, and maintenance windows all reason against the map it provides.
Its failure mode is the archetype's signature trap, calendar-only alignment: the cycles are neatly drawn, everyone feels coordinated, but because the artifact only displays and never adjusts, the underlying phase mismatch is untouched — the collision is now well-documented and still happening. A classic misuse is mistaking the map for the intervention and declaring victory once the calendar is pretty. The guarding discipline is to treat the calendar strictly as input to an acting mechanism (a synchronization rule, a readiness gate) and to check that some cycle actually moved because of what the calendar revealed — otherwise it is decoration.
How it implements the components¶
cycle_map— its core: represents every interacting cycle's interval, duration, phase, outputs, and dependency points on one surface.phase_offset— renders the relative timing between cycles at each dependency point as a visible gap, so early/late/drifting relations can be read directly.usable_window— shades the intervals (and blackout periods) during which each receiving cycle can actually use a handoff, making usability explicit rather than implied by a due date.
As a passive artifact it does not itself adjust timing: it leaves synchronization_rule and timing_authority to acting mechanisms like Release Train Alignment and Budget–Planning Alignment, and does not perform per-handoff verification via handoff_condition or readiness_gate — that is Handoff Readiness Check.
Related¶
- Instantiates: Cycle Phase Alignment — provides the shared representation of cycles, phases, and windows the pattern depends on.
- Sibling mechanisms: Budget–Planning Alignment · Maintenance Window Coordination · Synchronized Production Cycles · Release Train Alignment · Handoff Readiness Check · Retrospective Before Planning · School–Work Schedule Coordination · Circadian Schedule Alignment
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Shared Cycle Calendar operates by externalizes multiple recurring cycles as aligned lanes and phases on one shared timeline. That concrete deployed or enacted form is Representation, Specification & Plan under the frozen taxonomy.
Nearest alternative: Interface, Display & Cue — Although Interface, Display & Cue can support this mechanism, the frozen evidence makes its operative form the act that externalizes multiple recurring cycles as aligned lanes and phases on one shared timeline; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Rendering recurring phases, windows, and dependencies for multiple actors is organizational calendar and coordination design.
Related originating lineages:
- Agricultural Science & Agronomy — Seasonal calendars coordinate planting, labor, weather, and biological cycles.
- Futurism & Strategic Foresight — Temporal maps expose future windows and interdependencies across cycles.
- Religious Studies & Theology — Liturgical calendars provide an old institutional form of shared recurring time.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a calendar or visual artifact that shows recurring cycles, phases, usable windows, and dependency points across actors.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined record shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance, and encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The Shared Cycle Calendar is deliberately an input, not an intervention — it is the one mechanism here that changes no timing at all. That is why several siblings list it under Consumes: it is the substrate they read before they act. Keeping it purely representational is what lets it stay a neutral, trusted map rather than becoming one team's schedule imposed on the rest.
[n1] An "information radiator" (Alistair Cockburn's term) is a highly visible, low-effort display that broadcasts current status to anyone passing, so coordination happens by shared sight rather than by asking — exactly the role a shared cycle calendar plays. ↩