A Player OS

The A Player Operating System. Build. Run. Learn. Compound.

            PLAYBOOKS
             (build)
               ╱╲
              ╱  ╲
             ╱    ╲
            ╱      ╲
           ╱ ASSETS ╲
          ╱(compound) ╲
         ╱             ╲
        ╱               ╲
       ╱_________________╲
  DEBRIEFS          OPERATIVES
   (learn)             (run)

The four stages

Playbooks — sequential. An executable build sequence. Defined input, ordered skills, defined output. Authored by humans, executed by agents, refined through debriefs. A playbook that hasn't been run is just an opinion. One that's been run and refined is institutional knowledge with teeth.

Operatives — cyclical. A persistent autonomous agent that watches for a trigger, executes a response, and returns to watching. It doesn't terminate — it cycles. Where a playbook is invoked, an operative is deployed. An operative without a boundary event is just a busy loop. A well-tuned operative compounds every asset it touches.

Debriefs — reflective. Structured intelligence extracted from what happened. Raw data in, synthesised understanding out — patterns, anomalies, causal links, recommendations. Debriefs feed playbooks, tune operatives, and appraise assets. A debrief that doesn't change a playbook or operative was a waste of cycles.

Assets — cumulative. Any durable artefact that compounds through reuse. Code, design systems, trained models, documented decisions, brand. Assets are the residue of playbooks running, operatives cycling, and debriefs refining. Every rotation should leave more than the last. An asset nobody's compounding is depreciating.

How it works

Playbooks builds assets. Operatives runs on assets. Debriefs evaluates assets. Assets compound. Each rotation leaves more than the last.

No stage owns the assets. All stages shape them. A Player OS accelerates because the assets at the center get better every turn — not because any single stage gets faster.

The repos

Repo	Stage	Behaviour
aplayerlabs/playbooks	Build	Sequential
aplayerlabs/operatives	Run	Cyclical
aplayerlabs/debriefs	Learn	Reflective
aplayerlabs/assets	Compound	Cumulative

Nomenclature

See GLOSSARY.md for the canonical terminology. All product repos defer to this file.

Term	What it is
A Player Labs	The company
A Player OS	The system. This repo describes it.
Playbooks	Build stage. Product name stands alone — never "A Player Playbooks".
Operatives	Run stage. Same rule.
Debriefs	Learn stage. Same rule.
Assets	Compound stage. The center of the triangle.
Skill	A slash command. The unit of interaction within any product.
Playfield	The project folder. The bounded environment. Shared concept across all products.

License

MIT. See LICENSE. Built by A Player Labs.