Kanshō/Orchestrator delegation card

Orchestrator delegation card

The operator-facing record of how an orchestrator broke down a mission and where it sent the work. Expandable per-step chain with status, instruction, result, and spend.

Included in the single kansho full pack. Components are not offered as separate installs.

In-flight delegation chain

Orchestrator delegationOD-14· M-201414:01
Plan & dispatchclaude-opus-4-7

Compact the audit log into hourly chunks in staging, verify against source row counts, and then ask the operator before cutting over to production.

ContractNo event drop. Drift threshold 0.5%. Operator approval before production write.

  1. 1
    postgres.executeSuccess

    Acquire advisory lock on audit.logs

    → lock_id=8841 acquired in 0.1s

    0.1s120
  2. 2
    agent.audit-writerSuccess

    Sketch hourly chunk window proposal

    → Window: 60m, max_payload=4096. Approved against staging schema.

    4.2s2.8k$0.04
  3. 3
    postgres.executeRunning

    Backfill hourly aggregates in staging

    → 144,019 / 145,225 source rows so far

    running 1m12s
  4. 4
    human.operatorPending

    Approve production cut-over once drift < 0.5%

64k$2.18

Error & recovery

Static preview: Retry requires a host callback; settled steps stay actionless
Orchestrator delegationOD-15· M-201515:20
Plan & dispatchclaude-opus-4-7

Reindex the invoice embeddings and verify recall against the golden set.

  1. 1
    vault.readSuccess

    Fetch the embedding model key

    0.2s
  2. 2
    agent.embedderFailed

    Re-embed 4,210 invoices

    → Out of memory at item 4,210

    1m 22s

Closed delegation

Orchestrator delegationOD-12· M-201213:31
Plan & dispatchclaude-opus-4-7

Rotate every sandbox secret older than 30 days and confirm new credentials authenticate.

  1. 1
    vault.listSuccess

    List eligible secrets

    0.4s
  2. 2
    vault.rotateSuccess

    Rotate 14 secrets

    12.8s
  3. 3
    vault.verifySuccess

    Authenticate against new credentials

    2.1s
  4. 4
    agent.audit-writerSuccess

    Append rotation receipt to ledger

    1.8s720$0.02
18k$0.06

Included components

This page is the canonical destination for these components. All ship in the single Kansho pack.

Orchestrator delegation card

components/control-plane/orchestrator-delegation-card.tsx

Component documentation

Orchestrator delegation card

components/control-plane/orchestrator-delegation-card.tsx

Purpose

Explains an orchestrator plan and its ordered delegated steps with results and spend.

Appropriate use

Use in a run timeline when operators need to inspect delegation contracts and recover failed steps.

Example

components/control-plane/orchestrator-delegation-card.tsx has a representative live example in the "In-flight delegation chain" section on /components/orchestrator-delegation.

States

Steps use the shared status vocabulary and may include result, duration, tokens, and cost; the chain may start open or closed and failed steps may expose Retry.

API and props

OrchestratorDelegationCard accepts id, orchestrator, plan, steps, contract, defaultOpen, onRetryStep, mission, tokens, cost, startedAt, and className.

Dependencies

Direct imports are React, Lucide icons, AgentDot, StatusPill, CostChip, Disclosure, and cn.

Accessibility

The delegation chain is a keyboard disclosure, each step has an ordered number and labelled status, and Retry renders only with a callback.

Limitations

It does not delegate, retry, calculate settlement, validate step order, or report pending/error results after callbacks.

Source

Source: components/control-plane/orchestrator-delegation-card.tsx.

Full pack

components/control-plane/orchestrator-delegation-card.tsx is documented at /components/orchestrator-delegation and installs only through the single Kansho full pack; no individual component install is offered.