humanOS: The Controls
What can you actually do?
You’ve loaded into the map. You’ve got your gear. Now the match starts.
What are your actual moves?
humanOS is your control scheme. The real-time execution layer. The reflexes, the micro-decisions, the adaptive loops that turn plans into actions.
This is where the game is actually played.
Why Controls Matter
You can understand the map perfectly. You can have the best loadout in the world.
But if you can’t execute — if you can’t move, aim, adapt, respond — none of it matters.
Good players have good keybinds.
They know:
- What tools they have access to
- How to deploy them quickly
- When to switch modes
- How to recover when things go wrong
humanOS is the system that makes execution legible, trainable, and improvable.
What humanOS Actually Does
humanOS is a metacognitive framework for modeling and improving how you actually operate in real-time.
It’s the layer that tracks:
- What you’re doing right now (current state)
- What you could be doing (available actions)
- What’s blocking you (constraints, resources, attention)
- How you adapt (response patterns, recovery loops)
Think of it as:
- Your keybind config — the notation system for capturing decisions
- Performance monitoring — seeing where execution breaks down
- The training mode — identifying what to practice
The 14 Systems (Your Full Control Scheme)
humanOS breaks daily execution into 14 interoperable systems — each one a domain where you’re already making decisions, whether you know it or not.
| System | Domain | What It Controls |
|---|---|---|
| WardrobeOS | Physical inventory | What you wear, own, maintain |
| gatorFinance | Money & resources | Cash flow, budgets, value tracking |
| SnakeSocial | Relationships | Network topology, interaction patterns |
| LTS Octopus | Time & tasks | Scheduling, prioritization, execution |
| FoodOS | Nutrition & energy | What fuels your body and when |
| SleepOS | Recovery & rhythms | Rest cycles, energy management |
| MovementOS | Physical capacity | Exercise, mobility, physical state |
| EnvironmentOS | Space & setup | Where you work, how it’s configured |
| LearningOS | Skill acquisition | What you’re training, how you practice |
| CreativeOS | Idea generation | How you capture, develop, ship creative work |
| CommunicationOS | Information flow | How you read, write, speak, listen |
| DecisionOS | Choice architecture | How you evaluate options and commit |
| EmotionalOS | Affective state | Mood tracking, regulation, expression |
| IdentityOS | Self-model | Who you think you are, how that shapes action |
Each system has:
- Inputs — what information it needs
- Outputs — what actions it produces
- Interfaces — how it connects to other systems
The Execution Loop
Every match runs the same basic loop:
- Check — what’s the current state?
- Decide — what’s the next move?
- Execute — do the thing
- Adapt — did it work? What changed?
Repeat.
humanOS makes this loop visible so you can:
- See where it breaks
- Speed up the cycle
- Train better reflexes
- Build new habits
How It Works With the Other Layers
| Layer | Relationship to humanOS |
|---|---|
| mythOS (The Map) | Defines what success looks like, shapes your strategy |
| archiveOS (The Loadout) | Provides the tools and knowledge you execute with |
| humanOS (The Controls) | Does the actual button-pressing in real-time |
Your map tells you where to go. Your loadout gives you what to bring. Your controls determine whether you can actually get there.
humanOS is where theory meets practice.
Examples in Practice
Morning Routine
Without humanOS: “I should probably work out… and eat better… and get organized… but I’m already behind…”
With humanOS: You have a mode (morning startup sequence). It chains: WardrobeOS → FoodOS → MovementOS → DecisionOS. Each system knows its inputs and outputs. Execution is automatic.
Context Switching
Without humanOS: “I was deep in that task, then got interrupted, now I can’t remember what I was doing…”
With humanOS: The notation system captured your state. You have a keybind for “pause + checkpoint.” You resume exactly where you left off.
Burnout Recovery
Without humanOS: “I’m exhausted but I don’t know why. I should just push through…”
With humanOS: You check the dashboard: SleepOS is red, MovementOS is yellow, DecisionOS is overloaded. The system tells you: you’re not being lazy, you’re resource-constrained. Adjust the loadout, not your identity.
The Notation System (Your Keybinds)
One of humanOS’s core tools is a notation system — a symbolic language for capturing complex decisions and states quickly.
Think of it like:
- Vim keybinds for your life
- Shorthand for “I’m in this mode, doing this thing, tracking these variables”
Example notation:
[mode=deep-work] + [context=writing] + [blockers=none] + [energy=high]
→ execute: draft new section
This isn’t overcomplicated. It’s compression.
Instead of re-deciding “what should I do now?” every time, you have pre-configured modes you can load instantly.
That’s what good keybinds do.
The Core Philosophy
“You can’t improve what you can’t see. You can’t train what you can’t measure.”
humanOS isn’t about optimizing your life into a robot routine.
It’s about making your execution visible so you can:
- Understand your own patterns
- Identify what’s working
- Fix what’s breaking
- Build better reflexes over time
Conscious execution beats unconscious drift.
Go Deeper
- The Map (mythOS) — the world-rules that shape your execution
- The Loadout (archiveOS) — the tools and knowledge you execute with
- Career Stats — how 20,000 hours refined these systems
← Back to almanOS