Operating Framework · 2026

The Three-Mode System

Operations executes. Management triages and leads. Executive commissions and dissolves.
Modes coexist — what shifts is the dominant weight. The list must die.

Friday 21 March 2026  ·  Q1 closing  ·  Q2 begins 1 April
The Batching Protocol — Dominant Weight by Cadence
WeekdaysMon – Fri
75% Operations
15% Triage
10%
Ops dominant. Triage enters when a live flag demands it. Fix, classify, return.
WeekendSat – Sun
75% Flag Processing
15% Ops
10%
Process the week's flags. All domains batched together. Weekend output = Monday input.
Month-endLast weekend
75% Executive
15% Mgmt
10%
Did we hit the target? Adjust mandates. Queue anything new for parliament.
Quarter-endParliament
75% Executive — Parliament
15%
10%
All ministries report. Commission new. Dissolve inactive. Set next quarter's direction.
The Three Modes — click to expand
Operational
75%
Weekdays · The constant
The river that never stops. Execute. Flag in motion. Classify fast. Keep moving.
Managerial
75%
Weekends · Triage & lead
Process the week's flags. Stand in front of what happened. Make fast proclamations. Weekend output becomes Monday's ops input.
Executive
75%
Month-end / Quarter-end
Two binary questions. Did we hit the target? Do we commission anything new? Month-end is light. Quarter parliament is full.
Q2 2026
Apr 1 – Jun 30
Quarter Parliament
Jun 27–28
Commission · Dissolve · Set Q3 direction
AprilStandard
▼
Month-end Convention
Last weekend of April
Light executive — close arc, adjust mandates
~1–2hrs
MayStandard
▼
Month-end Convention
Last weekend of May
Light executive — close arc, adjust mandates
~1–2hrs
JuneQuarter Close
▼
Quarter Parliament · Jun 27–28
Full executive session — all ministries report
Commission new · Dissolve inactive · Set Q3 direction
Half day
Flag Taxonomy — what you are classifying and why it matters
Core · Really Bad
Strategy failure
Everything is being executed correctly but results are not coming. The problem is not your competence — it is the approach itself. Continuing without addressing this compounds the damage.
Response Stop. Address immediately. Accept the energy cost — the cost of continuing is higher. This is a parliament-level flag. Scrapping the approach, not tweaking it. Rare but expensive to ignore.
Rational · Bad
Execution shortfall
The strategy is right, the goal is right, but your current competence has not met the standard the executive set. You still suck at this specific thing. Growth lives here.
Response Capture it. Name it precisely. Defer to weekend batch. At the weekend: what specifically changes in how I execute this next week? Most flags live here. Address them consistently and they clear.
Circumstantial · Inconvenience
External obstacle
Something was in the way. Not your execution, not your strategy. Environment, energy, access, disturbance. These are not failures — they are conditions. Do not misattribute them upward.
Response Note it. Understand what the circumstance was. If it is recurring, it becomes a rational flag — a pattern you need to design around. If isolated, let it go. Do not manufacture meaning from noise.
The List Must Die — what healthy looks like
Danger state
Core flags accumulating. Strategy is broken and not being addressed. Everything else is noise until this is resolved.
Working state
Rational flags dominate. You are building competence. Flags are appearing faster than they clear — normal early in a domain. Keep processing.
Optimisation state
Mostly circumstantial flags. Rational flags clearing faster than they appear. This is when new capacity genuinely exists. Only now does the executive commission something new.
Binary Question Stack — one question per cadence
Operational · Weekdays
No questions. Just doing. Flags surface as signals — not interruptions.
  • —Execute the process
  • —Flag if something surfaces
  • —Classify: core / rational / circumstantial
  • —Return to ops
Managerial · Weekend
Process the flags. Stand in front of what happened. Proclamations, not analysis.
  • 1Did we achieve the weekly goal?
  • 2For each flag — what changes on Monday?
  • 3Do we queue anything new for the pipeline?
Executive · Convention
Month-end light. Quarter parliament full. Both use the same questions.
  • 1Did we hit the target?
  • 2Does any mandate need adjusting or dissolving?
  • 3Do we commission anything new?
Live Flag List — capture in motion, process at the weekend
0
Core
0
Rational
0
Circumstantial
0
Resolved
No flags yet. Capture them as they surface during operations.
The Batching Rules
→Modes coexist. What shifts is the dominant weight, not exclusivity.
→Triage entering ops mid-week is responsive, not a violation — classify the flag, fix if core, return to ops weight.
→Weekend flag processing covers all active domains together. Never split reviews by domain mid-week.
→The weeks must earn the month-end convention. Vigorous ops early makes the close meaningful.
→No new ministry is commissioned mid-week on impulse. New rivers open at conventions only.
→New capacity is proven by a dying flag list, not by a picture in your head.
→Most flags are rational. Rational flags are solvable. Address them consistently and they clear.
→Do not misattribute circumstantial flags upward. A bad environment is not a bad strategy.
→The system exists. The work is to use it. A new system is not a solution.
Process Stack
Operational
Execution
The constant. Always present. Absorbs responsive triage when live flags demand it. Returns to ops weight after.
Managerial
Flag Processing & Lead
Weekend output becomes Monday input. Processes flags, adjusts direction, queues new things for pipeline. Not reviewing — triaging.
Executive
Commission & Dissolve
Decides the architecture. Opens new rivers. Commissions ministries. Dissolves inactive ones. Does not operate, does not manage.
Q1 Parliament · Mar 28–29 · Then Q2 Operations Begin