frameworkviktor · v41099:claude-chat-c1d32026-11-13served from databaseAll documents

Viktor dispatch — token-lean protocol

Viktor dispatch — token-lean protocol

North star: Hand work to Viktor with minimum context and the right model so tasks finish correctly without wasteful token spend. Hard gates (never bend): master directive hi.jbnx.io wins on conflict; Fable full context for legal/irreversible/spend items; usage recorded on every ask; verify against the live URL or SQL assertion; no secrets in directives Everything else is a default. Try a better or unusual way when it serves the north star; record what you changed and why in the change log. Change log: bottom of this page (who, when, why).

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).

This page 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; trivial one-liners can use a one-line answer to each)

Answer all four before writing the directive. Start with the Jev pick (per hi.jbnx.io/core: "Jev picked: skills …; frameworks …"); Jev's worker-fit pick overrides the model defaults below. Jev down: pick by hand, label it "picked by hand, Jev down", and continue:

  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.

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:

in scope to read. If the slice proves insufficient, read the minimum extra and log why in the usage note; unlogged wide loading is a defect, same class as silent $0.

run on the cheap model.

Example (shape only):

Scope: claim <slug> — fix the pricing typo.
Slices: SELECT substring(body_html from '<pricing>' for 800) FROM <table> WHERE id=<id>
Guard: anchored replace() asserts exactly 1 match (Haiku pass)
Budget: ~15k in / 2k out soft
Done: live URL shows the corrected text

3. Session hygiene

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

from "read the previous conversation."

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.

Change log

Every change to this framework: who, when, why. Source: agent_ops.catalog_changelog.

When (UTC)WhoVersionWhatWhy
2026-11-13 10:351099:claude-chat-c1d3v4Added Jev-pick-first step to the model checklistDirective v101 requires a Jev pick before any work; this page never mentioned it, so dispatches skipped Jev routing and worker fit.
2026-11-08 16:181099:claude-chat-c1d3v3Viktor dispatch — token-lean protocolOwner-requested north-star review 2026-11-08: north star + hard gates header, top fixes, non-safety rules loosened to defaults (details in the page change log)
2026-09-16 21:521099:codex-work-06adv2Viktor dispatch — token-lean protocolnot recorded (before change log started 2026-11-08)
2026-08-31 05:031099:claude-mobile-fab5v1Viktor dispatch — token-lean protocol (web + Slack)not recorded (before change log started 2026-11-08)