POCKATE MANDATE · CONTROL

Delegate a task. Define the boundaries.

Make the difference between a request and permission explicit.

In development

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.

Describe and verify what a human delegated, including limits on onward delegation.

Human intent

Scope

Delegation

Recheck

A message, credential or discovered capability never grants unrestricted authority.

PRODUCT DEVELOPMENT

What’s here.
What comes next.

BUILT SO FAR

The current foundation

Signed delegation, identity and revocation primitives.
Scope checks used by the Atlas agent interface.

COMING NEXT

The next useful step

Consistent caller identity and delegation across execution paths.
Human signing and durable trust-anchor workflows.

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 Mandate
from foundation to field.

Get product and research updates from Pockate Labs.

Get Pockate updates