A Personal Operating System

PrimalOS

A serious operating system for running your life and your business. One owner. Plain-text files. An assistant that reads the rules every morning and holds to them.

No app to log into. No dashboard to maintain. Just a folder of markdown files and a set of rules any AI assistant can follow.

What PrimalOS is

A brain for a one-person business,
written in plain text

PrimalOS is a folder of markdown files plus one rulebook. The rulebook tells an AI assistant how to run your day: what to read, what to write, what to protect, and what to push you on. Because it is all plain text in a git repo, it is portable, versioned, and belongs to you — not to any single app or vendor.

01
One rulebook
A single file holds the goals, guardrails, and checklists. The assistant reads it at the start of every session — no re-explaining, no prompt engineering each morning.
02
File-based memory
Every fact has exactly one home. A task lives on the board, a metric in one table cell, a mood in the mood log. Nothing is stated twice, so nothing drifts.
03
Built for a real brain
Designed around ADHD and executive dysfunction. Revenue gets named first. Low-energy days are legal. Forgotten wins get resurfaced. Work with the brain, not against it.
The whole system
One picture

The entire operating system,
on one page

Owner and assistant at the top. Every fact flows into its one file-home. The daily loop runs briefing to close. Nothing gets built without passing the gate — and the guardrails stay on the whole time.

PrimalOS The file-based operating system - owner + AI assistant, file-memory, the daily loop, the gates. COLOUR LEGEND People + entry hook Core OS file (Playbook) File homes (memory) Automation (6am agent) Daily loop Build gate Guardrails Owner keeps the wheel - final go on anything irreversible AI Assistant reads the OS, drives the daily loop CLAUDE.md thin harness hook -> points to the OS Playbook.md the portable OS SOURCE OF TRUTH read every session 6am Cloud Agent runs while you sleep mechanical reconcile - flag, not fix Daily Brief.md tidied / needs-you / flags + resurface line FILE HOMES - one home per fact, write on event Board.md task status - Kanban BusinessHealth.md revenue truth tables Context.md project state + Next: Assets.md owned IP inventory Memory/ assistant lessons Done.md completion log Mood.md mood log Happiness.md life side + friends Mistakes.md errors + fixes PrimalOS.md the WHY / rationale THE DAILY LOOP MVB Briefing reads Daily Brief, names revenue task Work write-on-event to file homes Session Close light - commit + push 6am Agent reconciles overnight BUILD GATE - PRD before any build · nothing irreversible without owner's go 1 Blind-spot 2 Sketch 3 Grill 4 PRD 5 Build + notes Audit loop x3 6 Quiz -> ship GUARDRAILS - always-on: survival-first, money + life REVENUE SIDE the one bet - daily revenue action pipeline floor = 5 warm leads DECISION CHALLENGE survival-first / revenue-first · thinking razors shiny-object guard: park, don't chase LIFE SIDE happiness signal call 3 friends / week repeat
The core idea
You run it. It keeps you honest.

You make the calls.
The system is your discipline layer.

A good operating system gives its owner a clear goal, honest feedback, and a set of rules that hold even on a bad day. PrimalOS runs your life and business on that same discipline. You make every real decision. The assistant reads the rules, tracks the numbers, names the risk — and hands every meatspace move back to you.

