summon

## Table of Contents - [Overview](#overview) - [When To Use](#when-to-use) - [When NOT To Use](#when-not-to-use) - [Orchestration Loop](#orchestration-loop) - [Pipeline-to-Skill Mapping](#pipeline-to-skill-mapping) - [Context Overflow Protocol](#context-overflow-protocol) - [Token Budget Protocol](#token-budget-protocol) - [Failure Handling](#failure-handling) - [Module Reference](#module-reference) # Summon ## Overview Summon is the egregore orchestration loop. It reads the manifest (`.egregore/manifest.json`), selects the next active work item, maps the current pipeline step to a specialist skill, and invokes that skill. After each step it advances the pipeline, checks context and token budgets, and repeats until all items are completed or the budget is exhausted. The orchestrator never re-implements phase logic. Each pipeline step delegates to an existing skill via `Skill()` calls. Summon only manages state transitions, retries, and budget guards. ## When To Use - Processing one or more work items through the full intake-build-quality-ship pipeline. - Resuming an interrupted egregore session (manifest already exists with active items). - Running autonomously under a watchdog that relaunches on exit. ## When NOT To Use - Running a single skill in isolation (call the skill directly instead). - Exploratory work where the pipeline does not apply. - When human review is needed before every step (use manual skill invocations). ## Launching the Orchestrator *...