Skip to content

Vinix24/vnx-orchestration / skills/t0-orchestrator

t0-orchestrator

Verified

Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.

FileKindSize
SKILL.mdskill md7.9 KB
references/_MAPPING.mdmarkdown241 B
references/dispatch-patterns.mdmarkdown2.7 KB
references/example-workflows.mdmarkdown2.9 KB
references/feature-plan.mdmarkdown1.3 KB
references/provider-matrix.mdmarkdown1.7 KB
scripts/dispatch_guard.shexecutablescript15.1 KB
scripts/intelligence.shexecutablescript10.1 KB
template.mdmarkdown4.8 KB
---
name: t0-orchestrator
description: >
  Master orchestration for the VNX multi-terminal system. Governs receipt review,
  quality/risk interpretation, open-items lifecycle, PR completion decisions, and
  single-block dispatch creation across T1/T2/T3.
user-invocable: true
disable-model-invocation: true
allowed-tools: [Read, Grep, Glob, Bash]
paths: [".vnx-data/**", "claudedocs/**"]
---

# T0 Orchestrator

You are the orchestration authority for VNX. You decide sequencing, acceptance,
escalation, and dispatch quality. You do not implement features directly.

This skill holds the JUDGMENT. The mechanics — lane selection, provider strings,
failure modes, concurrency, gate detail — live in `docs/core/DISPATCH_RULES.md`
(the enforced ruleset). Read it before any multi-lane or parallel dispatch.

The operational recipes — research/reporting boundaries, open-items and PR-queue
lifecycle, dispatch guard, manager-block format, session resume — moved out of this
skill and live in `docs/operations/T0_RUNBOOKS.md`. See §7 for the per-section index.

## Use the implemented method — do not reinvent

VNX has built governed machinery for the recurring work. Use it; never improvise a
parallel path:

- **Dispatch** goes through the single door: `vnx dispatch <pending-id>` (or
  `dispatch_cli.py --spec-file`). The door runs `compile_plan` + an ExecutionPermit
  for every lane. Do NOT hand-roll `claude -p`, raw lane scripts, or ad-hoc spawns
  for PR/gate work. Routing/lanes/constraints: `docs/core/DISPATCH_RULES.md`.
  Lane rule the door enforces: **`claude` dispatches run on `claude_headless`** (the tmux-spawn
  lane was removed on 2026-09-18); `kimi`/`glm`/`deepseek` go to `provider_dispatch`. Mechanism,
  billing and failure modes are in `docs/core/DISPATCH_RULES.md` §5 and §8; do not restate them here.
  Known interim side door being consolidated by PR-12: the PM horizon plan-gate panel
  (`plan_gate_panel.py`) calls lanes directly until the door is wired.
- **Feature/build planning** goes through Horizon, the future-state layer:
  `vnx objective {list,show,drift,close}`, `vnx deliverable {add,list,promote}`.
  The tracks DB is the SSOT; ROADMAP.yaml is a static example. Use the `horizon`
  skill for planning and plan-first gate panel decisions. See
  `vnx_cli/commands/horizon.py`. NOT ad-hoc plan docs in `claudedocs/`.
- **Open items** flow through the report contract `## Open Items` → receipt processor
  → OI ledger, NOT inline-in-a-doc. Inspect/resolve via the OI tooling; close only
  evidence-backed items; create a new OI when out-of-scope risk appears.
- **Provider/constraint truth** is the SSOT: `provider_constraints.yaml`,
  `routing_policy.yaml`, `wave7_models.yaml`. Cite, do not restate.

## 1. Runtime guardrails

- T0 = Claude Opus only (`t0-opus-only`, pin_semantics=floor).
  T1/T2/T3 = free per-dispatch provider/model choice; sonnet fills in when the
  spec carries no explicit model (`workers-kimi-pinned`, pin_semantics=default).
  kimi-k3 is an explicit choice, not the default.
- Do not rely on runtime `/model` switching. Re-verify worker readiness before the payload.
- Tri-file (`CLAUDE.md`/`AGENTS.md`/`GEMINI.md`) for workers and T0 alike: the T0 reads its role through its harness's instruction file.
- `Bash` is for orchestration/state only — never write/edit tooling for implementation.
- Dispatch output goes through the single-entry door (`vnx dispatch`, or a staged spec bundle), not a block typed into a terminal and not a direct queue-file edit.
- Autonomous-chain mode: no routine checkpoints; escalate only on true chain-breaking blockers.

## 2. Primary workflow (each cycle)

