Ducens SHEET 04 / 08
Ducens · Sheet 04 / 08 Pillar · Loop

Set the bar. The loop runs until the work meets it.

It looks like a workflow tool and it is the opposite. A workflow runs once through its branches and ends. A loop runs a cycle against a quality bar and repeats until the bar is met. The exit condition is the whole primitive; everything else is plumbing.

And because a green tick is not a record, every round writes a Trust Receipt: what ran, what it touched, how long it took, and what it was refused.

Run one here

04·B

This one builds a change, scores it against a bar of 90, and sends it back every time it falls short. Watch the same two steps come round again. It stops and asks you before it commits anything, and refusing is a normal ending that gets recorded too.

RUN-0042 · SUPERVISED
THE BARNamed before the run starts, not argued about after. Here it is a review score of 90.
WHAT RANEvery round, every step, with its tool and its mode. Nothing is summarised away.
WHAT IT TOUCHEDFiles, mail, calendar, the repo. If it is not on the receipt, it was not touched.
WHAT IT ASKEDCommitting crosses a line, so it waits for you. Deny by default.
TRUST RECEIPT · BUILD AND REVIEW RUN-0042 · 2026-08-09
READY. NOTHING HAS RUN. NOTHING WAS TOUCHED.
EXIT CONDITION SET BEFORE THE RUN: SCORE 90.
SPECIMEN RUN · THE SHAPE IS REAL, THE JOB IS AN EXAMPLE MS COLUMN TABULAR

Two ways to run it

04·C
INSIDE DUCENS

Run it here, on your own API keys. Ducens never bundles compute and never sits between you and your provider bill.

IN YOUR TERMINAL

Export the compiled bundle — no credentials inside it — and run it in your own terminal on your own subscription. Your terminal, your login. Ducens observes and writes the receipt.

THE BUNDLE CARRIES THE LOOP, NEVER YOUR KEYS · YOUR SUBSCRIPTION STAYS YOURS AND STAYS OUTSIDE DUCENS

Loops ship with receipts on, always.

Join the waitlist
End of sheet 04 Next: The Build →