Orchestrarium

A cross-provider agent orchestration monorepo that keeps the production Codex and Claude Code lines aligned on one shared governance and reference core, while temporarily retaining deprecated full-mirror examples for Gemini and Qwen pending the npm-skillpack-distribution epic:

• src.codex/ — the production Codex provider-pack source
• src.claude/ — the production Claude Code provider-pack source
• src.gemini/ — deprecated Gemini full-mirror example around GEMINI.md; repository status: DEPRECATED / WEAK MODEL / NOT RECOMMENDED
• src.qwen/ — deprecated Qwen full-mirror example around QWEN.md; repository status: DEPRECATED / WEAK MODEL / NOT RECOMMENDED

The provider lines share one governance model and role vocabulary, while each keeps the runtime structure expected by its own provider. The root router install surface is production-first: Codex plus Claude are the default shipped production install. Gemini and Qwen remain selectable only as deprecated demonstration/compatibility paths until the npm-skillpack epic decides whether to remove, archive, or generate them.

Warning: Orchestrarium is optimized for maximum execution effectiveness and low orchestration drag rather than for minimum token spend. On large tasks, multi-opinion review lanes, or aggressive external fan-out, usage can rise quickly and consume a substantial token budget in a short time.

New maintenance sessions should start with docs/new-session-guide.md. It records the source-first rule for this monorepo: tracked Orchestrarium source is canon, while ~/.codex/, ~/.claude/, project .agents/, and project .claude/ are installed runtime outputs that should not be patched as the durable fix before the source owner is updated.

WARNING: Claude external authentication

The Python-owned invoke-claude-prompt.py transport (also exposed through the thin POSIX launcher invoke-claude-prompt.sh) runs automated, headless claude -p. Subscription sign-in (OAuth), including Claude Pro and Max, is not permitted for these orchestrated runs; use a commercial API key, apiKeyHelper, Amazon Bedrock, or Google Vertex AI instead. The transport fails closed when it cannot detect one of those commercial-auth signals. For the secret-backed path, use invoke-claude-api.py or its thin invoke-claude-api.sh launcher with the credentials documented in SECRET.md. See Anthropic's Claude Code legal and compliance guidance.

Repository layout

shared/             Shared cross-provider governance and canonical reference cores
docs/               Common branch-level docs index and operator/runtime references
src.codex/          Codex provider-pack source
src.claude/         Claude Code provider-pack source
src.gemini/         Gemini example-provider source tree with `GEMINI.md`
                    and the universal `skills/` surface (skills-only)
src.qwen/           Qwen example-pack source tree with `QWEN.md`
                    and the universal `skills/` surface (skills-only)
references-codex/   Codex-specific addenda and compatibility pointers
references-claude/  Claude Code-specific addenda and compatibility pointers
references-gemini/  Gemini-specific addenda and compatibility pointers
references-qwen/    Qwen-specific addenda and compatibility pointers
RELEASE_NOTES.md    Canonical tracked release log
install.py          Python-owned entry-point installer (asks which pack to install)
install.sh          Thin POSIX launcher for `install.py`
scripts/            Pack-specific installers plus the repo-local publication gate
AGENTS.md           Dev overlay for Codex pack maintenance
CLAUDE.md           Dev overlay for Claude Code pack maintenance

Provider Packs

Pack	Status in this monorepo	Source	Runtime entrypoint in source	Packaging in this branch	Validation
Codex	Production	src.codex/	assembled installed AGENTS.md from shared/AGENTS.shared.md + src.codex/AGENTS.codex.md	root Python router plus scripts/install-codex.py and its POSIX launcher	validate-skill-pack.py and its POSIX launcher
Claude Code	Production	src.claude/	src.claude/CLAUDE.md	root Python router plus scripts/install-claude.py and its POSIX launcher	validate-skill-pack.py and its POSIX launcher
Gemini CLI	Deprecated full-mirror example (WEAK MODEL / NOT RECOMMENDED)	src.gemini/	src.gemini/GEMINI.md importing shared/AGENTS.shared.md	retained compatibility installer pending npm-skillpack	validate-pack.sh and validate-pack.ps1
Qwen	Deprecated full-mirror example (WEAK MODEL / NOT RECOMMENDED)	src.qwen/	src.qwen/QWEN.md importing shared/AGENTS.shared.md	retained compatibility installer pending npm-skillpack	validate-pack.sh and validate-pack.ps1

