A firm's architecture does not maintain itself. The Weekly Commissioning Audit is the minimum viable governance cadence — the instrument that keeps an installed system from drifting back into disorder.
Once a firm has installed its architecture — documented workflows, decision lanes, a named system of record — the founder's operational role changes. Execution is no longer the primary function. Governance is.
Governance is not performance management. It is not a status check or a team meeting. It is the recurring act of verifying that the systems installed to govern the firm are still functioning as designed — and intervening precisely when they are not.
Without a governance cadence, structural drift is not a risk. It is a schedule. Every system installed without a maintenance rhythm begins degrading the week after it launches.
The Weekly Commissioning Audit is the primary governance instrument of the INTJ operating model. It is a 30-minute structured review conducted by the Operations Lead — or by the founder in early-stage firms — each week, without exception. Its purpose is system maintenance. It surfaces the structural problems that compounding latency and Tool Rot create before they become expensive to fix.
The audit is anchored by five questions. Each targets a specific structural failure mode. They are not conversation starters — they are diagnostic instruments. Each question has a correct answer and an intervention if the answer is wrong.
Which decisions were escalated to the founder this week — and were they above the defined threshold?
Escalation that did not breach a documented threshold is not caution. It is structural failure: undefined authority, missing rules, or insufficient system trust. Every unnecessary escalation is evidence of a gap in the Decision Rights Matrix — and must be treated as such, not accommodated.
If escalation occurred below threshold → update the relevant Decision Lane scope or threshold to close the gapDid any team member ask a question this week that should have been answered by a documented SOP?
A question that the SOP should have answered is a Ghost Workflow signal — either the SOP does not exist, or it exists and is not being used. Both conditions require intervention. The Ghost Workflow is a process held in memory rather than the system, and it compounds directly into delegation failure and founder dependency.
If yes → either create the missing SOP or identify why the existing one was not consulted and correct the gapIs the System of Record current? Are tasks being tracked in the designated tool — or are workarounds appearing in email and chat?
Workarounds appearing outside the designated system are shadow systems — the first observable symptom of Tool Rot. Caught at this stage, the intervention is simple: reinforce the adoption standard and address the friction causing the bypass. Left unaddressed, the shadow system displaces the governed system within weeks.
If workarounds are present → identify the friction causing the bypass; address it in the system, not around itDid any task or deliverable fall through the gap between roles this week — and is there a named owner for every active commitment?
Unowned work does not stay unowned — it defaults to whoever cares most, which is usually the founder. Ownership gaps are not personnel failures. They are architecture failures: the Decision Lane did not specify the handoff clearly, or a new category of work emerged without being assigned. Both are structural, not behavioral.
If gaps are present → assign ownership by role immediately; update the relevant Decision Lane to prevent recurrenceWhere did the team experience unnecessary delay or confusion — and does the delay indicate a missing rule, threshold, or workflow?
Friction is structural information. It is the system's way of reporting a missing rule. When a team member was delayed this week, the cause is almost always architectural: no documented standard for this situation, no defined escalation path, no named resolution node. Friction that is observed but not diagnosed becomes recurring friction — the same delay next week, at compounding cost.
For each friction point → identify the missing structural element and install it before the next audit cycleThe audit is not a meeting. It does not require the full team. It is a structured 30-minute review conducted by the Operations Lead working from a fixed template. The output is not a report — it is a short list of structural interventions to execute before the following week.
The output of every audit is a short intervention list — typically two to four items — that close the structural gaps surfaced that week. The audit is only useful if the interventions are executed. An audit that produces observations without action is not governance. It is documentation of decline.
The Weekly Commissioning Audit maintains the system week to week. Once per month, a deeper review is required — one that examines not the work output, but the governance infrastructure that governs it. This is the Monthly Structural Review: a 60-minute session between the founder and the Operations Lead.
| Domain | What It Examines | Diagnostic Standard |
|---|---|---|
| Decision Lane Compliance | Pull the 30-day escalation log. Calculate the percentage of escalations that were above threshold. | Valid escalation rate below 70% indicates threshold miscalibration or team training gaps — recalibrate the relevant lanes. |
| SOP Drift Assessment | Review the five most-used SOPs. Do they describe the actual process being executed today? | SOPs that describe processes no longer in use must be updated or retired — outdated SOPs are worse than no SOPs. |
| Ownership Audit | Review current role assignments and Decision Lane ownership. Have any roles changed or new functions emerged without documented ownership? | Every function without a named owner is generating escalation pressure — assign before it routes to the founder. |
| Tool Governance Review | Is the System of Record actively maintained? Are shadow systems emerging — side spreadsheets, personal task lists, undocumented channels? | Any shadow system present is a Tool Rot signal at the Drift stage — intervene now, not at Decay. |
The Weekly Audit catches operational drift. The Monthly Review catches architectural drift — the slower degradation of the system design itself as the firm grows and changes. Both cadences are required. Neither substitutes for the other.
The most common failure mode in governance is selective execution — running the audit when things are calm and skipping it when things are busy. This inverts the value. The audit is most important precisely when the firm is under load, because load is when structural gaps surface fastest and compound most expensively.
A busy week is not a reason to skip the audit. It is evidence that the audit is overdue. The firm that skips governance during high-load periods is the firm that discovers, three months later, that it has re-accumulated the same structural debt it spent the previous quarter eliminating.
| Failure Pattern | What It Produces |
|---|---|
| Audit skipped during busy periods | Structural gaps accumulate precisely when the firm is least able to absorb them; problems surface as crises rather than early signals. |
| Audit run but interventions not executed | Documentation of decline; same problems recur weekly; team loses confidence that anything will change. |
| Audit delegated without a trained owner | Surface-level review; structural gaps missed; founder remains the de facto governance authority. |
| Audit converted into a status meeting | Performance discussed instead of systems examined; root causes unaddressed; governance function lost. |
| Monthly review skipped for 60+ days | SOP drift goes undetected; Decision Lanes become stale; tool governance lapses; architecture degrades to pre-installation condition. |
The Weekly Commissioning Audit is the difference between a firm that installed architecture and a firm that operates on it. Installation without governance produces a system that degrades. Governance without installation produces a meeting with no system to maintain. Both are required. Neither is sufficient alone.
The governance cadence in practice:
The Reality Check measures Execution Reliability as a scored OSI category — including whether your firm's systems hold under load or require constant founder intervention to maintain.
Most owners avoid this moment. The Reality Check identifies your operational leaks, calculates your OSI score, and — if there is a fit — opens the path to the Architecture Blueprint.