Skip to main content
API reference sections

Schema

HandoverState

Where a controller handover stands.

Release, not preemption: nothing takes a lease from its holder. The holder is asked, releases at a boundary of its choosing, the requester attaches, and gives it back the same way. Each step is a state a reader can see and an event a subscriber receives.

Type "idle" or "requested" or "released" or "taken" or "returned"

Shape

One of 5 shapes:

  1. Variant 1

    "idle"

  2. Variant 2

    Someone asked while a controller was held; the holder has been told.

    "requested"

  3. Variant 3

    The holder released its lease for the handover; the next attach takes it.

    "released"

  4. Variant 4

    The lease was granted after a release: a person holds the session.

    "taken"

  5. Variant 5

    The person gave the lease back, or lost it; the next attach reclaims.

    "returned"

Example
"idle"

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Generated from contract version 1. Last updated .

Privacy choices

Choose which optional tools Koru may use on this site. Your choice is saved in a cookie in this browser for 12 months. Privacy policy

Privacy choices

Keep you signed in, protect forms and remember your language and this choice.

Always on

PostHog and Google Analytics 4 measure page views and actions such as downloads, using cookies or local storage.

PostHog records how pages are used, with form inputs masked and private pages excluded. Needs Analytics.

Ahrefs Web Analytics measures visits and where they come from, and Google Ads measures whether our ads led to a visit or download.