Different Hunger

Execution OS

0 Hour OS

The 0 Hour Execution OS — one denominator, two matrices, one loop. Generated from canon.

0 HOUR — The Operating System for Reality

One denominator. Two matrices. One loop.

The denominator

Return on Time (RoT) — $/hr

Return on Time = net_profit ÷ (operating timer minutes ÷ 60)

Time is the unit of measurement. The north-star is your Return on Time = income ÷ time.

Everything is denominated in time — a brand, a person, a single task. It is an accounting identity, not a mindset, which is why it can be enforced in code.

The laws

  • Let It Flow
  • Always On
  • 99.9% Async
  • D1 Profitable

99.9% Async is the operative one: no step may require two people present at the same time. That single law is what removes approval bottlenecks.

The CEO's job

JobPermanent
VisionYes — never delegable
PrioritiesYes — never delegable
PeopleYes — never delegable
TrainingNo — decays to zero

QA is not on this list; it belongs to the COO. QA fixes one artifact — training fixes every future artifact. Training is the work of moving things down the Time Freedom Matrix, so it shrinks as trust rises. The job is designed to end.

The two agents

They are the two halves of Return on Time.

Zero · COO

The machine — execution, triage, ops, finance, the belt, QA. Life AND business.

Owns the denominator: time.

Zera · Chief Client Officer

The market — the client relationship end to end.

Owns the numerator: value.

Mandate, in order: RETENTIONACQUISITIONLEAD GENERATIONDISTRIBUTION

Retention feeds referrals, which feed distribution — client success is upstream of acquisition in a flywheel, even though it looks downstream in a funnel.

Creative authorship belongs to neither. It is the owner's zone of genius, and the standing rule is that AI never creates copy — only reuses his.

Matrix 1 — Time Freedom

Filters the item: who or what should do this? Sequential; exits at the first match.

StepQuestionCriterion
1DELETEIs this truly essential?A2O — aligned to the 90-day objectives
2AUTOMATECan technology do this?in the Proven Library and machine-doable
3DELEGATECan someone else do this?in the Proven Library and a roster owner exists
4HYPERFOCUSIs this worthy of my time?above THR and inside the Zone of Genius

A2O, THR and ZOG are not separate flags — they are the criteria that answer each question.

Matrix 2 — Solution

Filters the approach: how do we solve it? Ranked descending, applied before score.

RankStepQuestion
4MORECan we do more of what already works?
3BETTERCan we do it better?
2NEWDo we need to create a new solution?
1CONSOLIDATEShould this merge into something else, or die?

NEW is the highest cost, the lowest certainty, and therefore the lowest priority.

Scoring

score = (Value × Certainty) ÷ Effort

Effort is stored in minutes. Hours are a view for multi-day horizons, never the stored unit. A missing input scores null, never 0 — a missing estimate is not a worthless task.

Value ladder: $100,000 · $10,000 · $1,000 · $100 · $10 · $1

Certainty ladder:

%Meaning
20Rookie — haven't done before
50Beginner — done a few times
80Expert — done dozens of times
100Master — done hundreds of times

Anything inside the Zone of Genius scores 100 by rule.

Roles, rates and budget

Budget is derived, never negotiated: budget = rate × effort.

RolePaid forRateMatrix step
AIINPUTS$1/hour · $0.01/wordAUTOMATE
VAINPUTS$5/hour · $0.06/wordDELEGATE
PMSYSTEMS$20/hourDELEGATE
Outcome rolesOUTPUTSDELEGATE
CXO / CEOOUTPUTS$100/hourHYPERFOCUS

What you buy decides how much supervision the role needs. Pay for inputs and you must supervise. Pay for outputs and the incentive supervises. That is the mechanism behind 0-hour management.

Pre-approval

A standing decision that removes a class of work from the CEO's queue.

TierRoleStanding authority
T0AIProven Library only. Never asks.
T1VAProven Library only, under cap.
T2PMWeekly ceiling, itemized after the fact.
T3OUTCOMESelf-approving — paid only on the result.
T4CXONever pre-approved. This is the definition of the CEO's time.

Caps are not static — they are a function of demonstrated trust, per role, per task class. Trust starts at zero, so early on everything reaches the human: the approval queue is the training loop, and it dissolves itself as trust is earned.

trust (executor reliability) is not certainty (confidence in the value estimate). Two different numbers; never merge them.

Never pre-approvable, at any trust level

  • money out
  • client or POC contact
  • publishing under the owner's name
  • anything irreversible

Trust curve

Not ratified. This is a proposal awaiting mk's ruling. Nothing in the system enforces it.

  • Starts at: zero — every new entity sends everything to the human
  • Advance: 5 clean approvals advances a tier
  • Drop: one rejection drops a full tier (asymmetric on purpose)
  • Ceiling: T2 — nothing ever reaches unlimited

Demotion — why execution cannot stop

Not ratified. This is a proposal awaiting mk's ruling. Nothing in the system enforces it.

Silence demotes, it never halts:

HYPERFOCUS  →  DELEGATE  →  AUTOMATE  →  BACKLOG

Terminal state is BACKLOG — logged, owned, never silently dropped. Irreversible work degrades to its reversible half — draft the email, build the ad paused, generate the doc unpublished.

Configuration cadence

A rate cannot be assigned blindly; it is unique to the person and their current stage. Set at onboarding, changed only here.

WhatWhen
VISION BOARDa few times per year
NINETY DAY PLANquarterly — objectives, THR, targets, caps
OTHERWISEstable in between

Every setting is per-entity. There is no global default — the owner is entity #1, not a hardcoded constant.

The week

PhaseDaysSteps
PRIORITIZEFRI–SUNAuto-triage · Report · Priority vote · Assign + plan
EXECUTEMON–THURitual · Assigned work · Clear inbox · EOD reflection
OPTIMIZEWEEKLYReview · Update docs · Publish changelog

The loop

SCAN — the machine

  1. OUTPUTS — Results. Peace Protocol (life) · Brand Flywheel (brand).
  2. SYSTEMS — The machines producing them. Brand: the stack. Life: the schedule and rituals.
  3. INPUTS — What goes in. Brand: spend, outreach, content. Life: fuel, reps, hours.

PLAN — the human

  1. DIAGNOSIS — Names the ONE constraint, and why. Produces the bottleneck.
  2. PRESCRIPTION — How we solve it. Solution Matrix, then score. Produces the ranked approach.
  3. SPRINT — Who, by when, for how much. Time Freedom Matrix + rates + capacity.

PLAY — moves the machine

  1. CUE — The trigger fires — dispatch, schedule, ritual, or event. Time-based AND event-based.
  2. ACTION — Commit and execute. Evidence produced, real minutes logged.
  3. REWARD — Verify, pay, bank the proven play, raise trust.

REWARD is contingent on verified output. Never on effort, never on hours.

The three axes

AxisWhat it answers
The loopwhat happens — the nine steps above
The cadencewhen — daily: PLAY — the reps · start and end of day · weekly: SCAN + PLAN · plan Fri–Sun, play Mon–Thu · quarterly: config — objectives, THR, targets, caps · yearly: the vision board
The levelshow deep — BELIEFS → HABITS → IDENTITY (published at /way)

Dimensions

The same four planes describe a life and a brand.

PlaneLifeBrand
MENTALMINDDISTRIBUTION
PHYSICALBODYLEAD GENERATION
FINANCIALINCOMEACQUISITION
EMOTIONALLOVERETENTION

Time is the outcome that sits on top of all four — measured, not scored.