Chio/Docs
LOGIN · JOIN

chio partner

Add a partner from its partner card, which pins the partner's kernel key, and choose the transport the two kernels use.

Reference chio@5f63e6e

On this page

All command families · Global flags

chio partner

Add partners from their partner cards.

Command synopsistext
chio partner [OPTIONS] <COMMAND>
  • chio partner demo Run a demonstration partner on this machine, with its own kernel, keys, policy, and agents, and write its partner card.
  • chio partner add Add a partner from its partner card and pin its kernel key.
  • chio partner status Print the stored record for a partner: pinned kernel key, handshake schema, assurance tier against your floor, admitted capabilities, ladder manifest, and the key-rotation deadline.
  • chio partner handshake Run the kernel handshake with a partner now, re-verify its pinned key and ladder manifest, and renew the rotation deadline.

Example

Run a demonstration partner, then add its card over the optional iroh lane.

Terminalbash
chio partner demo --out partner-card.json
chio partner add partner-card.json --name partner --transport iroh
Output
partner    did:chio:z6MkpA7…c2T, named partner
kernel     9b07…d31c, pinned from its card
transport  iroh, endpoint 3fa8…91be, authenticated at handshake
lanes      signals · revocation · co-sign

chio partner demo

Run a demonstration partner on this machine, with its own kernel, keys, policy, and agents, and write its partner card.

Command synopsistext
chio partner demo [OPTIONS] --out <OUT>
  • --out <OUT> Path for the partner card. Required.

chio partner add

Add a partner from its partner card and pin its kernel key.

Command synopsistext
chio partner add [OPTIONS] --name <NAME> <CARD>
  • <CARD> Partner card file. Required.
  • --name <NAME> Local name for the partner, used by Computer.connect. Required.
  • --transport <TRANSPORT> Transport the two kernels use. Default https. Values https, iroh.
Additional behavior

The card carries the partner’s organization DID, trust-control URL, authority key history, receipt-signer keys, and status resolve URL. HTTPS with mTLS or signed bodies is the default transport. iroh selects authenticated QUIC through self-hosted relays and carries the signals, revocation, and co-sign lanes.

chio partner status

Print the stored record for a partner: pinned kernel key, handshake schema, assurance tier against your floor, admitted capabilities, ladder manifest, and the key-rotation deadline.

Command synopsistext
chio partner status [OPTIONS] <NAME>
  • <NAME> Partner name given to chio partner add. Required.

chio partner handshake

Run the kernel handshake with a partner now, re-verify its pinned key and ladder manifest, and renew the rotation deadline.

Command synopsistext
chio partner handshake [OPTIONS] <NAME>
  • <NAME> Partner name given to chio partner add. Required.

Read more in Pair your kernel with theirs.