Shared design references now live in shared/references/. Provider-local references-codex/, references-claude/, references-gemini/, and references-qwen/ keep provider-specific addenda plus compatibility pointers where older paths still need to resolve. The clearest example is subagent-operating-model: the canonical blueprint core now lives in shared/references/subagent-operating-model.md, while each provider-local tree keeps only its runtime and repository concretization addendum. Shared governance is maintained across provider lines; the repository-level overlays in AGENTS.md and CLAUDE.md exist only for maintaining this monorepo.

The maintainer-only cross-pack reconciliation manifest maps shared semantic blocks between provider contracts. It is intentionally excluded from standalone provider branches and packages.

Installed Codex now follows the same compact-entrypoint pattern that Claude already uses: the installed AGENTS.md is intentionally the compact universal minimum, while installed runtime guidance lives in the Codex skill bodies under skills/<role>/SKILL.md. Shared and provider-specific reference trees remain source-maintainer canon rather than installed target-project docs. Claude keeps a short CLAUDE.md entrypoint and leaf-role files under .claude/agents/; the deliberate exception is the five curated role-skills — lead, product-manager, analyst, architect, planner — whose canonical contracts live at .claude/skills/<role>/SKILL.md (.claude/agents/lead.md is a fail-closed compatibility stub; the other four keep thin delegate wrappers under .claude/agents/ that load the same-named skill).

Maintainer note: this repository is the installer/source monorepo, not automatically a repo-local Codex install target. When working inside Orchestrarium/, it is valid to rely on the global Codex install under ~/.codex/. A missing local .agents/ tree in this monorepo does not by itself mean the Codex runtime is misconfigured; create .agents/ here only by running the installers intentionally.

Installed governance now requires a cited repository-orientation record before the first run, build, or mutation in an unfamiliar repository or subtree. The record names scope, live/archive status, canonical workflow, protected surfaces, and file:line evidence; names, file counts, recency, and layout never prove liveness. The production Claude Code and Codex installers also register a warn-only, fail-open process audit that detects a skipped or conflicting record without scanning repository prose or inferring canon from deprecation words.

Cross-provider execution is available through two routing adapters:

• $external-worker is the external execution adapter for eligible worker-side roles.
• $external-reviewer is the external execution adapter for eligible review and QA roles.
• $consultant remains advisory-only and is not reused for implementation or review gates.

Work-item physical lifecycle

The Codex and Claude production packs use one physical lifecycle owner for local task memory. Current work is in category roots such as work-items/backlog/ and work-items/active/; terminal identities exist only under that category's archive/YYYY-MM/ directory, selected from explicit strict UTC terminal evidence. status.md is active recovery state and closure.md is final work-item outcome. The generated work-items/README.md and compatibility index.md do not authorize transitions. Historical records without explicit terminal evidence remain unmoved for a human data decision; the workflow does not infer timestamps, status, or archival targets. Two owner-managed legacy transitions handle the old directory-shaped backlog: convert-legacy-candidate creates one visible flat candidate while preserving every accepted source text and digest as an appendix, and retire-legacy-backlog records an explicit product rejection directly in the monthly archive without inventing candidate, active, or closure history.

Installation

Use the root router installers for the common path:

bash install.sh --global

python .\install.py --global

Each router asks what to install:

What to install?
Production installs:
  1) Codex pack
  2) Claude Code
  3) Codex + Claude (default production install)
Deprecated example integrations (retained pending npm-skillpack):
  4) Gemini CLI (DEPRECATED / WEAK MODEL / NOT RECOMMENDED)
  5) Qwen (DEPRECATED / WEAK MODEL / NOT RECOMMENDED)

