Behind the builder / 16 October 2026

A passing test needs a place to stop.

Local R4 tests exercised receipts, privacy checks and replay rejection. The next step still required explicit permission and a recoverable native trial.

By Alex MelczerPublished 1 min read

The useful part of a small test

The 16 October report recorded 269 passing checks across selected R4 components and five passing cases in an isolated end-to-end broker test. Receipts, privacy checks and rejection of repeated requests were part of that work. The existing R3 service was left untouched.

That is progress worth keeping. It gives the next experiment a more precise starting point: we can name what the local test exercised, rather than treating a successful run as evidence for the whole machine.

The next result has to cross a different boundary

A persistent native trial still needed its owner, permission and recovery conditions. The local result could not supply those things for itself. Nor could an archive inventory prove that a restore would work.

The practical lesson was to make the next trial small enough to inspect: one harmless operation, its receipt, an interruption, and a check that restarting does not repeat the effect. The test suite had advanced. Native acceptance remained open.

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.