Duk

It asks first.

An open-source agent, being built at Zyrn, that works on a firm’s operating core — brainstorming, drafting and arguing real improvements with the people who actually run it. One rule underneath all of it: no answer until the question is the right one.

IN DEVELOPMENT LICENCE OPEN SOURCE BUILT BY ZYRN RUNS ON YOUR OWN INFRASTRUCTURE
01

The name

Programmers have kept a rubber duck on the desk for forty years. You explain the broken code to it, out loud, line by line — and somewhere in the explanation you find the bug. The duck never says anything. It works because being made to articulate a thing is most of understanding it.

Duk is that, with the duck able to ask back.

Almost everything in this category is built to produce. Give it a prompt, receive a strategy, a plan, a deck. That is the easy half, and it is usually the wrong half — because the prompt already contains the mistake, and a fluent answer to the wrong question is worse than no answer at all. It is just harder to argue with.

DUK — /dʌk/

The oldest debugging tool there is, given the ability to ask back.

00 — THE STATEMENT 22 / 22 LIVE QUESTIONS 00 000%
DUKASKS

Our sales team keeps missing quota.

Twenty-two candidate causes, and everyone in the room is holding a different one. A tool that answers this question now is guessing in a confident voice.

An illustration of Duk’s intended method: candidate causes are eliminated by successive questions until one structural constraint remains.

03

What it is being built to do

  1. 01

    Ask

    Read the business you describe and ask the next question that would actually narrow it — not the next one on a checklist. Most of the value is in the first four questions, and almost nobody asks them.

  2. 02

    Argue

    Hold a position when the evidence supports it, and say so when it does not. A tool that agrees with everything you propose is a mirror with a subscription attached.

  3. 03

    Draft

    Write the actual artefact — the operating model, the role definition, the policy, the page — in your formats and your voice, at a standard you would send rather than one you would rewrite.

  4. 04

    Build

    Produce the thing, not a description of the thing. If it proposes a page, it ships the page. This is the line most of the category does not cross, and it is the one that decides whether anything changes on Monday.

  5. 05

    Measure

    Name the number a change should move before the change is made, so it can be wrong out loud. An agent that cannot be caught being wrong cannot be trusted when it is right.

  6. 06

    Remember

    Carry the firm’s own decisions forward — what was tried, what it cost, who owns it now — so the fourth quarter stops re-litigating the first.

04

What it will refuse to do

It will
  • Say “I do not know” — and then say what would settle it
  • Show the reasoning that produced a recommendation, in full
  • Run entirely on infrastructure you control
  • Be forked, audited, and disagreed with
It will not
  • Generate a strategy from a one-line prompt
  • Invent a number because a slide needed one
  • Hold your data as the price of the answer
  • Let you treat a structural problem as a tooling problem
05

Why it is open

The same rule that governs every brand kit we hand over: it is the client’s from the day it ships, and if it needs us in order to keep working, it was not finished. A firm’s operating core is the last thing that should be rented.

There is a second reason, and it is the harder one. Duk’s job is to have opinions about where authority sits inside your company. You cannot take that advice from a black box. If the reasoning is not inspectable, the recommendation is just a confident stranger telling you to reorganise.

So: readable source, self-hosted, forkable. If we disappear, it keeps working. That is not generosity — it is the only version of this that a serious firm should agree to run.

THE RULE, RESTATED

If it needs us in order to keep working, it is not finished.

Where that rule comes from
06

Where it actually is

Duk is not released. There is no public build, no waiting list counter, and no launch date on this page — if one appears here later it will be because it is true, not because the page needed one.

What exists is the part that matters and cannot be shortcut: the method. Four service lines, run by hand, repeatedly, on real firms. Duk is that method being encoded — which is why it starts by asking rather than by generating, and why the answer it reaches for is usually about authority rather than about tools.

It is being built in the open. When there is something to run, it will be here and it will be forkable on day one.

Ask about early access The AI adoption line