Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Genesis Mesh
Logo
Genesis Mesh

Start Here

  • Quick Start
  • How It Works in Five Minutes
  • Tutorials
  • Installation
  • Public API Stability
  • Changelog
  • Tutorial: Build and Verify Trust Evidence

Concepts

  • Introduction
    • Overview
    • Design Goals
    • Glossary
  • Protocol
    • Architecture
    • Trust Model
    • Security Model
    • Governed Changes and Evidence
    • Certificate Lifecycle
    • Routing
  • Context
    • Use Cases
    • Comparison With Existing Solutions
    • Deployment Scenarios
  • Rust Trust Gateway

SDK Clients

  • Overview
  • Develop Against a Local Network Authority
  • TypeScript SDK
    • Client
      • Sub-clients — TypeScript SDK
      • Auth, Errors & Types — TypeScript SDK
      • High availability (v0.60)
    • Governed actions
      • Governed SDK actions
      • Evidence store and policy clients
      • Changes outside the controlled path
      • Remediation, reviews and urgent changes
      • Pre-issued grants
    • Verification
      • Offline verification
      • Key succession, audit packs and offline verification
  • Go SDK
    • Sub-clients — Go SDK
    • Auth, Errors & Types — Go SDK
    • Offline Verification — Go SDK
  • .NET SDK
    • Sub-clients — .NET SDK
    • Auth, Errors & Types — .NET SDK
    • Offline Verification — .NET SDK
  • Rust
    • Rust SDK
    • Rust SDK: governed actions and records
    • Rust SDK: pre-issued grants
    • Rust SDK: offline verification
    • Gateway crate
    • Gateway: modules and CLI
    • Gateway: signing admin requests and errors

Operators

  • Operator Guides
  • Setup & Security
    • Operator Quickstart
    • Production Checklist
    • Operator Security Checklist
    • Maintainer-Operated Multi-Cloud Sovereigns
  • Federation & Recognition
    • Federation Bootstrap
    • Trust Bundle Exchange
    • External Operator Proof
    • Treaty Lifecycle
    • Recognition Playbook
    • Operator Exit and Fork
    • Managing Partner Control Boundary
  • Reference
    • Sovereign Health and Trust Dashboard
    • Proof Bundle Schema

Infrastructure

  • Deployment
    • Deployment Options
    • Container Images
    • High Availability
    • Sanitized public reference dashboard
    • Network Authority VM Bootstrap
    • Infrastructure
    • Terraform Deployment on Azure
    • Kubernetes Deployment
  • Runbooks
    • Monitoring
    • Audit Export
    • Governed Changes and Audit
      • Judging Changes
        • Changes Outside the Controlled Path
        • Remediation and Reviews
        • Emergency Changes and Break-Glass
      • Offline Changes
        • Pre-Issued Grants
        • The Edge Agent
        • Walkthrough: Enrolling an Edge Device
      • Audit Evidence
        • Evidence Anchors
        • Audit and Retention
        • Audit Packs
        • Verifying a Pack
        • The Rust Verifier
        • Walkthrough: Verifying an Audit Pack
      • Keys
        • Key Succession and the Root Key
        • Walkthrough: Succeeding the NA Key
    • Incident Response Runbooks
    • Backup and Restore
    • Upgrade and Rollback
    • Pilot Deployment Profile
    • Revocation
    • Managed Sovereign Operations

Reference

  • Public Contract
  • CLI Reference
    • Network Authority Commands
    • Evidence and Audit Commands
    • Federation Commands
    • Node and Developer Commands
    • Trust Graph Commands
    • Agreement and Policy Commands
    • Evidence and Token Commands
    • Oversight and Consensus Commands
    • Agent Control Commands
  • Network Authority API
  • Configuration Reference
  • Evidence event schema (gm.evidence.event v1)
  • Audit Pack Format
  • Canonical Form of Signed Records
  • Trust API — HTTP Reference

Protocol RFCs

  • Genesis Mesh RFCs
    • RFC-001 — Sovereign Identity
    • RFC-002 — Recognition Treaties
    • RFC-003 — Trust Bundles
    • RFC-004 — Revocation Feeds
    • RFC-005 — Capability Manifests
    • RFC-006 — Connectome Model
    • RFC-007 — Operator Continuity
    • RFC-008 — Managed Operator Role
    • Prior Art and Design Lineage

Contributing

  • Contributing
  • Code Architecture
    • Node Runtime Internals (dormant)
  • Testing
  • Cross-Language Interoperability
  • Security Policy
  • Security Review for v1

