Kairos — Standard of Performance (2026-08-14)

Lee's own framing, voiced in his free-write on the Kairos week, 2026-08-14. Recorded here because it is the successor to the business-health page and the shape the second half of the engagement takes. Not yet built — this is the mechanism, not a report on one.

What it replaces

The first version of this shipped in the War Room as business health — "Where the subscription machine breaks." Lee's verdict on it: a very lame initial version, not representative of the potential it has if executed properly. He pulled its URL off the War Room's front door for exactly that reason, and it is confirmed unlinked from mnwar/index.html. The page still exists; it is simply not on a door until it earns the place.

The rename is not cosmetic. Business health describes a state you observe. Standard of performance describes a bar you measure against and then close on. The second is actionable; the first is a dashboard.

The mechanism

Three steps, then repeat.

1. Map and log every vital operation precisely. Each operation that MN's business actually runs on gets mapped and instrumented. Lee's read is that the tooling for this already exists across the stack — what is missing is implementation, not capability.

2. Assemble the gold standard for that specific operation. For each mapped operation, gather as granular an insider-knowledge database as can be built on what a genuinely world-class version of that operation looks like in the real world. Not a generic best-practice list — the specific, in-depth account of how the best actually run it.

3. Measure current against gold, take one fruit, ratchet it. Set the current operation against the standard, identify the single lowest-hanging 80/20 gap, and close it once and for all. Then move to the next one.

The critical constraint sits inside step 3: what gets implemented is not a single action item. It is a tiny, high-quality habit — or machine automation wherever automation is possible — that does not revert. An improvement that decays is not an improvement; it is a project. The ratchet is the whole point.

Why it holds

It inherits the discipline the engagement already runs on. The evidence ranking on /opportunities/ answers how good is this claim — level of evidence, graded separately for quality, never averaged. The standard of performance answers the sibling question: how good is this operation, against what. Both refuse the same failure — an unmeasured judgement wearing a conclusion's clothes.

It also inverts the usual consulting output. A findings report tells a company what is wrong. A ratchet leaves behind a habit that keeps being right after the engagement ends.

What it needs before it can start

Step 1 is gated on the same unlock as everything else this week: read-only data grants — ClickUp, Drive, Slack and Intercom among them (/data-unlock/, the full data-access board sent 2026-08-14, which retired the narrower four-grant ask to Šaras of 08-13 and carries the 21 August date). Operations cannot be mapped and logged precisely from the warehouse alone; the warehouse records what happened, and those sources carry why. Lee names this the biggest blocker and the biggest possible unlock in the same breath.

Open

Which operations count as vital — the list has not been drawn, and drawing it is the first real act of step 1.
Where the gold-standard database lives, and whether it is a War Room room of its own.
Whether this becomes the page that returns to the War Room front door, or something wider than a page.