Pressing Enter selects the default production install, Codex + Claude. The router then forwards the same arguments to the selected provider-specific installer in scripts/. Use scripts/install-codex.*, scripts/install-claude.*, scripts/install-gemini.*, or scripts/install-qwen.* directly when you want deterministic automation on one line. If a future checkout lacks the root scripts/install-qwen.* entrypoints, the router hides the dedicated Qwen slot and you should fall back to the Qwen source tree and provider-local docs directly.

Important: operator preferences live in per-provider agents-mode files; all provider lines may read the lower ~/.agents-mode.yaml cross-pack global overlay below their pack-local globals. Only Codex and Claude use that shared file for shipped production routing; Gemini and Qwen remain example-only consumers of the same fallback shape.

• Codex reads .agents/.agents-mode.yaml.
• Claude Code reads .claude/.agents-mode.yaml.
• Gemini reads .gemini/.agents-mode.yaml.
• Legacy extensionless .agents-mode files remain compatibility input only. Decision-driving reads should resolve in this order: provider-local .agents-mode.yaml, local legacy .agents-mode, matching pack-local global ~/.<provider>/.agents-mode.yaml, matching pack-local global legacy .agents-mode, then the shared cross-pack global ~/.agents-mode.yaml, then built-in defaults. scripts/resolve-agents-mode.py --provider <provider> --json is the executable reference for this per-key read order. Normalize whichever file supplied the effective config into the canonical .yaml path in the same scope without recreating any legacy path or synthesizing a project-local override on read alone.
• Reinstall is expected to do the same maintenance work for installed overlays: if the shipped schema or defaults changed, the installer must rewrite an existing .agents-mode.yaml to the current canonical form instead of preserving stale pack-owned structure verbatim.
• consultantMode controls $consultant.
• delegationMode: manual keeps explicit-permission behavior, auto leaves ordinary delegation enabled by routing judgment, and force makes delegation a standing instruction whenever a matching specialist and viable tool path exist. Because the host does not parse .agents-mode.yaml natively, the production Claude/Codex installers register an agents-mode-reminder SessionStart hook that surfaces the active auto/force posture into the main conversation at session start and after compaction (silent on manual), so an init-project run is not required for the posture to take effect.
• parallelMode: manual keeps parallel fan-out explicit-by-request, auto leaves safe parallelism enabled by routing judgment for any independent internal or external lanes, and force makes safe parallel launch a standing instruction whenever scopes are independent and the merge cost is justified.
• mcpMode: auto lets the agent decide when MCP is appropriate; force means the config itself is an explicit instruction to use relevant available MCP tools instead of treating MCP usage as optional.
• preferExternalWorker and preferExternalReviewer let routing prefer $external-worker on implement and $external-reviewer on review and QA.
• Production externalProvider routing now uses auto | codex | claude. externalProvider: auto is lane-driven, not host-pack-driven, and the shipped production profiles stay on the Codex/Claude provider pair with reserve allowed only as a supplemental advisory/review candidate.
• The current Gemini and Qwen full-mirror packs are DEPRECATED / WEAK MODEL / NOT RECOMMENDED. They remain available only for demonstration, compatibility, and inspection, do not participate in production auto profiles, and must not receive feature/parity work before the npm-skillpack-distribution epic decides their replacement or removal.
• externalPriorityProfile selects the active named provider-order profile, reserveResolver binds the symbolic reserve slot to a concrete read-only resolver, externalPriorityProfiles stores the switchable per-lane provider orders, and externalOpinionCounts raises specific lanes above the default single-opinion behavior when one external opinion is not enough. Those counts are lane-local distinct-opinion requirements, not a cap on how many parallel external helper instances may run overall; parallelMode remains the general fan-out rule for any helper lane, while bounded same-provider external helper fan-out lives under the dedicated brigade surfaces.
• externalModelMode: runtime-default | pinned-top-pro remains the shared production model policy for the Codex/Claude pair. runtime-default leaves the resolved provider on its runtime default model/profile; pinned-top-pro starts on the strongest documented provider-native model/profile and allows one named same-provider fallback on limit-style failures.
• externalCodexProfile: default | gpt-5.6-sol-xhigh | gpt-5.6-sol-max | gpt-5.6-terra is the Codex-specific external profile override. The shipped value is gpt-5.6-sol-xhigh, symmetric to Claude's opus-xhigh. default instead inherits externalModelMode after provider resolution; gpt-5.6-sol-xhigh pins model gpt-5.6-sol with model_reasoning_effort = "xhigh" regardless of externalModelMode; gpt-5.6-sol-max requests model gpt-5.6-sol with model_reasoning_effort = "max" for higher-complexity/hard lanes; gpt-5.6-terra selects the balanced Codex model (a distinct model, model_reasoning_effort = "high", not an effort suffix) and must be verified against the installed Codex runtime — a genuine cheaper-than-flagship reasoning lane, review-gated like any external lane, replacing the former gpt-5.5-fast and gpt-5.3-codex-spark.
• Explicit self-provider selection is allowed only as an override for isolation, transport, profile, or an intentionally independent rerun.
• reserve is a symbolic advisory/review-only profile candidate. It is not a scalar provider, not a worker path, and not a silent fallback from primary claude or codex; reserveResolver: claude-sonnet | claude-wrapper | wrapper:<command> | disabled selects the concrete read-only resolver, where wrapper:<command> is a PATH-resolved command or repo-relative wrapper path.
• External provider CLI launches use file-based prompts by default: write substantive task prompts to temporary prompt files and feed them through stdin or a provider-supported file-input mechanism instead of putting the full prompt in argv.
• Codex may additionally use externalClaudeProfile to select or override the Claude CLI execution profile: sonnet-high, opus-xhigh (shipped default), opus-max (max-depth escalation for especially hard tasks at caller discretion), or fable-xhigh (current Claude flagship-family best-effort tier; the fable flagship alias as of 2026-07). New Codex installs seed opus-xhigh by default unless a preset or explicit override chooses otherwise.
• Codex install does not seed .codex/agents/default.toml, worker.toml, or explorer.toml; native subagent model and reasoning selection stays with the runtime or an explicit operator-owned override. Reinstall removes only recognizable retired Orchestrarium-owned copies at those paths and preserves genuinely customized user files.
• Provider-specific workdir keys stay separate and default to neutral: externalCodexWorkdirMode, externalClaudeWorkdirMode.
• For first-time Codex project setup, run $init-project to write ## Project policies in the root AGENTS.md and review or update the installed default .agents/.agents-mode.yaml. If local Codex overlay files are missing but ~/.codex/.agents-mode.yaml exists, ordinary reads should use that global overlay honestly until you choose to create a project-local override.
• When the current working directory is this installer monorepo itself, a missing local .agents/.agents-mode.yaml should fall back to the global Codex install by default. Create a repo-local install only when you explicitly want project-local runtime state; the installer source tree and the installed runtime are different surfaces.
• For first-time Claude Code project setup, run /agents-init-project to write ## Project policies in .claude/CLAUDE.md and review or update the installed default .claude/.agents-mode.yaml. If local Claude overlay files are missing but ~/.claude/.agents-mode.yaml exists, ordinary reads should use that global overlay honestly until you choose to create a project-local override.
• Deprecated Gemini compatibility use: use Gemini's built-in /init to generate or tailor GEMINI.md, keep official runtime config and MCP wiring in .gemini/settings.json or extension manifests, and do not extend the Orchestrarium full-mirror pack.
• Deprecated Qwen compatibility use: use Qwen's built-in /init to generate or tailor QWEN.md, keep official runtime config and MCP wiring in .qwen/settings.json or extension manifests, and do not extend the Orchestrarium full-mirror pack.
• Explicit user role requests still override the toggle state in either direction.
• Full value-by-value operator semantics live in docs/agents-mode-reference.md, including task continuity, continue-by-default execution expectations for initialized projects, and the current init-time preset family: default, absolute-balance, external-aggressive, correctness-first, power-mode, and max-speed. Init helpers can either write the chosen preset as-is or open an optional fine-tune pass before saving .agents-mode.yaml.
• Machine-readable agents-mode contract sources live in shared/agents-mode.schema.json and shared/agents-mode.presets.json. scripts/validate-agents-mode-contract.py checks those sources against the shared YAML exemplar, the operator reference, and provider init surfaces.

