Behind the builder / 12 October 2026

Enrolled does not mean authorized.

R4’s next proof is an authorized native action. Identity enrollment and prepared components cannot substitute for a current execution grant.

By Alex MelczerPublished 1 min read

The key and the permission are different

The 12 October close returns to a small but decisive distinction: admitting a WorkMachine or mission object does not establish a currently authorized executed mission.

A key can identify an actor. A grant must still say what that actor may do, on which resource, within which limits. Keeping those facts separate is part of making autonomous work governable.

One reversible action is enough to start

The report retains the local R4.17 frontier and unresolved inherited findings. Its next technical step is a narrowly authorized native canary, rather than another declaration that all of R4 is finished.

A deliberately small reversible operation can answer several questions at once: does the right owner receive it, is the grant enforced, and can a reviewer reconstruct the result? The value comes from the evidence, not the scale of the action.

Leave room for the missing evidence

The close also reports unavailable Mac telemetry. That limits what the reporting can establish about local execution; it is not proof that no work occurred.

R3 remains live. R4 remains in development while the native route, recovery and acceptance gates are demonstrated. The distinction keeps the next milestone understandable: permission first, a bounded action next, then a result that can stand up to inspection.

Ask UBI

Understand UBIKITOS. Explore your workflow.

What would you like to understand?

Ask how it works, or bring an example from your business.

Explore an industry example

See how a proposed rule could work in your industry.