Viktor dispatch — token-lean protocol

Viktor dispatch — token-lean protocol

Updated 2026-09-16: apply Token efficiency. Model examples below are historical role illustrations, not verified current pricing or availability. Choose supported models using current telemetry and task quality.

Subordinate to the master directive at https://hi.jbnx.io — on any conflict, the directive wins. This page governs HOW work is handed to Viktor on web chat and Slack; the directive governs the loop (claim → boot → work → verify once → usage → release).

Subordinate to hi.jbnx.io (re-fetch live per jbnx-ops). This skill governs HOW work is handed to Viktor, not WHAT the work is. Baseline failure this exists to prevent: 22:1 input:output on the bizplan task — Viktor re-read the world to write a page.

1. Pre-dispatch checklist (every task, no exceptions)

Answer all four before writing the directive:

1. Model — does this need judgment, or execution?
2. Fable 5: novel legal/financial reasoning, irreversible decisions, first-of-kind design.
3. Sonnet: PRs, SQL edits, table repairs, anything with a test or guard behind it.
4. Haiku 4.5: guards, formatting, verification passes, queue housekeeping.
5. Default is Sonnet. Fable requires a stated reason in the directive.
6. Slice — what is the MINIMUM context? Never "read the plan." Always the

substring(body_html from '<anchor>...') pattern, a single file path, or a line range. If the directive says "familiarize yourself with," rewrite it.

1. Surface — web chat or Slack?
2. Web is the default work surface. Pick the model in the model picker BEFORE the

first message; switching later doesn't refund what the big model already read. If the chat lives in a claude.ai Project, keep project knowledge lean — every file in it rides along on every turn of every chat in that project.

• Slack (@Claude) is for small, self-contained asks only: a status read, a single

guard check, a one-shot draft. Each thread reply re-ingests the whole thread, so a long Slack back-and-forth is the most expensive way to work. Anything over ~3 turns or needing repo/DB context moves to a fresh web chat with slices.

2. Directive format

Every Viktor directive contains, in order:

• Scope line — one sentence, includes the slug claim string.
• Context slices — exact queries/paths Viktor runs to load context. Nothing else is

in scope to read. Loading outside the slice list = defect, same class as silent $0.

• Anchors + guards — anchored replace() edits with assertions, per jbnx-ops. Guards

run on the cheap model.

• Token budget — set a task-sized soft cumulative input/output target including workers and review. Near it, checkpoint and reduce optional exploration; required checks and authorized completion remain necessary. Honor explicit hard caps.
• Done means — the live-URL or SQL assertion that ends the task.

3. Session hygiene

• Keep context relevant. Checkpoint at task boundaries. Decide whether to start fresh from remaining context, duplication and progress, not an input/output ratio alone. Runtime caching and compaction vary.
• Paste slices, not documents. Attaching a whole plan/export to a web chat puts it in

every subsequent turn. Paste the section, or give Viktor the SQL/path to fetch it once.

• Handover row, not chat memory. Next session boots from the handover + slices, never

from "read the previous conversation."

• Measure real waste. Track cumulative usage, cache effects where exposed, rework and outcomes. High input/output ratios can follow from concise responses; never pad output or abort solely for a ratio.
• No re-verification theater. One guard pass on the cheap model. Fable does not

re-read its own output to admire it.

4. Recording

Per hi.jbnx.io, usage is recorded on every ask. Add to the usage note: model used and why, and the in:out ratio. Review unexplained spend, duplicated work and unnecessary model escalation; record actual runtime models and measured rates, not assumed historical prices.

5. What Fable 5 is still for

Do not starve real judgment to save tokens. Lender-document claims, SDVOSB structure questions, anything on the CEO threshold list (legal_binding / irreversible / spend) — Fable, full context, no budget squeeze. The savings come from the other 90% of the queue.