Shipped production provider-order profiles:

These are the persisted production externalPriorityProfile choices shipped from the root surfaces, not the init-time preset shortcuts. Example integrations may define their own provider-local examples, but root production profiles stay on Codex plus Claude provider families only. reserve may appear only as a supplemental read-only candidate after primary Claude and Codex on advisory/review lanes.

Lane	Balanced priority	Quality-first priority
advisory.repo-understanding	claude > codex > reserve	codex > claude > reserve
advisory.design-adr	claude > codex > reserve	codex > claude > reserve
design.ui-ux-structure	codex > claude	codex > claude
worker.reasoning-constraints	claude > codex	claude > codex
worker.default-implementation	codex > claude	codex > claude
worker.systems-performance-implementation	claude > codex	codex > claude
worker.ui-implementation	claude > codex	claude > codex
worker.visual-graphics-visualization	claude > codex	claude > codex
review.pre-pr	claude > codex > reserve	codex > claude > reserve
review.security	claude > codex > reserve	codex > claude > reserve
review.performance-architecture	codex > claude > reserve	codex > claude > reserve
review.ui-visual-correctness	codex > claude > reserve	codex > claude > reserve

If a repo-local lane policy explicitly asks for consultant input at closeout, it should follow the configured consultantMode; consultantMode: disabled waives consultant closeout instead of blocking the batch. parallelMode is the general rule for whether any helper lanes are parallelized by judgment or only by explicit request, while externalOpinionCounts may still raise advisory or review lanes above 1 when the active policy wants multiple independent external opinions before advancing.