Project

  • Project History
  • Project Phases
    • Building the Mesh (Phases A–D)
      • Phase A – Foundation
      • Phase B – Agent Layer
      • Phase C – The Trust Thesis
      • Phase D – Operational Proof
    • Operating and Adopting (Phases E–G)
      • Phase E – Operator Readiness
      • Phase F – Multi-Cloud Operation
      • Phase G – Application Layer
    • Trust Architecture and Governed Changes (Phases H–J, N)
      • Phase H – First Complete Trust Architecture Cycle
      • Phase I – Runtime Trust Layer
      • Phase J – Third Trust Cycle and 1.0
      • Phase N – Governed Changes and Edge Trust
  • Versioning
  • Direction
    • Genesis Mesh Strategy
    • Roadmap
    • Milestones
      • Rollout Closure
      • Externalization
    • Genesis Mesh Atlas
  • Genesis Mesh RFC Program
  • RFC Decision Log
  • Decisions
    • 0001: Release model: a pinned contract bundle, not lockstep
    • 0002: SDK capability tiers; Go and .NET as verifier plus thin client
    • 0003: Verification engine: separate ports driven by generated tables
    • 0004: Forward compatibility for unknown record kinds
    • 0005: Feature-switch lifecycle and upgrade support window
    • 0006: Review: automatic Copilot review and review agents, no required human approval
    • 0007: Dormant core packages are internal
  • Governance
    • Genesis Mesh RFC Program
    • RFC Decision Log
    • Decisions
      • 0001: Release model: a pinned contract bundle, not lockstep
      • 0002: SDK capability tiers; Go and .NET as verifier plus thin client
      • 0003: Verification engine: separate ports driven by generated tables
      • 0004: Forward compatibility for unknown record kinds
      • 0005: Feature-switch lifecycle and upgrade support window
      • 0006: Review: automatic Copilot review and review agents, no required human approval
      • 0007: Dormant core packages are internal

Examples

  • Overview & Demos
    • Demos
    • Capability Demos (Part A)
    • Packaging & Operations Smoke Tests (Part C)
    • Example: Capacity Baseline
  • Agent & Capability Examples
    • Example: AI Agent Network
    • Example: Multi-Agent Workflow
    • Example: Distributed Capability Orchestration
  • Trust & Sovereignty Examples
    • Core Trust & Sovereignty
      • Example: Sovereign Membership Attestations
      • Example: Recognition Treaties
      • Example: Cross-Sovereign Revocation Propagation
      • Example: Independent Sovereigns Proof
      • Example: Two Sovereigns from the Signed Images
      • Example: Connectome Operator View
      • Example: Trust Atlas
    • Relationships & Agreements
      • Example: Relationship Agreement
      • Example: Attenuable Delegation Chain
      • Example: Relationship Context
      • Declarative Boundary Policy
      • Example: Attestation-Backed Boundary Evaluation
      • Example: Trust Evidence
    • Evidence & Audit
      • Worked Example: Execution Evidence Hash Chain
      • Example: Evidence Store in the Network Authority
      • Example: Changes Outside the Controlled Path
      • Example: Pre-Issued Grants
      • Worked Example: Freshness Proofs + Bounded Revocation
      • Justification Proofs
      • Example: Data Usage Attestation Layer
    • Authorization Controls
      • Invocation-Bound Capability Tokens (IBCTs)
      • Human Oversight + Dual-Signed Commitments
      • Selective Disclosure Capability Proofs
      • Example: Process-Level Execution Mediation
      • Example: Ephemeral Identity Purge Protocol
    • Consensus & Risk
      • Distributed Consensus Authorization
      • Peer Risk Signals
      • Cascade-Resilient Consensus
      • Example: Adversarial Seed Isolation
      • Example: Trust Path Performance and Atlas Pruning
    • Security & Verification
      • Formal Verification + Interop Bridges
      • Example: Verifiable Logic Attestation
      • Example: Context-Injection Defense Gate
      • Example: Communication Privacy Layer
      • Example: Sovereign Overlay Discovery
      • Example: Formal PeerRiskSignal Verification (Tamarin)
    • Rust Trust Core Walkthrough
  • Adoption & Positioning Examples
    • Supply-Chain Trust Gate
    • Managed Sovereign Readiness Example
    • Federation Bootstrap And Trust Bundle Exchange
    • Treaty Lifecycle Management
    • Sovereign Health and Trust Dashboard
    • Why A Maintainer Would Run A Sovereign
    • Genesis Mesh vs Sigstore And SLSA
  • Use-Case Walkthroughs
    • Example: Edge Fleet
    • Example: Sovereign Organization
    • Example: Distributed Compute Cluster
Back to top
View this page
Edit this page

Client¶

The client itself: what each sub-client wraps, how admin requests are signed and errors reported, and how the client works with several NA instances.

  • Sub-clients — TypeScript SDK: every sub-client’s methods and the key tier each needs

  • Auth, Errors & Types — TypeScript SDK: admin signatures, raw admin calls, errors and types

  • High availability (v0.60) (v0.60): failover across NA instances, readiness, and retryable conflicts

Next
Sub-clients — TypeScript SDK
Previous
TypeScript SDK
Copyright © 2026, Genesis Mesh contributors
Thesis and proofs → genesismesh.org Hub, videos and articles → www.genesismesh.org Try it → mesh.genesismesh.org