Skip to content

Appendices

Appendix A — Glossary of Terms

Term Definition
Career Recipe A concise, five-component description of a single professional skill unit: Domain, Skill Name, Trigger, Action Sequence, and Expected Outcome. Designed to be readable in thirty seconds and immediately applicable.
Execution Intuition The capacity to enter an unfamiliar context and rapidly form a reliable working hypothesis about what is happening, what matters, and what the right first move is. The target state of the HOS model.
Execution Loop The third pillar of the HOS: a dual-mechanism system combining real-world execution tracking with deliberate scenario sparring, designed to generate both rewards for existing execution and pattern recognition for new domains.
Human Operating System (HOS) The three-layer framework described in this paper: Instructional Deconstruction, Open Thinking Frameworks, and the Execution Loop. A model for high-velocity, multi-disciplinary professional mastery.
Instructional Deconstruction The process of breaking a complex professional competency into its minimum viable executable units — stripping away scaffolding to expose the core pattern of expert thinking.
Intuition Sparring A deliberate practice format in which AI-generated professional scenarios containing a single embedded flaw are presented for diagnosis under time pressure, with immediate feedback.
Judgement Deficit The gap between a practitioner's knowledge of a domain and their capacity for reliable, fast decision-making within it. The central problem this paper addresses.
Operational Sixth Sense An alternative term for Execution Intuition, used to describe the state in which pattern recognition fires automatically — before the practitioner has consciously articulated the framework they are applying.
Time-to-Learn-Skills (TTLS) A measurable variable: the elapsed time from first encountering a professional skill to being able to apply it reliably and autonomously in a real context. The primary metric that Instructional Deconstruction is designed to reduce.
Thinking Framework A structured set of questions and pattern-recognition cues for a specific professional domain. The HOS maintains five: Design, Business, Market, User, and Project.

Appendix B — The Five Thinking Frameworks: Current State

The frameworks are living documents. The table below represents the core triggering questions for each domain as of the initial publication of this paper. They will be updated as community contributions refine them.

Design Framework — Core Triggering Questions

  1. What job is this designed to do, from the user's perspective rather than the designer's?
  2. Where does this create unintended friction?
  3. What has been optimised for, and what has been deprioritised in that optimisation?
  4. What assumptions about user context are baked into this design?
  5. If the user's circumstances were different, where would this break?

Business Framework — Core Triggering Questions

  1. Where in this system is value actually being created?
  2. What is being exchanged for what, and is that exchange sustainable?
  3. What does the unit economics story say about the health of the model?
  4. Who captures the value, and what gives them that capture position?
  5. What market assumption is this model most dependent on — and what happens if that assumption changes?

Market Framework — Core Triggering Questions

  1. Who else is solving this problem, and what does their approach reveal about what buyers actually value?
  2. Is the urgency of this problem increasing, decreasing, or stable?
  3. Where are the unserved segments, and why are they unserved?
  4. What does the distribution of existing solutions tell us about where the real constraint is?
  5. What needs to be true about timing for this to work — and is it true now?

User Framework — Core Triggering Questions

  1. What is the user actually trying to accomplish — not the stated goal, but the underlying one?
  2. Where in their journey does this create or remove friction?
  3. What would we need to believe about user behaviour for this decision to be correct?
  4. How are we currently receiving signal from users — and how much should we trust that signal?
  5. What behaviour are we hoping to change, and what is currently maintaining the behaviour we want to replace?

Project Framework — Core Triggering Questions

  1. What is the critical path, and where is it most fragile?
  2. Where is the resource constraint — and are we building around it or against it?
  3. What are the highest-probability failure modes, and when do they become visible?
  4. What is the minimum viable version that still tests the core assumption?
  5. What does the team not yet know that they need to know — and when does not knowing it become dangerous?

Appendix C — Career Recipe Template

Use this template to capture a Recipe from any successful execution.

DOMAIN:
[Design / Business / Market / User / Project]

SKILL NAME:
[Name the specific, executable skill — one line]

TRIGGER:
[Describe the condition that tells you to deploy this skill]

ACTION SEQUENCE:
1.
2.
3.
4. (add or remove steps as needed)

EXPECTED OUTCOME:
[Describe what successful execution produces — one or two sentences]

CONTEXT NOTES (optional):
[Any caveats about industry, team size, geography, or other context
 that affects when this Recipe works or doesn't]

Appendix D — Bibliography & Foundations

The HOS framework is built upon established research in cognitive science, expertise development, and the author's previous work on community-led systems.

Primary References

  • Itseuwa, O. (2023). Building Communities into Economies: A Systematic Approach to Growth and Innovation. Link
  • Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). The role of deliberate practice in the acquisition of expert performance. Psychological Review.
  • Klein, G. (1998). Sources of Power: How People Make Decisions. MIT Press.
  • Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science.

Theoretical Foundations

  • Deliberate Practice: Built on the work of Anders Ericsson regarding the necessity of immediate feedback and scenario volume for mastery.
  • Mental Models: Draws from Charlie Munger’s "Latticework of Mental Models" (2005) and Shane Parrish’s synthesis of multi-disciplinary thinking.
  • Cognitive Load Theory: Implementation of Instructional Deconstruction based on John Sweller's research on reducing extraneous cognitive load to accelerate skill acquisition.

Appendix E — Tools & Reference Implementations

The following tools provide the software infrastructure for the Execution Loop:

  • SYD Protocol (Current): syd-protocol.github.io/terminal
    A gamified, terminal-style interface for logging real-world execution and deliberate practice.
  • Slop Runner (Legacy): slop-runner.github.io/game
    A prototype designed to test the initial mechanics of the pattern-recognition loop.

← Section 8 | ↑ Back to Home