Trust & Sovereignty Examples

These examples are the architectural heart of Genesis Mesh, shown in running code: portable trust between independently administered sovereigns, treaty-based recognition, cross-boundary revocation propagation, and a human-visible recognition graph.

Read this section if you want to understand or demonstrate how trust travels across sovereign boundaries without a central authority.

Start Here

Sovereign Membership Attestations

One sovereign issues a signed membership attestation; another sovereign accepts or rejects it based on local recognition policy.

Example: Sovereign Membership Attestations
Recognition Treaties

Explicit signed community-to-community recognition. Treaty-backed attestation verification and revocable treaties.

Example: Recognition Treaties
Cross-Sovereign Revocation Propagation

Signed revocation feeds that propagate trust withdrawal across recognized sovereigns without revoking the treaty itself.

Example: Cross-Sovereign Revocation Propagation
Connectome Operator View

The recognition graph rendered for an operator, including trust-path explanations and revocation blast-radius summaries.

Example: Connectome Operator View
Independent Sovereigns Proof

The cross-cloud operational proof between sovereigns on Azure and DigitalOcean, with separate keys, databases, and policies.

Example: Independent Sovereigns Proof
Trust Evidence

Two independently keyed sovereigns produce and verify a signed TrustEvidence record offline — no shared backend or identity provider required.

Example: Trust Evidence
Trust Atlas

A read-only explorer over the recognition graph — sovereigns, relationships, treaty scope, and TrustEvidence overlay — as a live console page or a self-contained static snapshot.

Example: Trust Atlas
Relationship Agreement

Two sovereigns exchange a dual-signed AgreementRecord via Offer → Counter → Acceptance. Neither party can produce the record alone. The first artifact in GM that requires two independent signatures.

Example: Relationship Agreement
Delegation Chain

A party holding an AgreementRecord delegates a strict subset of its rights to a third party. Every hop in the chain is independently signed. Capabilities can only narrow — never widen — at each hop.

Example: Attenuable Delegation Chain
Relationship Context

A ContextRecord asserts a specific capability invocation. The BoundaryEngine evaluates it against ordered gates and produces a signed, time-bounded BoundaryDecision. An agreement alone is not an authorization.

Example: Relationship Context
Execution Evidence Chain

After execution, each event is recorded as a signed ExecutionEvidence record linked by prev_evidence_digest. Any insertion, deletion, reorder, or tampering breaks the chain and is immediately detectable.

Worked Example: Execution Evidence Hash Chain
Freshness Proofs

A FreshnessProof binds revocation-feed state to a specific time. The BoundaryEngine embeds valid proofs in every BoundaryDecision; execution records produced after the proof window are flagged as stale.

Worked Example: Freshness Proofs + Bounded Revocation
Formal Verification + Interop Bridges

The GenesisMesh protocol is formally verified with Tamarin Prover (five security lemmas). GM records cross ecosystem boundaries via SPIFFE, W3C VC, and JOSE/JWT bridges without losing provability guarantees.

Formal Verification + Interop Bridges
Invocation-Bound Capability Tokens

A compact signed token that lets an agent prove offline what it can do, how often, and until when — without calling the GM stack. Supports budget caps, policy constraints, and tamper-evident use chains.

Invocation-Bound Capability Tokens (IBCTs)
Justification Proofs

A signed artifact that proves not just what the BoundaryEngine decided, but how: the ordered gate inputs, intermediate results, and short-circuit point. Any auditor can verify the reasoning offline without re-running the engine.

Justification Proofs
Human Oversight

An 8-check deterministic policy engine that classifies proposed actions as automatic, human_approve, or block. High-stakes actions require a DualSignedCommitment — both agent and human custodian keys are required.

Human Oversight + Dual-Signed Commitments
Selective Disclosure

Merkle-based capability membership proofs. Prove that you hold a specific capability without revealing the full capability set, the agreement ID, or any other capability. CapabilityNullifier prevents replay.

Selective Disclosure Capability Proofs
Distributed Consensus

K-of-N validator threshold for high-stakes decisions. Validators sign the same JustificationProof; the assembled ConsensusProof gates an EphemeralExecutionIdentity that expires in ~120 s. Opt-in gate — normal authorization is unaffected.

