/ultracode

Where /goal is one model working through a task, /ultracode splits the work across several that check each other before anything reaches you.

Type it the same way

/ultracode audit this repository for authentication bugs

Fan-out

It fans out

The task is decomposed and the parts run in parallel rather than one after another. Breadth costs wall-clock time once instead of once per part.

One after another

In parallel

Wall-clock

Both bands carry the same parts and the same work. Only the arrangement differs.

Refutation

It verifies adversarially

A claim from one model is handed to others whose job is to refute it. What survives is reported. What does not is dropped silently, rather than shown to you as a maybe.

Refutation

The claim holds

Reported

The claim falls

You never see it

Two ends for the same claim. The empty half of the lower track is the point: nothing arrives there, and nothing arrives flagged as unsure either.

Cost

It costs more

Several models on one task is several bills. Use it when being wrong is expensive, and /goal the rest of the time.

/ultracode: Audits Migrations Reviews before a release
/goal: The rest of the time

Ceilings

The ceilings still apply

It obeys the same ceilings as any other long-running job: spend limits, the budget governor, and whatever cap you set when you started it.

Every lane

One bar, drawn across every lane at once. Fanning out buys no exemption from it.

It appears under Jobs and keeps running with the browser closed.

Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Legal & privacy · Home