See INSTALL.md for quick install, pack-specific install details, dual-platform setup, and post-install customization.

Orchestration utilities

Two independence techniques ship on the Claude and Codex production lines (currently primary-pack only; the Gemini/Qwen demo mirror is deferred):

Technique	Stage	Claude	Codex
Review-loop	Independence at verification of one already-written artifact, across autonomous rounds	/agents-review-loop (.claude/agents/contracts/review-loop.md)	$review-loop (skills/review-loop/)
Design-panel	Independence at generation: N independently-framed candidate designs on one pinned problem, converged through one mandatory synthesis, before a single design exists	/agents-design-panel (.claude/agents/contracts/design-panel.md)	$design-panel (skills/design-panel/)

Both are conditional, deliberate-cost techniques with narrow explicit triggers — neither auto-invokes on plain "design" or "review". Composition is sequential: design-panel generates and synthesizes once, then optionally hands its output to review-loop for verification. See shared/references/design-panel-methodology.md and shared/references/review-loop-methodology.md for the provider-neutral design.

Common skills

In addition to roles, the pack ships common skills — workflow-focused capabilities that any role or the main conversation can invoke when the skill's description matches the current task. They package reusable methodology, gates, and evidence requirements without owning delivery.

Two archetypes:

• Knowledge-style — loaded into the caller's current context to inform how the caller performs the work.
• Delegate-style — additionally spawnable as a fresh-context subagent that executes the workflow and returns one self-contained artifact.

The governance index and runtime layout are defined in shared/AGENTS.shared.md under ## Common skills. Each provider source tree carries its native form under src.<provider>/skills/<name>/, and Claude delegate-style skills additionally register a thin Agent-tool wrapper at src.claude/agents/<name>.md.

Currently shipped:

• $windows-gui-manual-testing — delegate-style; Windows desktop GUI manual visual verification with screen capture, hard crop validation, and theme/state evidence across toolkit/runtime variants.
• $analyzing-video-bugs — knowledge-style; frame extraction, scene-change detection, and dense sampling for any UI/animation/layout bug video.
• $bug-hunting — knowledge-style; systematic runtime-bug investigation via diagnostic logging.
• $mathtype-book-page — knowledge-style; bring translated technical-book DOCX pages to accepted MathType format.
• $explain-simply — knowledge-style; reader-tailored plain-language explanations for concepts, code paths, results, decisions, and learner notes.
• $vak-dissertation-review — knowledge-style; review of a Russian dissertation (диссертация) and autoreferat for a кандидат/доктор наук defense — нормоконтроль, novelty, ВАК compliance, borrowings, references, ВАК-list publications.

