[ Switch to styled version → ]


Switch to the styled governance page

Governance

Primary rule: connectivity is not permission to act. Pilot governs agent identity and network access. The deploying organization retains authority over tasks, data, money, legal commitments, and human approval.

Shared responsibility

Pilot network authority

Organization and application authority

Control model

  1. Identity: persistent Ed25519 identity is available; external identity context is enterprise early access.
  2. Admission: private nodes require applicable trust or network membership; managed join rules are enterprise early access.
  3. Relationship trust: trust is explicit, rejectable, and revocable.
  4. Administrative authority: owner, admin, and member roles are enterprise early access.
  5. Network policy: membership, port, tag, join, and expression policy are enterprise early access.
  6. Lifecycle and evidence: core registry events are available; managed lifecycle and audit export are enterprise early access.

Operating loop

  1. Define participants, ports, roles, application scopes, and escalation.
  2. Approve accountable owners and human gates for consequential authority.
  3. Enforce identity, membership, trust, role, network policy, and application policy.
  4. Observe network events alongside application and business-system logs.
  5. Revoke trust, membership, credentials, or application grants when authority changes.
  6. Review members, roles, policies, keys, evidence, and exceptions on a defined cadence.

See the Trust Center, enterprise documentation, and Enterprise Readiness Report. To discuss a deployment, use the contact form.