Delegation context and evidence interpretation
A specialist starts with a fresh context. A useful handoff identifies the bounded
question, exact target and permitted actions, acceptance observable, environment,
relevant evidence excerpts and paths, known failed approaches, remaining uncertainty
and budget. Credential references should identify protected artifacts, not repeat
secrets. The live task schema supplies actual field names and available specialists;
examples from another installation do not override it.
Context quality
Distinguish direct observations, inferred mechanisms and untested assumptions. For a
proof question, include a competing benign explanation and discriminating control.
A code tree, existing reproducer or prior capture may supply enough context without
another collection pass. Include exact versions and session prerequisites where
behavior depends on them. Summarize large outputs without dropping conditions that
would change the conclusion; keep raw artifact links for independent assessment.
Result interpretation
An agent return is testimony to inspect, not proof that its acceptance criterion
was met. Look for the actual observable and whether the evidence belongs to the
claimed target, identity and run. An empty output, environment fault, exhausted
budget, refuted hypothesis and meaningful negative result are different outcomes.
Repeated failures with the same mechanism do not justify confidence inflation.
Preserve uncertainty and provenance when revising a conclusion.
Startup, dispatch ordering, execution-state mutation, quality gates and engagement
close are defined by the selected workflow and injected runtime contracts. This
reference does not define another plan, a mandatory role chain or a report sequence.
1---2name: orchestration3description: "Decepticon orchestrator patterns — delegation, state management, adaptive re-planning, context handoff protocols."4allowed-tools: Read5metadata:6 source: https://skillmd.com/skills/purpleailab/orchestration7 skillogy:8 version: 19 subdomain: orchestration10 when_to_use: "delegate, orchestrate, next objective, blocked, re-plan, hand off, engagement state, status update"11 tags: orchestration, delegation, state-management, re-planning, context-handoff12 upstream_ref: "Decepticon orchestrator delegation / re-planning patterns — multi-agent control plane, no direct attack technique"13---1415# Delegation context and evidence interpretation1617A specialist starts with a fresh context. A useful handoff identifies the bounded18question, exact target and permitted actions, acceptance observable, environment,19relevant evidence excerpts and paths, known failed approaches, remaining uncertainty20and budget. Credential references should identify protected artifacts, not repeat21secrets. The live task schema supplies actual field names and available specialists;22examples from another installation do not override it.2324## Context quality2526Distinguish direct observations, inferred mechanisms and untested assumptions. For a27proof question, include a competing benign explanation and discriminating control.28A code tree, existing reproducer or prior capture may supply enough context without29another collection pass. Include exact versions and session prerequisites where30behavior depends on them. Summarize large outputs without dropping conditions that31would change the conclusion; keep raw artifact links for independent assessment.3233## Result interpretation3435An agent return is testimony to inspect, not proof that its acceptance criterion36was met. Look for the actual observable and whether the evidence belongs to the37claimed target, identity and run. An empty output, environment fault, exhausted38budget, refuted hypothesis and meaningful negative result are different outcomes.39Repeated failures with the same mechanism do not justify confidence inflation.40Preserve uncertainty and provenance when revising a conclusion.4142Startup, dispatch ordering, execution-state mutation, quality gates and engagement43close are defined by the selected workflow and injected runtime contracts. This44reference does not define another plan, a mandatory role chain or a report sequence.