Jacket Meeting — Skill | Infinite Game OS

Definition

The Jacket Meeting is the team-meeting form of your advisory lenses, the all-hands to the Jacket Session 1:1. Every jacket you have defined comes to one room and works a twelve-step flow from convene to close. The mechanism at its heart is preparation in isolation. Before the lenses meet, each one develops its perspective alone, from one shared set of facts, so what arrives at the table is genuinely separate rather than five readings already blurred into one. You chair. One seat holds synthesis, naming alignments, tensions and trade-offs in the room own language without flattening real disagreement into bland compromise. A dissenting lens can record a minority report that travels into the meeting note without blocking the decision. Options arrive tagged do-now or plan-for-later, you decide and restate the decision in your own words, and the meeting closes as a record, not a work session. The building happens later, in scoped sessions.

Perspective prepared in isolation

Before the meeting, each lens prepares its own read independently, working from one shared set of agreed facts. A lens developed alone keeps its perspective uncontaminated.

The value of the meeting is proportional to how genuinely separate the perspectives were before they met. Five views blurred into one in a single head is the thing this design exists to prevent.

Synthesis without deciding

One seat holds synthesis. It names what the room actually said, preserves visible dissent, and tags what is still contested. It integrates. It does not decide.

You chair and you decide. Restating the decision in your own words, including where you diverged from the synthesis, is the guard against the synthesizer becoming a shadow decider.

Two routes out

Options arrive in two lanes. Do-now items are light enough to handle as the meeting closes. Plan-for-later items are filed for a fresh, scoped session.

A connectivity check runs before any build is filed: confirm it does not duplicate something already designed or running. The meeting is a decision room, not a build session.

Use Cases

A standing review across every lens

You convene all your jackets on a regular rhythm to look at the business together. Each brings its own most-pressing read, and the synthesis surfaces the cross-lens pattern no single seat could see.

A wide decision with many stakes

A move touches marketing, finance, operations and community at once. The meeting holds all four perspectives as genuinely distinct inputs, then narrows to options you can actually choose between.

Catching the blind spot

The structured cross-lens conversation, round-robin before open debate, keeps the loudest voice from anchoring the room and lets a quiet lens surface the thing everyone else missed.

FAQ

How is this different from the Jacket Session?

The Jacket Session is a 1:1 with one lens, or two at once. The Jacket Meeting brings every lens you have defined into one room at the same time. Most people run sessions first and grow into the meeting.

Why prepare each lens separately?

When one mind considers several angles at once, the angles average toward each other and blur. Preparing each lens in isolation keeps the perspectives genuinely distinct, which is the only way the synthesis at the end has anything real to harmonize.

What is a minority report?

A principled disagreement a lens carries into the written record without blocking the decision. It preserves the dissent so a choice made over real objection stays honest and traceable.

Does the meeting solve the problems it surfaces?

No. The meeting is a decision room. It names the work and routes it: small things handled as it closes, larger things filed for a scoped session. Solutioning in the meeting turns it into a stalled work session.