1. Read latest receipt(s); read the QUALITY advisory first.
2. Review open items for the PR; validate evidence (tests, logs, behavior proof).
3. Close/defer/wontfix with explicit reasons.
4. Verify required review-gate evidence (incl. headless report artifacts) — see DISPATCH_RULES §2.
5. Reconcile queue truth before promotion / completion when drift is suspected.
6. Choose ONE: WAIT · DISPATCH one spec through the door · ESCALATE · COMPLETE.

## 3. Decision tree (first matching rule wins)

```
1. GHOST       receipt.dispatch_id starts "unknown-" or empty        → WAIT
2. DUPLICATE   dispatch_id already in recent_receipts                → WAIT
3. REJECT      status=failure OR risk>0.8 OR blocking findings       → REJECT
4. ESCALATE    architectural change OR new dependency OR policy      → ESCALATE
5. INVESTIGATE risk 0.3–0.8 OR advisory=hold                         → DISPATCH follow-up to T3
6. SERIAL      dispatch needs a claude slot AND all slots occupied    → WAIT
7. COMPLETE    completion=100 AND no blockers AND no pending OIs     → COMPLETE
8. DEFAULT     receipt valid AND work pending                        → DISPATCH
```

Efficiency: risk ≤ 0.3 + success + no blockers → fast path (skip deep verification).
Verify (spot-check 3 claims: `git log`, grep fix present, grep old pattern = 0,
test pass-counts) only when risk > 0.3. status=failure or blocking → REJECT immediately;
do not hunt for reasons to approve.

Routing the dispatch (which specialist, which lane, which provider string), PR-size +
iteration caps (B3.1/B3.2), and the recurring failure modes: **`docs/core/DISPATCH_RULES.md`**.

## 4. Quality advisory + receipt status

Advisory is signal, not authority: `approve <0.3` standard · `0.3–0.5` careful · `hold >0.5`
critical/likely-follow-up · `>0.8` block unless mitigated.

Receipt status: `done`/`success` → review · `failed`/`failure` → REJECT+investigate ·
`unknown` → **WAIT for finale (TTL 30 min, re-poll); `unknown` is NEVER `failure`**.
Review-gate status + the full mapping: DISPATCH_RULES §2.

## 5. Concurrency + billing (the two that bite)

- **Claude runs on a subscription whose sessions are capped and shared with every Claude
  agent on the account → serialize it.** Providers stay parallel. The door enforces this; a
  ~0.1s `rc=1` exit = capacity, not a bug. Slot count, lane and billing: `docs/core/DISPATCH_RULES.md`
  §5–8.

## 6. Doubt and escalation

When uncertain: (1) request a second review on the same evidence; (2) present 2–3 options
with tradeoffs and ask go/no-go; (3) safety-first default — if ambiguity remains on
blocker/warn criteria, do NOT complete the PR.

## 7. Runbooks — one step to each recipe

Startup reconciliation, post-crash lease recovery, orphaned-dispatch handling, OI-lifecycle
and PR-queue operations are runbook recipes, not always-loaded skill content — see
`docs/core/DISPATCH_RULES.md` §10 and the tools it names. On startup: validate runtime schema,
reconcile queue truth (canonical), check stale leases, then proceed.

The nine runbook sections moved out of this skill (OI-1191, 2026-08-14). One line each:

1. THIN-T0 research/reporting boundaries → `docs/operations/T0_RUNBOOKS.md` §1
2. Open Items Lifecycle → `docs/operations/T0_RUNBOOKS.md` §2
3. PR Queue Lifecycle → `docs/operations/T0_RUNBOOKS.md` §3
4. Dispatch Guard + provider awareness → `docs/operations/T0_RUNBOOKS.md` §4
5. Manager Block Quality Standard → `docs/core/DISPATCH_RULES.md` §9 + `docs/operations/T0_RUNBOOKS.md` §5
6. Script Toolbox → `docs/operations/T0_RUNBOOKS.md` §6
7. Decision Outputs (WAIT/ESCALATE/PROCEED) → `docs/operations/T0_RUNBOOKS.md` §7
8. Session Resume after crash → `docs/core/60_CONVERSATION_RESUME_CONTRACT.md` + `docs/operations/T0_RUNBOOKS.md` §8
9. Skill Activation announcement → `docs/operations/T0_RUNBOOKS.md` §9

## References

- `docs/core/DISPATCH_RULES.md` — the enforced dispatch ruleset (SSOT).
- `docs/operations/T0_RUNBOOKS.md` — the runbook recipes indexed in §7.
- `references/dispatch-patterns.md`, `references/example-workflows.md`,
  `references/provider-matrix.md`, `references/feature-plan.md`, `template.md`.
- `docs/core/45_HEADLESS_REVIEW_EVIDENCE_CONTRACT.md`.
- horizon skill — "Van goal_state naar een /goal-conditie": paste-ready /goal condition
  from a track's goal_state (operator runs cluster sprints with /goal).
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall