SpielOS — the company harness

One durable loop for operating AI work as a company system:

GOAL -> OBSERVE -> DECIDE -> ACT -> EVALUATE
          ^                            |
          +----------------------------+

The runtime owns every Goal, Run, approval, evidence record, and notification. Departments are Lego packages: self-contained folders that supply business behavior and never create another loop. Codex, OpenCode, and humans are all clients of the same persisted state.

Install (one line)

pipx install spielos && spielos init

spielos init scaffolds a verified, self-contained harness home into your current folder — with OpenCode-style progress, an optional starter-department picker, host detection, and a runtime verification before it reports success.

Update (one line)

pipx upgrade spielos && spielos refresh

pipx upgrade fetches the newest release; spielos refresh re-vendors the runtime spine and host adapters into every home on this machine while keeping your strategy, assets, departments, installed agents, and .spielos/ state.

No pipx yet? The bootstrap installer sets everything up (Python check, pipx, spielos) and runs init in an empty folder automatically:

curl -fsSL https://raw.githubusercontent.com/ShayanSpiel/SpielOS/main/install.sh | sh

spielos init scaffolds a fresh home into your current folder — with OpenCode-style progress, host detection, and a runtime verification before it reports success.

Fresh means: the spine only — runtime, company skills, OpenCode/Codex adapters, empty .spielos/ state, opencode.json, AGENTS.md. Zero departments, zero strategy content. Your company starts empty; the Director onboards you and capabilities are added when goals need them:

spielos add outbound                 # install a built-in department
spielos add ./team.sdep              # or your own exported bundle
spielos init --department seo        # or vendor starters at scaffold time

Departments as products

Every department is one extractable folder: behavior (department.py), workflows, evals, skills, templates, and tooling live together.

spielos department export outbound --out ./dist   # portable .sdep bundle
spielos add ./outbound.sdep                        # install into a home
spielos add ./outbound.sdep --force                # upgrade in place
spielos init --department outbound                  # scaffold with one starter department

Bundles carry a checksummed manifest plus the department's skills. They never carry strategy, assets, credentials, or run state.

First-class workers

Any workflow compiles into a bounded agent worker (no Director, no routing):

spielos agent compile outbound --workflow social-lead-research --name lead-researcher

Emits the OpenCode agent, Codex TOML, and roster entry from one WorkflowSpec. The worker runs only that workflow, produces only its declared evidence kinds, never edits files; approvals still park in the runtime.

Updating

pipx upgrade spielos   # new CLI
spielos refresh        # re-vendor spine + hosts into an existing home;
                       # preserves strategy/, assets/, departments/, .spielos/

Layout

company/            Python package: runtime spine, evals, connections, CLI
  skills/           operator methods (director, department-runner, …)
  departments/      LEGO SHELF — each folder is an extractable product
    _shared/        cross-department contract + shared methods
    <id>/skills/    department-owned methods
    design/tools/   render/TTS tooling · design/tokens/ brand tokens
hosts/              adapter sources vendored into homes by init
tests/              → company/tests/ (in-package)
docs/               architecture notes
.spielos/           private runtime state (gitignored; exists only when this
                    checkout itself operates as a live company home)

Authority for architecture, vocabulary, pursuit semantics, safety rules, and the owner doctrine: company/README.md.