Pelagora 0.9 — mesh upgrades and Schema.org improvements

Release summary

Pelagora 0.9 ships a major upgrade to the mesh routing layer, expands Schema.org support, and introduces the new pelagora.md v2 Skill format. Here's what changed.

Mesh routing — faster peer discovery

Previous versions used a naive flood-fill for initial peer discovery: a new Beacon would broadcast to all known peers and wait. On a large mesh, this caused noticeable startup lag.

0.9 switches to iterative Kademlia lookup. The Beacon now queries the 3 peers closest to its own ID, refines the result set, and converges in O(log n) hops instead of O(n).

Benchmark on a 500-node testnet:

| Metric | 0.8 | 0.9 | |--------|-----|-----| | Time to first peer | 4.2s | 0.8s | | Peers found in 10s | 12 | 41 | | Bandwidth on startup | 2.4 MB | 0.3 MB |

Expanded Schema.org types

Listings now support the full Schema.org Product hierarchy, not just Offer. This means your Beacon can advertise richer metadata:

{
  "@type": "Product",
  "name": "Patagonia Black Hole Duffel 55L",
  "brand": { "@type": "Brand", "name": "Patagonia" },
  "offers": {
    "@type": "Offer",
    "price": "85.00",
    "priceCurrency": "USD",
    "itemCondition": "https://schema.org/UsedCondition"
  }
}

AI agents browsing the mesh can now filter by brand, condition, and product category without any custom parsing.

Skill format v2

The new pelagora.md v2 format adds a machine-readable frontmatter block:

---
skill: pelagora-setup
version: 2.0.0
requires:
  node: ">=18"
  beacon: ">=0.9.0"
---

This lets agents validate compatibility before executing — no more mid-install failures on older Beacons.

Upgrade

npx create-reffo-beacon@latest update

Or grab the new pelagora.md and hand it to your agent — it will detect the existing installation and upgrade in place.

What's next

0.10 will focus on escrow primitives and multi-party negotiation. Follow along on GitHub or join the community discussions.