Most weekly meetings fail for the same reason: they have no mechanism to force a decision. Someone raises a problem. The group nods. The meeting ends. Nobody knows who owns it or when it will be resolved. The problem shows up again next week.

The Line is built to prevent this. It is not a check-in. It is not a brainstorm. It is a 90-minute decision session with a fixed agenda, an AI-generated brief, and a hard rule: nothing leaves unresolved.

The structure: 30 + 60

The meeting has two halves. The first 30 minutes covers five short segments — Open, Dispatch, Signal, Bearings, and Close. The final 60 minutes is Issues Work: focused, structured problem-solving with no time wasted on updates or recaps. The ratio is locked. It does not change.

The agenda

CenterlineOS generates the agenda automatically before every meeting. You arrive with the brief already written.

01 — Open · 5 minutes

One personal highlight and one professional highlight from each person. Brief. Sets human tone before the work starts. The best Line meetings happen when people show up as people, not roles.

02 — Dispatch · 5 minutes

Company news, wins, and problems the room needs to know — broadcast only, no discussion. Good news moves fast. Bad news needs to move faster. Dispatch enforces the rule that bad news doesn't hide. If something needs to be worked, it goes on the issues list.

03 — Signal · 5 minutes

Each metric gets one call: Go or No-Go. Go means move on. No-Go goes straight to the issues list. No discussion. The Signal is not a conversation — it's a dashboard read. Flag and move.

04 — Bearings · 10 minutes

Each Bearing owner: brief progress update, Go or No-Go, blockers. No-Go or blocked goes on the issues list. Not discussed here. Same rule as Signal: flag and move.

05 — Issues Work · 60 minutes

This is the meeting. Everything surfaced from Signal and Bearings, plus anything already on the standing list, gets worked. Time-box each issue at 10—12 minutes. That's 5—6 issues fully resolved per session. Every issue runs the Root Protocol.

06 — Close · 5 minutes

Read back every decision made. Confirm every owner. Confirm every date. No one leaves unclear on anything. New issues go on the list for next week. The meeting ends.

The Root Protocol

Every issue in The Line runs through five steps. The goal is not to discuss the issue. The goal is to find The Root — the real cause underneath the symptom — and leave with steps so clear it's almost annoying.

Step 1 — State it

Read the issue as written. Everyone confirms they're aligned on what it says before anything else is said.

Step 2 — Find the Root

Ask why until you hit something real and actionable. The first answer is almost never The Root. "Sales are down" is a symptom. "We stopped following up after the first demo three months ago" is The Root.

Step 3 — Build the Solve

A real decision. Not "look into it." If the group can't state the solve in one sentence, they haven't decided yet.

Step 4 — Assign it

Owner. Steps. Dates. Written into the issue before the group moves on. If it isn't written down before moving on, it doesn't exist.

Step 5 — Say it Back

Someone who is not the owner states back: The Root, the solve, who owns what, and by when. If they can't do it clearly, the group isn't done. This is the clarity enforcement mechanism. It should feel almost annoyingly thorough. That's the point.

Why the fixed structure matters

Variable meeting structures create variable outcomes. When people don't know what's coming, they come unprepared. The fixed agenda means everyone knows what they're walking into. The AI-generated brief means the prep is already done. You show up and work.

Run The Line the same way every week and it compounds. Let it drift and it becomes another meeting nobody looks forward to.