RRunOnProof
Capability · Company Passport

Reusable state without reusable overclaiming.

A Passport is issued only from persisted, entity-bound UK executions whose evidence is current, healthy and replay-matching. Every update creates a new immutable version.

Admission policy

Committed decisions only

The service replays the stored semantic result, verifies company-number binding, validity, evidence references, source health and supported claim scope. Failed admission produces no Passport and no economic mutation.

Lifecycle

  1. 01
    Create

    Bind committed execution IDs to one GB company number and stable idempotency key.

  2. 02
    Refresh

    Issue a superseding version from a fresh admitted execution set.

  3. 03
    Replay

    Verify an immutable version without live source calls, signing or charging.

  4. 04
    Invalidate

    Preserve an immutable revocation version and prevent active use.

Not a seal of trust.

A Passport does not prove bank ownership, invoice authenticity, universal solvency, good standing, complete beneficial ownership or perpetual authorization.