The owner
You
The only one who can make calls, send the email, ship the thing. The system never pretends otherwise.
The assistant
The agent
Reads the rules, runs the briefing, challenges weak plans. Serves the owner — never takes the wheel.
The memory
The vault
Goals, projects, guardrails, and logs — one home per fact, all in plain text you own.
The numbers
The metrics
Revenue actions, streaks, happiness, pipeline count. Honest numbers, updated the moment they move.
The key mechanics
Mechanic 01
A 6am agent that tidies while you sleep
Before you wake up, a scheduled agent walks the whole vault: refreshes stale timestamps, files away finished projects, reconciles the metrics tables, counts the pipeline, and flags anything past due. It leaves a single Daily Brief on your desk.
You open your laptop to a briefing that is already done — not a pile of housekeeping you have to do before real work can start.
Auto vault-checkDrift reconcilePipeline countPast-due sweep
Daily Brief.md — 06:00
# Daily Brief — 2026-07-06 (tidied while you slept) TIDIED 3 stale timestamps refreshed 1 finished project moved to _Archive metrics tables reconciled — no drift NEEDS YOU Card "Ship the widget" is past due → dead or done? RESURFACE You built "Sample Toolkit" 41 days ago and never shipped it. Still good? ONE BET moved yesterday — on track PIPELINE 6 warm leads (floor = 5) — OK
Mechanic 02
A daily "you forgot about this" line
Executive dysfunction has a cruel bug: out of sight, out of existence. A finished asset, a warm lead, a half-built product — if it scrolls off the screen, the brain treats it as gone.
So every morning the system resurfaces exactly one dormant thing: a past win, a parked idea, an asset you already own. Object permanence, delivered as a single line. The stuff you already made stops silently rotting.
Object-permanence fixOne line a dayRotates the graveyard
resurface — rotating
// one dormant thing, every morning Mon You wrote "Sample Article" and never published it. 20 min from live. Tue Lead "Client B" went quiet 12 days ago. Worth one more nudge? Wed "Old Prototype" has been parked 60 days. Ship, kill, or keep parking? Thu You hit a 4-week streak in May. You can do that again.
Mechanic 03
One home per fact
The number-one bug in every personal system is drift: the same fact written in three places, updated in one, wrong in the other two. PrimalOS bans it with a write map. Every kind of fact has exactly one home, and it is written the moment it happens — never batched to the end of the day.
Anything else that mentions that fact points to its home instead of copying it. One source of truth, so there is nothing to keep in sync.
No driftWrite on eventPortable plain text
Write Map — one home per fact
FACT → ITS ONE HOME Task status → Board.md card Revenue fact → BusinessHealth.md cell Project state → Context.md Done log → Done.md Mood → Mood.md Happiness signal → Happiness.md A mistake → Mistakes.md Assistant lesson → Memory/ written the moment it happens, never batched
Mechanic 04

Revenue guardrails,
balanced by a life side

A one-person business will quietly starve its pipeline and then panic. A driven person will quietly starve their friendships and then burn out. PrimalOS runs a guardrail on both — money and life get the same non-negotiable, daily attention.

BusinessHealth.md — revenue guardrails
THE ONE BET Land 2 direct clients this quarter | Lead | Status | Touch | Next | | Client A | Proposal | 2 | Jul 8 | | Client B | Contacted| 1 | — | | Client C | Replied | 3 | call | Daily action (Mon-Fri) ✓ done today Pipeline floor 6 / 5 warm — OK Net new this week Rs XX,XXX action is the gate, result is the score
Happiness.md — the life side
CALL 3 FRIENDS week of Jul 6 [x] Friend #1 — called Mon [ ] Friend #2 — due [ ] Friend #3 — due Happiness signal 7/10 shipped a thing, walked outside, ate a real lunch the scoreboard is not only money
The one bet
The single most important revenue focus, pinned to the top of every briefing. If it goes two days without moving, it hard-blocks the day until you move it or override out loud.
Action, not result
You cannot control who replies. You can control whether you sent something. The gate is a daily controllable action; the reply, the call, the money is the scoreboard.
Pipeline floor
Pipelines empty silently — that is the root fear. Every week the system counts warm leads. Below the floor, this week's job becomes: add more outbound. No surprises.
Mechanic 05
A day measured in minutes
Every task carries a minutes estimate. The morning briefing knows your peak focus window is only so many minutes long, sums the tags, and shows you what actually fits. No more planning a 9-hour day into a 4-hour brain.
Owner tags say who can do it — you, the assistant, or both. Every non-trivial card carries a "Done when" line, so finished is defined before you start.
Minute tagsPeak-window fitDone-when on every card
Board.md — Doing
## Doing (peak window: 240 min) [ ] Send proposal to Client A @{2026-07-08} ~45min @together Done when: PDF sent to named contact [ ] Draft 2 outreach emails ~30min @claude Done when: both in drafts, dated [ ] Ship the widget ~90min @me fits window: 165 / 240 min ✓
Mechanic 06

