Deployment Scenarios

Genesis Mesh is easiest to understand when mapped to real operating models. These examples are not separate products; they are common shapes for the same trust, identity, routing, authorization, and revocation model.

AI Agent Network

        flowchart TB
    na["Network Authority"]
    supervisor["Supervisor Agent"]
    finance["Finance Agent"]
    crm["CRM Agent"]
    support["Support Agent"]
    policy["Signed Policy"]
    crl["Signed CRL"]

    na -->|join cert| supervisor
    na -->|join cert| finance
    na -->|join cert| crm
    na -->|join cert| support
    na -->|publishes| policy
    na -->|publishes| crl

    supervisor <-->|Noise XX + routes| finance
    supervisor <-->|Noise XX + routes| crm
    supervisor <-->|Noise XX + routes| support
    

Use this shape when autonomous or semi-autonomous agents need to communicate without becoming anonymous processes on a flat network. Genesis Mesh gives each agent a signed identity, assigns roles during enrollment, distributes policy, and lets the operator revoke a compromised or retired agent identity.

Edge Fleet

        flowchart LR
    na["Network Authority"]
    factory_a["Factory A<br/>Edge Node"]
    factory_b["Factory B<br/>Edge Node"]
    factory_c["Factory C<br/>Edge Node"]
    control["Operations Control"]

    na -->|certs, policy, CRL| factory_a
    na -->|certs, policy, CRL| factory_b
    na -->|certs, policy, CRL| factory_c
    control -->|signed admin actions| na

    factory_a <-->|peer route| factory_b
    factory_b <-->|peer route| factory_c
    factory_a -. multi-hop DATA .-> factory_c
    

Use this shape when sites need authenticated peer communication across locations but the organization still needs central admission, revocation, and policy control. The Network Authority manages trust state; edge nodes use that state to communicate directly.

Sovereign Organization

        flowchart TB
    root["Root Sovereign"]
    genesis["Signed Genesis Block"]
    na["Network Authority"]
    hq["HQ Node"]
    branch_a["Branch A Node"]
    branch_b["Branch B Node"]
    branch_c["Branch C Node"]

    root -->|signs| genesis
    genesis -->|authorizes| na
    na -->|enrolls| hq
    na -->|enrolls| branch_a
    na -->|enrolls| branch_b
    na -->|enrolls| branch_c

    hq <-->|Noise XX| branch_a
    hq <-->|Noise XX| branch_b
    branch_b <-->|Noise XX| branch_c
    

Use this shape when a company, lab, public-sector team, or defense environment must own its root of trust. Genesis Mesh keeps membership, policy, certificate validity, and revocation under the operator’s control instead of relying only on a third-party network control plane.

Distributed Compute Cluster

        flowchart LR
    na["Network Authority"]
    scheduler["Trusted Scheduler"]
    worker_a["Worker A"]
    worker_b["Worker B"]
    worker_c["Worker C"]

    na -->|role:scheduler cert| scheduler
    na -->|role:worker cert| worker_a
    na -->|role:worker cert| worker_b
    na -->|role:worker cert| worker_c

    scheduler -->|authorized work message| worker_a
    scheduler -->|authorized work message| worker_b
    worker_b -->|forwarded result| scheduler
    worker_c -. revoked identity rejected .-> scheduler
    

Use this shape when workers should accept tasks only from trusted identities. Enrollment roles and policy constrain who can schedule work, while certificate revocation removes workers or schedulers that should no longer participate.