When a problem resists structure, teams give it a cadence.
A rollout is going sideways. Three teams need to coordinate. A decision needs input from several people. Someone creates a weekly meeting for Tuesday at 10:00, blocks 45 minutes, and writes a sensible agenda. At that moment, the meeting is useful. It gives the problem a place to go.
Two sprints later, the rollout is done. The coordination problem is solved. The decision has been made. The calendar event remains. Nobody remembers who owns the invite, and the person who created it may have moved to another team. The meeting continues because cancellation feels more disruptive than attendance.
Summon Recurring Meeting is the spell that turns a temporary response into permanent infrastructure. The meeting outlives the problem that justified it and runs on institutional momentum. Try to cancel it and someone reaches for a defense: "It's not about the content, it's about the connection." That may sound reasonable, but connection is not the same as a decision, a resolved issue, or a piece of work that moved forward.
A meeting can produce the feeling of coordination while producing very little coordination. People exchange updates. The same risks appear on the agenda. Someone promises to follow up. The notes are filed. At the end of the hour, everyone has attended an event about the work, and the work is still waiting.
AI makes the spell easier to cast. New meetings appear for model governance, responsible AI review, and weekly alignment on the AI roadmap. Each begins with a legitimate question. The problem is not that those questions are unimportant. It is that the meeting often survives after the question changes or disappears.
The generated summary adds another layer of protection. An AI tool produces a tidy recap and files it in a wiki nobody reads. The document becomes an artifact. The artifact becomes evidence that the meeting is producing value. A Cleric can point to the archive and say the process is working, even when no decision has emerged and no owner has changed what they are doing.
A summary is not proof that a meeting was necessary. It only proves that words were spoken and recorded. If the same update could have been written in a channel, added to a project document, or sent to the people who needed it, the recurring appointment may be serving the calendar more than the team.
The spell stacks quickly. A team can have Monday planning, a Wednesday sync, a Friday retrospective, and a daily standup. Then an AI-generated daily status report arrives alongside the standup, duplicating the same information in a different format. Focused work now happens in the gaps between recurring events. Declining a meeting looks like disengagement, so people protect their reputation by attending and push the actual work into evenings or weekends.
That creates the next problem. Less working time means more coordination trouble. Coordination trouble becomes the reason to add another meeting. The calendar fills up, and the team mistakes calendar density for collaboration. The meeting is now part of the problem it was created to solve.
The question that breaks the spell is blunt: "What would happen if we just stopped doing this?" Often, the answer is uncomfortable because it is so small. The work would continue. People would ask for help when they needed it. A real decision would happen in the channel or document where the decision belonged. The connection the meeting was preserving had already been an illusion for months.
A recurring meeting needs an expiration date when it is created. Put the kill date in the invite, along with the problem the meeting is supposed to solve and the decision rights of the people attending. When the date arrives, the meeting ends unless someone explicitly renews it.
Renewal should require evidence: a live problem, a useful agenda, and a reason this group needs synchronous time. If the meeting has become a status recital, replace it with an update. If the decision has already been made, end it. If nobody can say what the meeting is for, do not schedule another occurrence while they search for an answer.
The default should be death, not another year of calendar noise.