dispatch-spec

Validate dispatch documents against the Arcanum route graph schema.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill dispatch-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch-spec
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/dispatch-spec
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill dispatch-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jsonschema, pyyaml, and includes scripts (resource) components.

What problem does it solve?

The Dispatch Spec defines a governance contract that ensures Arcanum route graphs are explicit, validated, and observable, preventing misconfigurations and unsafe handoffs.

Core Features & Use Cases

  • Formal schema and rules for validating dispatch documents describing how sigils and spells are chained, gated, observed, and promoted.
  • Supports technique overlays, boundary/evidence contracts, and subagent strategies to coordinate complex routings across teams.
  • Enables reproducible, auditable route planning with clear inputs, outputs, and lifecycle ownership.

Quick Start

Create a sample dispatch.json describing a route and run the validator to verify governance compliance.

Frequently Asked Questions about dispatch-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a dispatch document for Arcanum route graphs?

Validate a dispatch document by running the validator against your route graph specification to enforce required fields, technique usage, boundary/evidence constraints, and promotion guardrails per the dispatch schema.

What is governed validation for route graphs with steps, gates, and observability?

Governed validation ensures route graphs are explicit, validated, and observable by defining a formal schema and rules that prevent misconfigurations and unsafe handoffs across chained sigils and spells.

Can I use jsonschema and pyyaml to validate dispatch documents with subagent strategies?

Yes, the validator relies on jsonschema and pyyaml dependencies to check dispatch documents that include subagent strategies, technique overlays, and boundary/evidence contracts for complex routings.

How do I enforce promotion guardrails and boundary evidence constraints in a dispatch schema?

Enforce promotion guardrails and boundary_evidence constraints by applying the validator to your dispatch document, which checks these specific rules alongside required fields and technique usage.

When do I need to validate dispatch documents with technique overlays and observability contracts?

You need dispatch document validation when coordinating complex routings across teams, ensuring reproducible, auditable route planning with clear inputs, outputs, and lifecycle ownership.

What are the limitations of validating dispatch documents for Arcanum routes?

The validator is limited to checking dispatch documents against the schema rules; it verifies governance compliance for required fields, technique usage, and boundary constraints but does not execute the route graph itself.