Skip to content
Pilox
Access

Docs_archive

Planetary product (P1–P3)

Source docs/MESH_PLANETARY_PRODUCT.md · All_docs

Objective: describe what is shipped as a minimal P1–P6 product reference (discovery, edge, WAN bus → Hive, directory sync, trust hook, WAN traces), without conflating it with a production Internet-scale deployment (DHT, VC, full chart).

P4–P6 milestones (repository reference)

The "complete" milestones in the vision sense MESH_V2_GLOBAL.md (libp2p DHT, verified DID/VC, multi-region SLO) remain largely roadmap. This repository provides documented reference implementations:

Scroll horizontally →
MilestoneShipped here (stub / ref.)Not covered
P4Pull sync (REGISTRY_SYNC_*), outbound auth (REGISTRY_SYNC_AUTH_BEARER), proof verification on merge (REGISTRY_SYNC_VERIFY_ED25519_PROOF), read RL + protected catalog — see MESH_PLANETARY_P4_FEDERATED_SYNC.mdDHT, gossip, public NAT relays, "Internet scale" catalog trust
P5proof, Ed25519 (GET/POST + sync), Postgres, optional PDP-lite on POST (REGISTRY_POST_*_ALLOWLIST), optional VC-JWT gate + multi-tenant registry — MESH_PLANETARY_P5_TRUST_PROOF.md, MESH_REGISTRAR_SAAS_VC.mdFull JSON-LD VC lifecycle, SD-JWT, status lists, enterprise PDP products (OPA/Cedar SaaS)
P6traceparent propagation bridge → NATS → subscriber → ingress — see MESH_PLANETARY_P6_WAN_TRACE.mdSLO, mandatory inter-region dashboards
K8s opsHelm gateway + bridge + registry — index deploy/helm/README.md; assembly guide MESH_WAN_COMPLETE_DEPLOYMENT.md; gateway detail (HPA/PDB, metrics, …) deploy/helm/hive-mesh-gateway/README.mdManaged WAF SKUs, full multi-region SLO program

Executive summary

Scroll horizontally →
LayerStatusRole
P1 DirectoryStub + schema + DockerRead + POST / DELETE, RL, catalog Bearer, signed catalog, validUntil, Postgres, POST allowlists (handle / agent-card host).
P2 GatewayStub + DockerJSON-RPC proxy + upstream auth + optional TLS / mTLS on the listener + UA guard + security headers.
P3 TransportBridge + subscriber + Hive ingressNATS (core or JetStream); validated envelope; closed loop: subscriber → POST /api/mesh/wan/ingress → Redis hive:system:events (mesh.wan.envelope).
P4–P6 (ref.)Directory sync + proof + WAN tracesSee table § P4–P6 milestones above; not equivalent to production DHT / VC / SLO.
Hive coreRoute + Zod + existing busAuthenticated operator edge workers (or HIVE_INTERNAL_TOKEN) republish on the same bus as system events.

Machine contracts

What remains "out of product" (next waves)

  • Production registry: write quotas / rate limit, audit, multi-tenant, registrar SLA (Bearer write + optional Postgres is a foundation, not a complete registrar product).
  • Production gateway: TLS termination, WAF, distributed quotas, mTLS to Hive.
  • Multi-region NATS topology, named durable consumers, DLQ.
  • Business consumers on mesh.wan.envelope: Redis publish; reference npm run mesh:wan-worker (JSON line to stdout or Bearer webhook) — additional business logic in other subscribers or integrations.

Quick start