---
name: spielos-run-workflow
description: Run an accepted SpielOS workflow or complete a bounded host-agent assignment with durable request identity and pinned context.
---

Select and inspect the company. Reuse a released workflow for the requested work;
production requests do not start GODAE again. Supply validated inputs and a
stable request key for one logical invocation. Repeating the request uses the
same key and inputs; changing inputs needs a distinct request.

For host execution, claim the named run before acting. Follow its assignment,
permissions, pinned skill/context documents and causal memory citations. Deliver
with that claim's token. A restarted chat restores the assignment; it must not
fetch or substitute a newer token for stale work.

Evaluate actual output and expose missing or errored checks. An unknown provider
result calls for reconciliation of that same run, never blind re-execution.
Cancel through the runtime and inspect the resulting state before claiming the
provider stopped. Use the host's supported wake/scheduling mechanism only when
the owner requested scheduling; do not install a SpielOS daemon.

Draft generation does not authorize sending or publishing. Present the exact
action, destination, reviewed content and scope for owner approval separately.


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.