References and maintenance

• shared/references/ contains the shared cross-provider design core that current and future provider packs can reuse.
• shared/agents-mode.defaults.yaml is the single editable YAML exemplar for provider default overlays in the monorepo. Keep it aligned with the machine-readable contract files, shared/agents-mode.schema.json and shared/agents-mode.presets.json; the pack validators call the shared contract check so docs, init helpers, defaults, and provider-order policy do not drift silently, and the normalizer reads the schema for provider/lane policy instead of carrying a second hardcoded provider universe. Main installers seed provider-local or global agents-mode files directly from that shared exemplar, with any provider-only additions applied at install time. Standalone pack repositories keep one shipped pack-root default for self-contained install seeding.
• docs/README.md is the common branch-level docs entrypoint for operator semantics and runtime-layout references.
• docs/provider-runtime-layouts.md records the installed production runtime layout for Codex and Claude Code, plus the current example-integration status for Gemini and Qwen, with global and local scopes split explicitly so install/runtime paths are not confused with repo source trees.
• references-codex/ contains Codex-specific addenda plus compatibility pointers for older reference paths.
• references-claude/ contains Claude-specific addenda plus compatibility pointers for older reference paths.
• references-gemini/ contains Gemini-specific addenda plus compatibility pointers for older reference paths.
• references-qwen/ contains Qwen-specific addenda plus compatibility pointers for older reference paths.
• subagent-operating-model is no longer duplicated per provider pack: use the shared core for the canonical blueprint and the provider-local file only for runtime and repository concretization.
• AGENTS.md is the root development overlay for Codex provider-pack maintenance.
• CLAUDE.md is the root development overlay for Claude Code provider-pack maintenance.

Before publishing maintenance changes, validate the active provider surfaces:

bash src.codex/skills/lead/scripts/validate-skill-pack.sh
bash src.claude/agents/scripts/validate-skill-pack.sh
bash src.gemini/scripts/validate-pack.sh
bash src.qwen/scripts/validate-pack.sh
python scripts/sync-agents-mode-docs.py --root . --check
python scripts/validate-agents-mode-installers.py --root .

python .\src.codex\skills\lead\scripts\validate-skill-pack.py
python .\src.claude\agents\scripts\validate-skill-pack.py
.\src.gemini\scripts\validate-pack.ps1
.\src.qwen\scripts\validate-pack.ps1
python .\scripts\sync-agents-mode-docs.py --root . --check
python .\scripts\validate-agents-mode-installers.py --root .

The docs sync command checks generated agents-mode tables, raised-count lists, and canonical YAML snippets against the JSON contract; use --write to refresh those generated blocks after intentional schema or preset edits.

The installer regression command creates disposable targets under /.scratch/, runs the Python production installers and the retained example-provider launchers, and verifies that stale agents-mode overlays are normalized to the current schema-backed contract. It also verifies that fresh Codex installs create no fixed preset overrides and that upgrades preserve customized preset files.

Work-item execution tracking uses agent-runs.jsonl beside status.md for machine-readable agent state. Use scripts/agent-run-ledger.* --work-item <path> init for one-time migration of missing status sections and ledger files, scripts/agent-run-ledger.* --work-item <path> append ... to append one validated event with rollback on failure, scripts/validate-work-item-state.* --work-item <path> before single-item closeout, and scripts/check-work-items-state.* --root . --stale-hours 24 before broad closeout or interruption recovery. The helpers catch stale agents, duplicate run IDs, missing evidence, inconsistent gates, or accepted artifacts that were never verified. scripts/agent-run-ledger.* rollup --root . (or --work-item <path> for one item) aggregates ledger events — runs by role, execution-role, gate, and status, evidence coverage, and a malformed-line count. scripts/check-work-items-state.* --root . --max-age-days <N> additionally reports (informational, never a failure) active items older than N days plus any open Depends-on blockers or dangling dependency targets.

