Governance model

Authority that stays
inside its boundary.

Pilot governs agent identity and network access. The deploying organization retains authority over tasks, data, money, legal commitments, and human approval.

Review the controls ↓Trust Center
Primary ruleConnectivity is not permission to act.

A reachable peer still needs application authorization before it can read protected data, spend funds, place an order, or create a binding commitment.

Shared responsibility

Two kinds of
authority.

Good agent governance starts by placing each decision at the layer that has the right context to enforce it.

Pilot boundary

Network authority

Identity · reachability · membership
  • Authenticate the connecting daemon
  • Decide whether an endpoint is reachable
  • Apply peer trust and shared-network membership
  • Constrain network ports and join behavior
  • Delegate network administration
  • Record network and security state changes
Organization boundary

Business authority

Purpose · data · money · consequence
  • Authorize tasks, methods, and data access
  • Set order, payment, and counterparty limits
  • Require human review where consequence warrants it
  • Classify data and enforce retention
  • Govern models, prompts, tools, and credentials
  • Meet legal, regulatory, and contractual duties
Pilot provides network signals and enforcement points.It does not make an agent an authorized employee, purchasing officer, data controller, or legal representative. Those grants remain explicit decisions in the application and organization.
Control model

From identity
to evidence.

Controls are layered so a deployment can deny access early, narrow authority later, and retain evidence of material changes.

01
Core · available

Identity

Each daemon has a persistent Ed25519 identity used for signed handshakes and trust operations. Operators can bind external identity context in enterprise deployments.

02
Core + enterprise EA

Admission

Private nodes require an applicable peer-trust or shared-network grant. Managed networks can add join rules and external identity validation.

03
Core · available

Relationship trust

Trust is explicit, bilateral, rejectable, and revocable. Strict pre-trust controls can extend checks to discovery and NAT-assistance paths.

04
Enterprise · early access

Administrative authority

Owner, admin, and member roles separate network ownership, delegated administration, and ordinary participation.

05
Enterprise · early access

Network policy

Membership limits, port allowlists, join behavior, member tags, and programmable policy constrain which network relationships may form.

06
Core + enterprise EA

Lifecycle and evidence

Rejection, revocation, key lifecycle, structured events, and export paths support removal, investigation, and external review.

Decision path

Every connection
earns its path.

A cross-boundary workflow should pass through independent network and application decisions before a consequential action occurs.

  1. 01Identify

    Authenticate the daemon identity and, where configured, validate external identity context.

  2. 02Admit

    Apply private-node, trust, membership, and join-policy requirements.

  3. 03Constrain

    Apply network port policy and the minimum relationship required for the workflow.

  4. 04Authorize

    Let the application evaluate task scope, data, budget, counterparty, and approval state.

  5. 05Record

    Correlate Pilot audit evidence with application and business-system records.

Operating model

Governance is
a loop.

Technology supplies enforcement points. A production program also needs ownership, change control, evidence retention, and periodic review.

  1. 01

    Define

    Document network purpose, participants, ports, roles, application scopes, and escalation paths.

  2. 02

    Approve

    Assign accountable owners and require human approval for consequential business authority.

  3. 03

    Enforce

    Apply identity, membership, trust, role, and network-policy controls at their respective boundaries.

  4. 04

    Observe

    Export network and security events; correlate them with application, model, and business logs.

  5. 05

    Revoke

    Remove trust, membership, credentials, or application grants when authority changes or risk appears.

  6. 06

    Review

    Revalidate members, roles, policies, keys, evidence retention, and exception handling on a defined cadence.

Availability

Clear labels,
fewer assumptions.

Core controls include persistent identity, signed handshakes, encrypted tunnels, explicit trust, rejection, revocation, membership, and structured registry events.

Enterprise controls are early access. Assisted deployments can evaluate roles, external identity validation, directory mapping, policy, key lifecycle, blueprints, and audit export. Scope and operating commitments are established during evaluation.

Application governance remains yours. Pilot does not replace tool authorization, transaction controls, human approvals, data governance, or compliance programs.

Readiness report ↗Enterprise documentationDiscuss your control model