Distributed Consensus Authorization
Peer Risk Signals

Locally-computed EWMA over ExecutionEvidence outcomes, time-decayed between updates. Anomaly detection when a delta exceeds 3σ of the last 10 updates. RiskSignalGate is opt-in. Not a reputation system — each sovereign’s signals are independent and never shared.

Peer Risk Signals
Cascade-Resilient Consensus

Extends K-of-N voting with Context Divergence Score and Temporal Clustering Score. Assembly is blocked when CascadeScore exceeds threshold, preventing correlated validators from satisfying a threshold they appear to meet independently.

Cascade-Resilient Consensus
Adversarial Seed Isolation

Pattern-based detection of credit-farming attacks on PeerRiskSignals. Three scores — Credit Farming (CFS), Volatility Discontinuity (VDS), and Streak Fragility (SFS) — identify adversarial histories that evaded per-update anomaly detection. SeedIsolationGate is opt-in. Each sovereign’s assessment is independent.

Example: Adversarial Seed Isolation
Verifiable Logic Attestation

Closes the “hidden instruction” exploit: a signed ModelAttestation binds model_id, system_prompt_hash, and tool_manifest_hash to each capability invocation. LogicAttestationGate rejects mismatched configurations before execution proceeds.

Example: Verifiable Logic Attestation
Context-Injection Defense Gate

Blocks prompt-injection attacks via structural context commitment: a signed ContextIntegrityRecord declares permitted append segments before execution. ContextInjectionGate rejects undeclared, oversized, or tampered context at runtime.

Example: Context-Injection Defense Gate
Ephemeral Identity Purge Protocol

Verifiable deletion of expired EphemeralExecutionIdentities. NullificationReceipts commit to identity existence and destruction without retaining sensitive fields. A signed Merkle registry enables auditable proof of inclusion without resurrecting deleted records.

Example: Ephemeral Identity Purge Protocol
Communication Privacy Layer

Defends against SALA mesh-layer fingerprinting: normalizes message length (block-padding), dispatch timestamps (bucket rounding), and strips custom headers before forwarding. MetadataEnvelopes are signed; a PrivacyAuditRecord documents exactly what was changed.

Example: Communication Privacy Layer
Sovereign Overlay Discovery

DNS-free peer discovery via gossip over existing Noise XX connections. OverlayDiscoveryRecords are Ed25519-signed, binding endpoint to cryptographic identity. Sequence numbers enable supersession detection; hop-count limits prevent unbounded gossip propagation.

Example: Sovereign Overlay Discovery
Process-Level Execution Mediation

GenesisGuard local enforcement sidecar: validates BoundaryDecision and IBCT before spawning subprocesses. Issues signed MediatedExecutionReceipts. Covers advisory mode and mandatory mediation mode with explicit 5-point enforcement checklist. Non-LLM, deterministic, no network access.

Example: Process-Level Execution Mediation
Trust Path Performance and Atlas Pruning

TrustPathCache (signed, TTL-bound) accelerates repeat path lookups to O(1). GraphPruningPolicy removes expired, revoked, and empty-scope edges. Every pruning run produces a signed PrunedAtlasExport with per-edge audit entries and staleness guard (refuses to prune graphs older than policy max).

Example: Trust Path Performance and Atlas Pruning
Data Usage Attestation Layer

Signed pre- and post-execution attestation for data access. DataLicensePolicy defines source allowlists and volume caps. DataAccessIntent and DataAccessRecord bind the agent’s declared intent to actual access. DataUsageGate integrates with BoundaryEngine. Payment and settlement are explicitly out of scope.

Example: Data Usage Attestation Layer
Formal PeerRiskSignal Verification

Three Tamarin Prover lemmas over the PeerRiskSignal state machine: (1) signal_bounded — signal stays in [0,1]; (2) anomaly_detection_responsive — SuddenDrop cannot permanently suppress detection; (3) no_single_source_cascade — cascade amplification requires independent per-sovereign observations. Executable property tests included for standard pytest runs.

Example: Formal PeerRiskSignal Verification (Tamarin)