Nothing gets built
without a spec

Shiny-object syndrome is expensive. Before any new product, app, or feature gets built, it runs a lightweight pipeline — surface the blind spots, sketch throwaway options, get grilled one question at a time, write a short spec, then build. A quick quiz at the end proves it actually holds together before it ships.

STEP 1
Blind-spot
surface the unknown-unknowns first
STEP 2
Sketch
a few wild mockups, fake data, to react to
STEP 3
Grill
one question at a time, architecture first
STEP 4
PRD
short spec — problem, scope, done-when
STEP 5
Build
with a deviations log kept alongside
STEP 6
Quiz
prove it holds up before it ships
Mechanic 07

Thinking razors,
applied to every decision

A pocket set of mental models the assistant runs on every real decision — silently by default, out loud when you are planning. They kill weak plans before they cost you time and money.

Red Team
What is the strongest case against this? Find the flaw before you ship it.
Pattern Break
What doesn't fit the expected pattern? That mismatch is usually the signal.
Argue Other Side
Steel-man the opposite position before committing. Confirmation bias is costly.
Problem Not Symptom
What is actually causing this? Don't fix the surface and call it done.
First Principles
Strip the assumptions. What is irreducibly true? Rebuild from there.
Leverage Mountain
Does this build a lever that multiplies future effort, or just move today's rock?
80 / 20
Which 20% drives 80% of the result? Act on the vital few, cut the trivial many.
Premortem
Assume it ran perfectly and still failed. Name three reasons. Kill the deadliest.
Inversion
What would guarantee failure? List the sure paths to it, then remove them first.
Mechanic 08

Important work isn't done
until it survives an audit

First drafts lie. Anything high-stakes — a client proposal, a strategy doc, a code change — is not finished when it exists. It is finished when it survives a clean audit by fresh eyes: an independent reviewer each round, ranking blockers over minor nits, fixing and re-auditing until a full pass finds nothing. Capped so it can't loop forever.

Audit
check against a fit-for-task checklist
→
Rank
blocker > major > minor
→
Fix
blockers and majors first
→
Re-audit
fresh eyes, until a clean pass
Zoom out: the daily loop
How a day runs on PrimalOS
🌅 6am Agent
tidies the vault, writes the Daily Brief
→
Briefing
one bet · top tasks · inbox · resurface line
→
Work
revenue first · minutes-planned · ADHD-aware
→
Close
log done + mood · commit + push
The philosophy
Why it's built this way
"
Work with the brain, not against it.
Low-energy days are legal, not a moral failure. Forgotten things get resurfaced. The system bends to how a real, distractible human actually operates — instead of demanding the discipline of a robot.
"
One home per fact, or it will drift.
The moment a fact lives in two places, one of them starts lying. Everything writes to a single home and points to it from everywhere else. Truth stays in exactly one cell.
"
Survival first, then the dream.
Every decision passes a two-tier filter: does it keep the business alive now, and only then, does it serve a long-term goal? A grand plan that starves this month gets shrunk until survival is safe.
"
The assistant never takes the wheel.
It drafts, challenges, tracks, and tidies — but nothing irreversible fires without the owner's explicit go. You keep the wheel. The system keeps you honest.

Want an operating system
like this?

PrimalOS is the private engine behind Put The Player First — the same rigorous systems-thinking we use to design tools and programs for teams. If you want an operating system built around how you actually work, let's talk.

Work with us See the framework
PrimalOS · a personal operating system by Put The Player First
All examples on this page use placeholder data.