genesis-mesh 0.5.0__tar.gz

genesis_mesh-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

genesis_mesh-0.5.0/PKG-INFO

@@ -0,0 +1,338 @@
+Metadata-Version: 2.4
+Name: genesis-mesh
+Version: 0.5.0
+Summary: Sovereign trust, identity, and communication fabric for AI agents, edge systems, and distributed infrastructure.
+Author-email: Thaer Saidi <thaer.saidi@outlook.com>
+Maintainer-email: Thaer Saidi <thaer.saidi@outlook.com>
+License-Expression: MIT
+Project-URL: Homepage, https://genesismesh.connectorzzz.com
+Project-URL: Documentation, https://genesismesh.connectorzzz.com
+Project-URL: Repository, https://github.com/thaersaidi/genesismesh
+Project-URL: Issues, https://github.com/thaersaidi/genesismesh/issues
+Project-URL: Releases, https://github.com/thaersaidi/genesismesh/releases
+Project-URL: Live Deployment, https://na.genesismesh.connectorzzz.com
+Keywords: mesh,p2p,noise-protocol,ed25519,decentralized,trust,identity,revocation,sovereign,agents
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Topic :: System :: Networking
+Classifier: Topic :: Security :: Cryptography
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Framework :: Flask
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography==48.0.0
+Requires-Dist: PyNaCl==1.6.2
+Requires-Dist: requests==2.34.2
+Requires-Dist: Flask==3.1.3
+Requires-Dist: pydantic==2.13.4
+Requires-Dist: python-dateutil==2.9.0.post0
+Requires-Dist: click==8.4.1
+Requires-Dist: dissononce==0.34.3
+Requires-Dist: websockets==16.0
+Requires-Dist: gunicorn==22.0.0
+Provides-Extra: dev
+Requires-Dist: pytest==9.0.3; extra == "dev"
+Requires-Dist: pytest-asyncio==1.4.0; extra == "dev"
+Requires-Dist: mypy==2.1.0; extra == "dev"
+Requires-Dist: pip-audit==2.10.0; extra == "dev"
+Requires-Dist: pre-commit==4.4.0; extra == "dev"
+Provides-Extra: docs
+Requires-Dist: sphinx==9.1.0; extra == "docs"
+Requires-Dist: furo==2025.12.19; extra == "docs"
+Requires-Dist: myst-parser==5.1.0; extra == "docs"
+Requires-Dist: sphinxcontrib-mermaid==2.0.2; extra == "docs"
+Dynamic: license-file
+
+# Genesis Mesh
+
+[![Docs](https://img.shields.io/badge/docs-online-blue)](https://genesismesh.connectorzzz.com)
+[![License](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+[![Release](https://img.shields.io/github/v/release/thaersaidi/genesismesh)](https://github.com/thaersaidi/genesismesh/releases)
+
+## Live Deployment
+
+| | |
+|---|---|
+| Network Authority | Online |
+| Public Endpoint | https://na.genesismesh.connectorzzz.com |
+| Deployment | Azure VM, Sweden Central |
+| TLS | Enabled |
+| Active Nodes | 2 |
+| Tracked Nodes | 2 |
+| Remote Nodes | 1 |
+| Online since | 2026-05-30 |
+
+Current deployment demonstrates:
+
+- Identity and certificate-based enrollment
+- Remote nodes across separate networks
+- Noise XX encrypted peer sessions
+- Direct message delivery
+- Multi-hop routing and packet forwarding
+- Route failure recovery
+- Certificate revocation and CRL enforcement
+
+![NA dashboard showing 2 active nodes](docs/examples/assets/na-dashboard.png)
+
+![/nodes endpoint showing two enrolled nodes with different remote addresses](docs/examples/assets/na-nodes.png)
+
+## Live Message Delivery
+
+A remote local node sends a DATA message to an Azure-hosted node over a Noise XX encrypted peer session.
+
+![Genesis Mesh live message delivery](docs/examples/assets/genesis-mesh-message-delivery.gif)
+
+- Noise XX handshake completed
+- Connection established
+- Neighbor added
+- DATA message delivered
+
+## Multi-Hop Routing
+
+Genesis Mesh supports decentralized route propagation and packet forwarding.
+
+Node A and Node C do not connect directly. Instead:
+
+**Node A → Node B → Node C**
+
+Node B learns routes, forwards packets, and decrements TTL values during transit.
+
+![Genesis Mesh multi-hop routing demo](docs/examples/assets/genesis-mesh-multi-hop.gif)
+
+- Route learned via intermediate node
+- DATA forwarded by router
+- DATA delivered to destination
+
+## Route Failure Recovery
+
+When a router goes offline, neighboring nodes withdraw its routes and traffic re-routes through a surviving path — no operator intervention.
+
+**Topology:** A reaches C through two routers — B (primary) and D (backup). B is killed mid-demo.
+
+![Genesis Mesh route failure recovery demo](docs/examples/assets/genesis-mesh-failover.gif)
+
+- Primary path A → B → C delivers
+- B goes offline
+- A detects the disconnect and invalidates B's routes
+- A → D → C delivers without retry or operator action
+
+
+![Genesis Mesh revocation demo](docs/examples/assets/genesis-mesh-revocation.gif)
+
+**Trust can be revoked.**
+
+A revoked node is removed from the active set, added to a signed CRL, and
+immediately rejected by heartbeat, renewal, handshake, and routing checks.
+
+Genesis Mesh treats revocation as a first-class control-plane action. When an
+operator revokes a certificate, the Network Authority publishes a new signed
+CRL, removes the node from the active set, and rejects further heartbeat,
+renewal, peer handshake, and routing activity from that identity.
+
+---
+
+Genesis Mesh is a sovereign trust, identity, and communication fabric for AI
+agents, edge systems, and distributed infrastructure.
+
+It answers the operational questions that basic mesh networking leaves open:
+who is allowed to be a node, how peers prove identity, what each node is
+allowed to do, how messages reach the right peer, and how a compromised or
+retired identity is removed.
+
+Genesis Mesh combines five capabilities in one trust fabric:
+
+- **Identity**: every node has an Ed25519 identity and a signed join certificate.
+- **Trust**: a signed genesis block, Network Authority, operator keys, and CRLs
+  define who the network trusts.
+- **Routing**: authenticated peers discover routes and forward messages without
+  depending on the Network Authority for every data exchange.
+- **Authorization**: enrollment roles, policy manifests, RBAC, and signed admin
+  actions define what identities may do.
+- **Sovereignty**: the operator owns the trust chain, membership process,
+  revocation process, and policy distribution path.
+
+Every enrolled node holds a signed join certificate issued by the Network
+Authority. Peer sessions are encrypted with the Noise XX protocol, deriving
+X25519 keys directly from each node's Ed25519 identity. No separate TLS
+certificate lifecycle is required for peer transport.
+
+## Why It Exists
+
+Most overlay networks focus on connectivity: can this machine reach that
+machine? Genesis Mesh focuses on controlled participation: should this machine
+be here, what identity is it using, what is it authorized to do, and can the
+network remove it quickly?
+
+Use Genesis Mesh when your system needs:
+
+- a private trust domain for agents, devices, or edge services
+- operator-controlled enrollment instead of open peer discovery
+- certificate-backed peer authentication
+- signed policy distribution
+- revocation that affects heartbeats, renewal, peer handshakes, and routing
+- audit trails for security-relevant control-plane actions
+
+Do not use it when you only need public peer discovery, anonymous networking, a
+general service mesh for Kubernetes ingress, or a permissionless blockchain.
+
+## Architecture
+
+```mermaid
+flowchart TD
+    RS["Root Sovereign<br/>offline trust anchor"]
+    NA["Network Authority<br/>invite enrollment, certs, CRLs, policy"]
+    A["Node A"]
+    B["Node B"]
+    C["Node C"]
+
+    RS -->|"signs genesis"| NA
+    NA -->|"invite token + join certificate"| A
+    NA -->|"invite token + join certificate"| B
+    NA -->|"invite token + join certificate"| C
+
+    A <-->|"Noise XX encrypted peer session"| B
+    B <-->|"Noise XX encrypted peer session"| C
+    A <-->|"Noise XX encrypted peer session"| C
+
+    NA -.->|"signed CRL bootstrap"| A
+    A -.->|"CRL gossip"| B
+    B -.->|"CRL gossip"| C
+```
+
+At a high level, the Network Authority admits identities and publishes trust
+state. Nodes use that state to communicate directly, route messages, and reject
+revoked peers.
+
+## Documentation
+
+[Documentation Website](https://genesismesh.connectorzzz.com)
+
+## Requirements
+
+- Python 3.12 or later
+- See `requirements.txt` for pinned runtime dependencies
+
+## Installation
+
+```bash
+python -m venv .venv
+source .venv/bin/activate   # PowerShell: .\.venv\Scripts\Activate.ps1
+pip install -r requirements.txt
+pip install -e .
+```
+
+## Quick Start
+
+The local workflow runs the NA in one terminal and joins a node in a second.
+
+```bash
+# Create keys, genesis block, and CLI config (one time).
+genesis-mesh init
+
+# Start the Network Authority (keep this terminal open).
+genesis-mesh na start
+
+# In a second terminal: create a single-use invite and join.
+INVITE_TOKEN=$(genesis-mesh admin invite --role anchor)
+genesis-mesh join --na http://127.0.0.1:8443 --token "$INVITE_TOKEN"
+
+# Inspect NA health and node certificate state.
+genesis-mesh status
+```
+
+PowerShell:
+
+```powershell
+$INVITE_TOKEN = genesis-mesh admin invite --role anchor
+genesis-mesh join --na http://127.0.0.1:8443 --token $INVITE_TOKEN
+```
+
+Full local smoke test:
+
+```bash
+genesis-mesh dev up
+```
+
+## Production Deployment
+
+Container startup uses `start.sh` and Gunicorn. Set `SERVICE_ROLE=na` for the
+Network Authority or `SERVICE_ROLE=node` for a peer node. The NA role requires
+two mounted secrets and fails closed if either is absent:
+
+| Environment variable      | Description                                      |
+|---------------------------|--------------------------------------------------|
+| `SERVICE_ROLE`            | `na` or `node`                                   |
+| `GENESIS_FILE`            | Path to the signed genesis block                 |
+| `NA_PRIVATE_KEY_FILE`     | Path to the NA Ed25519 signing key (NA role)     |
+| `OPERATOR_PUBLIC_KEYS_JSON` | JSON map of operator key IDs to public keys   |
+| `DB_PATH`                 | SQLite database path (default: `genesis_mesh_na.db`) |
+| `PORT`                    | Bind port (default: `8443`)                      |
+| `WEB_CONCURRENCY`         | Gunicorn worker count (default: `4`)             |
+
+The NA private key never leaves the NA process.
+
+Health and readiness probes are available at `/healthz` and `/readyz`.
+
+## Deployment Examples
+
+Genesis Mesh includes deployment examples for:
+
+- **Local process** — `genesis-mesh init && genesis-mesh na start`
+- **Docker** — `docker run` and Docker Compose (`docs/examples/compose/`)
+- **Kubernetes** — manifests under `examples/kubernetes/`
+- **Terraform on Azure** — `infrastructure/azure/`, the same module used by the live deployment
+
+See the [deployment guide](https://genesismesh.connectorzzz.com/operations/deployment.html) for the full walkthrough.
+
+## Repository Layout
+
+```
+.
+  Dockerfile              Container image definition
+  start.sh                Container entry point (NA and node roles)
+  requirements.txt        Pinned runtime dependencies
+  setup.py                Package metadata and entry points
+  docs/                   Sphinx documentation source
+  examples/               Demo workflows, sample genesis blocks, Kubernetes manifests
+  genesis_mesh/           Python package
+  infrastructure/         Terraform, Azure scripts, and operational tools
+```
+
+```
+genesis_mesh/
+  audit/                  Tamper-evident security audit logging
+  cli/                    High-level and low-level CLI commands
+  crypto/                 Ed25519 signing and key management
+  gossip/                 CRL gossip protocol
+  models/                 Genesis, certificate, policy, CRL, and enrollment models
+  monitoring/             Prometheus metrics and health checks
+  na_service/             Network Authority REST API and WSGI entry point
+  node/                   Node client, runtime, discovery, RBAC, and control plane
+  routing/                Routing table, protocol, and message forwarding
+  tests/                  Unit and integration tests
+  transport/              WebSocket transport, Noise XX, protocol framing, and connections
+```
+
+## Testing
+
+```bash
+python -m pytest genesis_mesh/tests -v
+```
+
+## Security
+
+To report a vulnerability, open a GitHub Security Advisory on this repository.
+Do not file a public issue for security-sensitive findings.
+
+## License
+
+[MIT](LICENSE)

genesis_mesh-0.5.0/README.md

@@ -0,0 +1,284 @@
+# Genesis Mesh
+
+[![Docs](https://img.shields.io/badge/docs-online-blue)](https://genesismesh.connectorzzz.com)
+[![License](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+[![Release](https://img.shields.io/github/v/release/thaersaidi/genesismesh)](https://github.com/thaersaidi/genesismesh/releases)
+
+## Live Deployment
+
+| | |
+|---|---|
+| Network Authority | Online |
+| Public Endpoint | https://na.genesismesh.connectorzzz.com |
+| Deployment | Azure VM, Sweden Central |
+| TLS | Enabled |
+| Active Nodes | 2 |
+| Tracked Nodes | 2 |
+| Remote Nodes | 1 |
+| Online since | 2026-05-30 |
+
+Current deployment demonstrates:
+
+- Identity and certificate-based enrollment
+- Remote nodes across separate networks
+- Noise XX encrypted peer sessions
+- Direct message delivery
+- Multi-hop routing and packet forwarding
+- Route failure recovery
+- Certificate revocation and CRL enforcement
+
+![NA dashboard showing 2 active nodes](docs/examples/assets/na-dashboard.png)
+
+![/nodes endpoint showing two enrolled nodes with different remote addresses](docs/examples/assets/na-nodes.png)
+
+## Live Message Delivery
+
+A remote local node sends a DATA message to an Azure-hosted node over a Noise XX encrypted peer session.
+
+![Genesis Mesh live message delivery](docs/examples/assets/genesis-mesh-message-delivery.gif)
+
+- Noise XX handshake completed
+- Connection established
+- Neighbor added
+- DATA message delivered
+
+## Multi-Hop Routing
+
+Genesis Mesh supports decentralized route propagation and packet forwarding.
+
+Node A and Node C do not connect directly. Instead:
+
+**Node A → Node B → Node C**
+
+Node B learns routes, forwards packets, and decrements TTL values during transit.
+
+![Genesis Mesh multi-hop routing demo](docs/examples/assets/genesis-mesh-multi-hop.gif)
+
+- Route learned via intermediate node
+- DATA forwarded by router
+- DATA delivered to destination
+
+## Route Failure Recovery
+
+When a router goes offline, neighboring nodes withdraw its routes and traffic re-routes through a surviving path — no operator intervention.
+
+**Topology:** A reaches C through two routers — B (primary) and D (backup). B is killed mid-demo.
+
+![Genesis Mesh route failure recovery demo](docs/examples/assets/genesis-mesh-failover.gif)
+
+- Primary path A → B → C delivers
+- B goes offline
+- A detects the disconnect and invalidates B's routes
+- A → D → C delivers without retry or operator action
+
+
+![Genesis Mesh revocation demo](docs/examples/assets/genesis-mesh-revocation.gif)
+
+**Trust can be revoked.**
+
+A revoked node is removed from the active set, added to a signed CRL, and
+immediately rejected by heartbeat, renewal, handshake, and routing checks.
+
+Genesis Mesh treats revocation as a first-class control-plane action. When an
+operator revokes a certificate, the Network Authority publishes a new signed
+CRL, removes the node from the active set, and rejects further heartbeat,
+renewal, peer handshake, and routing activity from that identity.
+
+---
+
+Genesis Mesh is a sovereign trust, identity, and communication fabric for AI
+agents, edge systems, and distributed infrastructure.
+
+It answers the operational questions that basic mesh networking leaves open:
+who is allowed to be a node, how peers prove identity, what each node is
+allowed to do, how messages reach the right peer, and how a compromised or
+retired identity is removed.
+
+Genesis Mesh combines five capabilities in one trust fabric:
+
+- **Identity**: every node has an Ed25519 identity and a signed join certificate.
+- **Trust**: a signed genesis block, Network Authority, operator keys, and CRLs
+  define who the network trusts.
+- **Routing**: authenticated peers discover routes and forward messages without
+  depending on the Network Authority for every data exchange.
+- **Authorization**: enrollment roles, policy manifests, RBAC, and signed admin
+  actions define what identities may do.
+- **Sovereignty**: the operator owns the trust chain, membership process,
+  revocation process, and policy distribution path.
+
+Every enrolled node holds a signed join certificate issued by the Network
+Authority. Peer sessions are encrypted with the Noise XX protocol, deriving
+X25519 keys directly from each node's Ed25519 identity. No separate TLS
+certificate lifecycle is required for peer transport.
+
+## Why It Exists
+
+Most overlay networks focus on connectivity: can this machine reach that
+machine? Genesis Mesh focuses on controlled participation: should this machine
+be here, what identity is it using, what is it authorized to do, and can the
+network remove it quickly?
+
+Use Genesis Mesh when your system needs:
+
+- a private trust domain for agents, devices, or edge services
+- operator-controlled enrollment instead of open peer discovery
+- certificate-backed peer authentication
+- signed policy distribution
+- revocation that affects heartbeats, renewal, peer handshakes, and routing
+- audit trails for security-relevant control-plane actions
+
+Do not use it when you only need public peer discovery, anonymous networking, a
+general service mesh for Kubernetes ingress, or a permissionless blockchain.
+
+## Architecture
+
+```mermaid
+flowchart TD
+    RS["Root Sovereign<br/>offline trust anchor"]
+    NA["Network Authority<br/>invite enrollment, certs, CRLs, policy"]
+    A["Node A"]
+    B["Node B"]
+    C["Node C"]
+
+    RS -->|"signs genesis"| NA
+    NA -->|"invite token + join certificate"| A
+    NA -->|"invite token + join certificate"| B
+    NA -->|"invite token + join certificate"| C
+
+    A <-->|"Noise XX encrypted peer session"| B
+    B <-->|"Noise XX encrypted peer session"| C
+    A <-->|"Noise XX encrypted peer session"| C
+
+    NA -.->|"signed CRL bootstrap"| A
+    A -.->|"CRL gossip"| B
+    B -.->|"CRL gossip"| C
+```
+
+At a high level, the Network Authority admits identities and publishes trust
+state. Nodes use that state to communicate directly, route messages, and reject
+revoked peers.
+
+## Documentation
+
+[Documentation Website](https://genesismesh.connectorzzz.com)
+
+## Requirements
+
+- Python 3.12 or later
+- See `requirements.txt` for pinned runtime dependencies
+
+## Installation
+
+```bash
+python -m venv .venv
+source .venv/bin/activate   # PowerShell: .\.venv\Scripts\Activate.ps1
+pip install -r requirements.txt
+pip install -e .
+```
+
+## Quick Start
+
+The local workflow runs the NA in one terminal and joins a node in a second.
+
+```bash
+# Create keys, genesis block, and CLI config (one time).
+genesis-mesh init
+
+# Start the Network Authority (keep this terminal open).
+genesis-mesh na start
+
+# In a second terminal: create a single-use invite and join.
+INVITE_TOKEN=$(genesis-mesh admin invite --role anchor)
+genesis-mesh join --na http://127.0.0.1:8443 --token "$INVITE_TOKEN"
+
+# Inspect NA health and node certificate state.
+genesis-mesh status
+```
+
+PowerShell:
+
+```powershell
+$INVITE_TOKEN = genesis-mesh admin invite --role anchor
+genesis-mesh join --na http://127.0.0.1:8443 --token $INVITE_TOKEN
+```
+
+Full local smoke test:
+
+```bash
+genesis-mesh dev up
+```
+
+## Production Deployment
+
+Container startup uses `start.sh` and Gunicorn. Set `SERVICE_ROLE=na` for the
+Network Authority or `SERVICE_ROLE=node` for a peer node. The NA role requires
+two mounted secrets and fails closed if either is absent:
+
+| Environment variable      | Description                                      |
+|---------------------------|--------------------------------------------------|
+| `SERVICE_ROLE`            | `na` or `node`                                   |
+| `GENESIS_FILE`            | Path to the signed genesis block                 |
+| `NA_PRIVATE_KEY_FILE`     | Path to the NA Ed25519 signing key (NA role)     |
+| `OPERATOR_PUBLIC_KEYS_JSON` | JSON map of operator key IDs to public keys   |
+| `DB_PATH`                 | SQLite database path (default: `genesis_mesh_na.db`) |
+| `PORT`                    | Bind port (default: `8443`)                      |
+| `WEB_CONCURRENCY`         | Gunicorn worker count (default: `4`)             |
+
+The NA private key never leaves the NA process.
+
+Health and readiness probes are available at `/healthz` and `/readyz`.
+
+## Deployment Examples
+
+Genesis Mesh includes deployment examples for:
+
+- **Local process** — `genesis-mesh init && genesis-mesh na start`
+- **Docker** — `docker run` and Docker Compose (`docs/examples/compose/`)
+- **Kubernetes** — manifests under `examples/kubernetes/`
+- **Terraform on Azure** — `infrastructure/azure/`, the same module used by the live deployment
+
+See the [deployment guide](https://genesismesh.connectorzzz.com/operations/deployment.html) for the full walkthrough.
+
+## Repository Layout
+
+```
+.
+  Dockerfile              Container image definition
+  start.sh                Container entry point (NA and node roles)
+  requirements.txt        Pinned runtime dependencies
+  setup.py                Package metadata and entry points
+  docs/                   Sphinx documentation source
+  examples/               Demo workflows, sample genesis blocks, Kubernetes manifests
+  genesis_mesh/           Python package
+  infrastructure/         Terraform, Azure scripts, and operational tools
+```
+
+```
+genesis_mesh/
+  audit/                  Tamper-evident security audit logging
+  cli/                    High-level and low-level CLI commands
+  crypto/                 Ed25519 signing and key management
+  gossip/                 CRL gossip protocol
+  models/                 Genesis, certificate, policy, CRL, and enrollment models
+  monitoring/             Prometheus metrics and health checks
+  na_service/             Network Authority REST API and WSGI entry point
+  node/                   Node client, runtime, discovery, RBAC, and control plane
+  routing/                Routing table, protocol, and message forwarding
+  tests/                  Unit and integration tests
+  transport/              WebSocket transport, Noise XX, protocol framing, and connections
+```
+
+## Testing
+
+```bash
+python -m pytest genesis_mesh/tests -v
+```
+
+## Security
+
+To report a vulnerability, open a GitHub Security Advisory on this repository.
+Do not file a public issue for security-sensitive findings.
+
+## License
+
+[MIT](LICENSE)

genesis_mesh-0.5.0/genesis_mesh/__init__.py

@@ -0,0 +1,3 @@
+"""Genesis Mesh - Secure decentralized mesh networking with cryptographic trust chains."""
+
+__version__ = "0.1.0"

genesis_mesh-0.5.0/genesis_mesh/audit/__init__.py

@@ -0,0 +1,5 @@
+"""Audit logging for security events."""
+
+from .logger import AuditLogger, AuditEvent, EventType
+
+__all__ = ["AuditLogger", "AuditEvent", "EventType"]