POCKATE ARBITER · CONTROL

Keep agents from working over each other.

Coordinate shared resources when more than one agent needs them.

Experimental

Implemented foundations. Independent release work continues.

Illustrative mechanism. The diagram describes the product’s role, not a live execution.

HOW IT WORKS

A focused role.
A clear boundary.

Prevent two agents from writing the same live resource or racing a native application.

Agent A

Resource

Agent B

Turn-taking

Coordination is separate from permission. Full atomic fencing and durable queue integration remain open.

PRODUCT DEVELOPMENT

What’s here.
What comes next.

BUILT SO FAR

The current foundation

Resource leases, expiry, waiting queues and a local coordination service.
Routing and orchestration helpers used by the host.

COMING NEXT

The next useful step

Integrated durable waiting and resource-side fencing.
Visible contention and safe preemption in Companion.

Plans describe direction, not delivery dates. Verified support and release maturity vary by product.

PART OF POCKATE

Independent purpose.
Shared foundations.

Pockate products are designed for independent adoption and composition. Companion connects these foundations to a local computer; authority stays with its enforcing host.

See Companion Explore the suite

Follow Arbiter
from foundation to field.

Get product and research updates from Pockate Labs.

Get Pockate updates