Ops Tactical

Most operational decisions don't get made. They get won.

Someone posts a Slack message. Three people respond quickly. The thread goes quiet. The first response with a link becomes the policy. Two people with relevant context who didn't check Slack until 4pm inherit a decision they never influenced.

This is how your organization makes choices every day: by whoever typed first, whoever spoke loudest in the standup, whoever was already in the channel. Not by whoever had the best information.

What a structured debate looks like

Ops Tactical is the simplest Council ceremony: four agents, four rounds, one operational question. No setup. No roster file. One command.

basal arena ceremony --protocol ops-tactical --topic "Should we delay the launch by two weeks?"

BASAL assembles four agents with distinct orientations: one prioritizing risk and stability, one prioritizing velocity and commitment, one representing customer-facing impact, one synthesizing the evidence. They don't take turns agreeing. They are explicitly seeded with different priors.

Round one: each agent states its position with evidence cited. Not "I think we should delay" but "the load testing report from March 8th showed 12% error rate at 2x expected traffic, and launch is at 3x."

Round two: cross-examination. Each agent challenges one other's evidence or inference. If the stability agent says "delay," the velocity agent asks which specific deliverable justifies the delay and whether a partial rollout addresses the risk without the cost.

Round three: position update. Agents either hold their position with sharpened reasoning or revise it and say why. The revision is noted. If an agent changed its mind, the record shows what argument moved it.

Round four: synthesis. The majority view, the minority view, and the specific action items that follow from the decision.

What you get in 5 minutes

The full debate runs in under 5 minutes and produces a structured output:

• The decision reached, with the vote count and confidence scores
• The minority position, preserved in full, with the evidence it cited
• Three to five action items with owners and deadlines extracted
• The single most critical assumption the decision depends on

That last item is the one most teams never write down. Ops Tactical forces it to the surface: "This recommendation assumes the API partner can deliver the authentication endpoint by March 22nd. If that slips, reassess."

Where it fits

Ops Tactical is not a replacement for judgment. It is a structure that makes judgment legible. When the decision is wrong, you can see exactly which assumption failed and who made it. When the decision is right, the reasoning is archived.

Teams that run it consistently report fewer "wait, I thought we decided..." conversations. Not because everyone remembers better — because the record exists and anyone can read it.

The loud voice in the Slack thread still exists. It just no longer decides alone.