Adoption & Positioning Examples¶
These examples are the material aimed at people evaluating Genesis Mesh for their own use - maintainers considering running a sovereign, organizations considering a managed deployment, and readers comparing it to adjacent projects.
Read this section if you are deciding whether Genesis Mesh fits your problem, or if you are explaining the project to someone who is.
Start Here¶
A narrow CI/release gate that demonstrates how Genesis Mesh sits in a publishing path - portable maintainer attestations honored across projects, with revocation blocking the same maintainer after import.
The operational claim behind a managed Network Authority - backup, restore, audit, and incident workflows are demonstrable end to end.
The operator-onboarding path: export public trust material, validate it, record a review receipt, and feed it into federation bootstrap without granting trust automatically.
The operator lifecycle view for recognition treaties: active, expiring, expired, revoked, replaced, and visible in Connectome.
One read-only page for local sovereign readiness, treaty risk, revocation-feed freshness, recent trust changes, and raw verification links.
A recruitment-oriented page aimed at open-source maintainers explaining the concrete reasons to stand up a sovereign.
A synthetic two-sovereign demo of the “team as operator” pattern behind the Aspayr Athlete Financial Twin direction - team-shaped sovereigns recognize each other and propagate a revocation. No affiliation, no real data.
How Genesis Mesh differs from in-domain provenance signing systems, and why portable trust across sovereigns is a distinct property.