orchestration
Control Plane Harness
High
A transactional local control plane for a deliberate new Master structure.
Scenario
“I am creating a new structure that needs a strict registry, transactions, and recovery.”
- Best for
- A new control plane whose registry and lifecycle mutations justify transactions and recovery.
- Not for
- Adopting an existing project layout, dispatching agents, or executing project work.
- What it changes
- Creates a strict Master registry and managed front structure through validated transactional mutations. It does not call models or dispatch agents.
Installation prompt
View full prompt
Install Control Plane Harness (`orchestration`) v0.2.0 from https://github.com/fabianomag/agent-harnesses/releases/download/v0.2.0/orchestration-0.2.0.zip. Before any write, confirm the explicit target and resolve exactly one Python 3.10+ executable available to the user or system as `<python>` (for example `python3`, `python`, or `py -3`); reuse only that executable and never use a private Codex runtime. Download the ZIP and its adjacent `.sha256` sidecar into an isolated temporary directory, verify the checksum before extraction or execution, then extract it. From the extracted bundle root run: `<python> -B installer.py doctor orchestration --target "<target>" --json` Stop without writes on a mismatch and only recommend a better fit; never silently substitute another harness. Then run: `<python> -B installer.py install orchestration --target "<target>" --dry-run --json` `<python> -B installer.py install orchestration --target "<target>" --apply --json` Follow `package/README.md` inside the extracted bundle to initialize the target, then run from the bundle root: `<python> -B installer.py verify orchestration --target "<target>" --json` Report success only when this final result contains `ready=true`. Clean up temporary files and report the receipt plus `uninstall`/rollback instructions. Do not edit unrelated documentation, `PATH`, or `.gitignore`, and do not install a global Skill.