---
source_hash: cfb7604dcfdb190e32e5650acf85733f8a885cd2fd86416085c25e5bb4058d9a
post: /posts/dispatch/context-pack-dispatch
shape: doctrinal
---

# Context Pack: Context Pack dispatch

Agent reference for the rewritten essay. Quoted excerpts are verbatim; component details below are identified separately. Historical subscription use is not a promise about current billing or unlimited usage.

## Verbatim excerpts

> Keep those verbatim. Summarise the bulk and leave references the worker can fetch when it needs more.

> I used the tool to ship its own repository by pointing it at itself.

> The count is a clue to inspect, not the evidence that finishes the job.

## Contract and reported build

Keep IDs, paths, values and exact constraint lines in one text file; condense the surrounding material and retain source references. The reported workflow budgets half the receiving model's context window for the pack, leaving room for the task, re-fetches and result. Half is a budget, not a target to fill.

A manager chooses the cheapest Claude tier capable of the job. Small tasks go direct; larger work fans out under a cheaper large-context model that reassembles results. The July 2026 setup used subscription access instead of metered API calls. Do not treat that account as current pricing or an unlimited entitlement.

The tool helped ship its own repository and reported `12 ok`. Ari diffed every file before trusting the result because an earlier workflow had reported success without running the work. Verify the artefact and behaviour, not just the tally.

## Retained component contracts

The anatomy component presents five sections in order: `Decode header`, `Task`, `Needles`, `Gist bulk`, `File index`. Its filename is `context-pack.md`. Task carries the specification and done condition; file index supplies locations for exact re-fetching.

The extractor demo recognises hex strings of at least eight characters, paths of at least two segments, numbers of at least four digits, and lines with both a negation trigger and a load-bearing token. Read the component for exact regex; this heuristic does not prove it finds every important constraint. Example strings include `7f3a9c2e1b8d`, `/etc/app/config.yaml`, port `8080`, and a no-remote-push instruction. These are demo data, not operational instructions for a reader's environment.

The historical routing illustration is S → haiku/low, M → sonnet/medium, L → fable/high, XL → fable/high with fan-out. Its retry ladder is haiku → sonnet → opus. Treat the illustration as this workflow's policy, not a universal routing rule.

## File index

- Essay: `content/posts/dispatch/context-pack-dispatch.mdx`.
- Anatomy: `apps/web/components/blocks/ContextPackAnatomy.tsx`.
- Exact extractor: `apps/web/components/blocks/NeedleExtractorFidget.tsx`.
- Routing: `apps/web/components/blocks/RoutingMap.tsx`.
- [MIT-licensed Build repository](https://github.com/PUSHINGSQUARES/Build).
- [The /swarm skill archive](/downloads/swarm-skill.zip).
