Frame it. Vote. Record. Move.

When to use the advanced protocol

The simple protocol handles one decision with one triad. The advanced protocol handles decisions that depend on other decisions, or that need more than three people.

Use the advanced protocol when a decision spawns sub-decisions, when different triads need to coordinate, or when a decision is revisited after the outcome arrives.

The principle

Frame it. Vote. Record. Move.

The dependency graph

Each decision is a node. Edges record dependency: premise, constraint, or delegation. The structure is a directed acyclic graph.

A triad ruling on a large question spawns the sub-decisions it owns, each routed to its own triad, in parallel. A triad blocked for want of an input spawns the blocking question and routes it laterally to whoever owns it, rather than escalating to a less-informed authority.

Any decision spawning children should retain a closing decision reviewing the whole.

Revisit alerts

When a parent decision is re-decided, all descendants are flagged for review.

Revisiting becomes a graph query: each decision records what it rested on, and when a parent is re-decided, descendants are flagged. Circular dependencies become detectable, and can be broken by identifying which decision must be made on a stated assumption.

Delegated triads

Where triad C's decision depends on rulings by triads A and B, C is bound by them.

This is premise-based aggregation distributed across groups. C may therefore be pushed toward a conclusion its own members would independently reach. The resolution is that a bound triad may formally reopen a prior decision rather than override it: prior rulings can be ignored, but can be sent back to their owners.

The amendment window

The amendment window stays open after the meeting.

Each member of the triad can change their mind on something they said during the meeting. They must say what they would change about their own position and why. A reasoned case.

The closure period is determined by the Group. In many cases it may be a matter of minutes after the meeting. After that, the window closes and the decision stands — unless an outcome proves it wrong.

The amendment window does double duty. It is the earliest sensor (see it) and the most direct path to reversing a decision (correct it). The same mechanism that names the error is the mechanism that corrects it.

Two amendment modes

Correction mode and reconsideration mode.

Correction mode: we approved something that should have been rejected.

Reconsideration mode: we blocked something that should have been approved, and here's why we think so now. The second is the harder one, because it requires someone to say "the group got it wrong by excluding me." It needs protection — procedural weight, not just a button.

Error-type tagging

When the outcome contradicts the expectation, the record tags the error.

False acceptance: we approved something that failed.

False rejection: we blocked something that would have succeeded.

These are opposite failures, and correcting them requires different actions. False acceptance is a cost paid. False rejection is a cost missed.

Known vulnerability: salami-slicing

Decomposition permits splitting a decision until each part is individually approvable.

The safeguard is that any decision spawning children should retain a closing decision reviewing the whole.

Get started

Three people. Paper and pen. A decision to make.

That's it. You need software. You need a rollout. You need one decision that matters and three people who can decide it.