---
name: spielos-company
description: Inspect an explicitly selected SpielOS company and restore its durable workflow context across chats.
---

Use the SpielOS tools over the bundled runtime. First call `select_company`
with the owner's absolute installed-home folder, then use its returned
`company_id` for every operation. Installation never selects or creates a home.
If the owner has not selected a company, ask for that folder; do not use the
plugin directory, source checkout or an unrelated browser tab as company context.

Read `inspect_company` before continuing company work. Describe Company,
Workflow, Run and Improvement using names and outcome sentences. Machine ids,
status codes, payloads and CLI details stay in tool fields unless requested.
Read only workflow-relevant context. Preserve unrelated private company data.

A local pilot is not an enterprise service or compliance certification. Host
wakes and schedules are separate from durable run state. Activepieces remains
inactive until the owner separately authorizes its connection and execution.


Evaluation and observability are governed by `EVALUATION.md` and `spielos-evaluation/2`. Codex/Claude/OpenCode is the host; Director is a recorded SpielOS role in that host. Start or reuse the activity session supplied by the context hook; pass its session identity with runtime operations. If capture is missing, say what is unobserved and start explicit activity recording before claiming observable work. Log actual supplied/changed context, tool outcomes, measured artifacts and feedback targets. Classify each correction as run/project/owner/workflow/evaluation/build scope and state its recorded consequence. During an order, keep artifact revisions and bounded candidate Improvements distinct; never silently mutate the active release. Evals must judge actual behavior/output against explicit questions and anchored criteria. A filename, schema pass or successful command is only supporting evidence. Inspectable Langfuse inputs/outputs, datasets, experiment items, ratings and rationale must be confirmed remotely before qualification. Local passing evidence remains awaiting telemetry. Templates, synthetic tests and self-ratings never certify Director/model/creative quality. Record exposed usage with its source; hidden context/reasoning and unavailable host tokens stay unknown.


Use the selected company's live `/report` record for workflow/run counts, memory, supplied context, artifacts, evaluations and telemetry status. Read `company/evaluation-and-learning-contract.md` when present. Every new or changed workflow needs the executable evaluation pair and regression cases before qualification. Record actual host token metadata and separately sourced reference prices; never invent usage, billed cost, memory retention or independent acceptance. End meaningful work with a concise human tracking receipt and report/trace links. Keep company content in the selected home and reusable product code in source; no publication, hidden pursuit or cross-company routing is implied.

For setup or a missing company, use the bundled setup skill. Resolve the launcher at scripts/entry.py relative to the installed plugin root. Use it for report and experiment operations that are not exposed by the six MCP tools; never require a separate global SpielOS installation. The runtime operating guide is bundled at runtime/company/README.md. Keep those commands internal and give the user names, findings and next decisions.