The runtime helper surface is installed with production Codex and Claude packs as well: Codex gets the scripts under ~/.codex/skills/lead/scripts/ or <repo>/.agents/skills/lead/scripts/, while Claude Code gets them under ~/.claude/agents/scripts/ or <repo>/.claude/agents/scripts/. See docs/work-item-execution-tracking.md for the operator runbook. To group several work-items under one goal or milestone, see docs/epics.md (the epic -> work-item -> phase hierarchy). For durable cross-item architecture decisions see docs/decisions.md (the ADR registry), and for standing cross-work-item dependencies see docs/dependencies.md (Depends-on edges + blocked/ready derivation). For the in-repo delivery-lessons registry see docs/lessons.md (capture lessons learned so they survive a work-item's archival), and for the DoR/DoD vocabulary map onto existing admission and close gates see docs/definition-of-ready-done.md.

For release-relevant tracked changes, update RELEASE_NOTES.md in the same change before publication and explain the practical effect of the change, not just its title. Keep release notes in reverse-chronological ## YYYY-MM-DD sections instead of one long-lived ## Unreleased bucket, and run the repo-local gate before publication:

bash scripts/check-publication-gate.sh

python .\scripts\check-publication-gate.py

License

This repository is licensed under the Mozilla Public License 2.0. See LICENSE.

Terms and Abbreviations

• AGENTS.md: agent governance entrypoint assembled or read by Codex-compatible runtimes.
• agent-run-ledger.*: helper script family that initializes legacy work-item ledger files and appends validated agent-runs.jsonl events.
• agents-mode: Orchestrarium operator configuration overlay for delegation, provider routing, MCP use, and parallelism.
• agent-runs.jsonl: JSONL execution ledger stored beside status.md for machine-readable work-item state.
• check-work-items-state.*: helper script family that checks every active work item under a repository root.
• reserve: symbolic supplemental read-only candidate for advisory/review lanes; it runs after primary claude and codex and is not a worker or editing path.
• reserveResolver: scalar agents-mode key that binds reserve to claude-sonnet, claude-wrapper, a wrapper:<command> resolver, or disabled.
• CLI: Command-Line Interface, a terminal command surface such as codex, claude, gemini, or qwen.
• Codex: the OpenAI Codex runtime and production provider line in this repository.
• Claude Code: Anthropic's Claude Code runtime and production provider line in this repository.
• externalProvider: auto: Orchestrarium routing mode that uses only production-recommended providers, currently Codex and Claude.
• externalPriorityProfile: the active named provider-order profile used when externalProvider: auto.
• externalPriorityProfiles: the map of named routing profiles to lane-specific provider priority lists.
• evidence: concrete verification data such as a command result, artifact path, review result, log summary, or observed output supporting a gate.
• Gemini: deprecated Google Gemini CLI full-mirror example retained pending the npm-skillpack decision.
• JSON: JavaScript Object Notation; structured data format used here for machine-readable contract files.
• JSONL: JSON Lines; one JSON object per line, used here for append-only execution events.
• ledger: append-only record of agent runs, gates, artifacts, and evidence for a work item.
• MCP: Model Context Protocol; a protocol for exposing tools and resources to agent runtimes.
• power-mode: init-time preset for hardest tasks where maximum useful result matters more than latency; starts from the quality-first provider-order profile.
• quality-first: production provider-order profile that biases near-tie advisory, source-bound, and review lanes toward Codex while preserving Claude-first lanes where the benchmark evidence gives Claude a clearer compact or visual-worker edge.
• Qwen: deprecated Qwen full-mirror example retained pending the npm-skillpack decision.
• runtime: installed provider-facing files and directories used by an agent tool outside the source tree.
• schema: structured contract describing allowed keys, values, defaults, provider sets, and routing shapes.
• status.md: human-readable recovery summary for the active work item.
• WEAK MODEL / NOT RECOMMENDED: repository classification for example-only providers that must stay out of production defaults and auto routing.