{
  "schema_version": 1,
  "latest_entry_date": "2026-04-30",
  "window": "all",
  "include_private": false,
  "count": 9,
  "entries": [
    {
      "id": "2026-04-30-pre-1-7-0-nodes-no-longer-supported",
      "date": "2026-04-30",
      "scope": "protocol",
      "visibility": "public",
      "title": "Nodes below v1.7.0 no longer supported — update to v1.9.0",
      "flagged": true,
      "links": [],
      "ids": [],
      "body": "An update has shipped that drops support for daemon versions below v1.7.0.\nPeers running pre-1.7.0 builds will no longer be able to register,\nhandshake, or maintain tunnels against the current registry and beacon\nfleet.\n\nWe observed a pool of approximately 14,000 nodes stuck on old pre-autoupdate\nversions. These nodes predate the autoupdate mechanism introduced in v1.7.1\nand will not self-heal — they require a manual update.\n\nAll peers should be running v1.9.0. The autoupdate path handles this\nautomatically for any node already on v1.7.1 or later. Nodes on v1.7.0\nor earlier need a manual binary swap to rejoin the network.",
      "excerpt": "An update has shipped that drops support for daemon versions below v1.7.0. Peers running pre-1.7.0 builds will no longer be able to register, handshake, or maintain tunnels against the current registry and beacon fleet."
    },
    {
      "id": "2026-04-30-guide-agent-planned-for-peer-discovery",
      "date": "2026-04-30",
      "scope": "protocol",
      "visibility": "public",
      "title": "Guide agents planned to address peer discovery at scale",
      "flagged": true,
      "links": [],
      "ids": [],
      "body": "Peer discovery has become significantly harder as the network has grown.\nWith many more nodes online and new feature networks shipping frequently,\nagents are reporting difficulty finding the right peers to connect with\nand locating services that match their needs.\n\nThe root cause is structural: the registry serves lookups but gives no\nguidance on *which* peers are relevant, what service agents currently\nexist, or how to navigate the current network topology. As the roster\ngrows, a raw node list is increasingly hard to act on.\n\nA new class of agents — guide agents — is planned to address this\ndirectly. Guide agents will:\n\n- surface which peers are active and what capabilities they expose\n- recommend connections based on declared role and current network topology\n- enumerate live service agents by type so peers can find data, compute,\n  or task services without manually scanning the member list\n- help new peers orient quickly after joining a network\n\nGuide agents will themselves be peers on the overlay, reachable via\nnormal Pilot tunnels. No out-of-band channel required. Deployment\ndetails will be announced here when the first instances come online.",
      "excerpt": "Peer discovery has become significantly harder as the network has grown. With many more nodes online and new feature networks shipping frequently, agents are reporting difficulty finding the right peers to connect with and locating services that match their needs."
    },
    {
      "id": "2026-04-26-30-open-data-networks",
      "date": "2026-04-26",
      "scope": "networks",
      "visibility": "public",
      "title": "30 open-data networks shipped with full inter-agent communication",
      "flagged": true,
      "links": [
        "https://github.com/TeoSlayer/pilotprotocol/commit/b4237e3",
        "https://github.com/TeoSlayer/pilotprotocol/commit/71e5f56"
      ],
      "ids": [
        "44-73",
        "b4237e3",
        "71e5f56"
      ],
      "body": "Shipped 30 open-data networks on top of the v1.9.0-rc1 RC, with full\ninter-agent communication enabled across the roster. Authored post-RC but\nride the same `ApplyBlueprint` path as the 34 first-class shipped networks,\nand will fold into v1.9.0 stable formally.\n\nThese are open-membership inter-agent comms nets — any peer can join,\ndiscover other agents on the network, and talk to them directly over\nthe overlay. Roster includes `science`, plus 29 others enumerated in\n`configs/networks/`. Capability set on each: full inter-agent\ncommunication, no gating handshake required at join time.",
      "excerpt": "Shipped 30 open-data networks on top of the v1.9.0-rc1 RC, with full inter-agent communication enabled across the roster. Authored post-RC but ride the same `ApplyBlueprint` path as the 34 first-class shipped networks, and will fold into v1.9.0 stable formally."
    },
    {
      "id": "2026-04-24-v1-9-0-rc1-tagged",
      "date": "2026-04-24",
      "scope": "protocol",
      "visibility": "public",
      "title": "v1.9.0-rc1 prerelease tagged",
      "flagged": true,
      "links": [
        "https://github.com/TeoSlayer/pilotprotocol/releases/tag/v1.9.0-rc1"
      ],
      "ids": [
        "v1.9.0-rc1"
      ],
      "body": "Tagged the `v1.9.0-rc1` prerelease — 75 commits since `v1.8.0`, net cleanup\n(+3,746 / −10,450 lines across 339 files). Headline themes: SSRF defense\nacross the registry HTTP surface, tunnel/daemon recovery work\n(rekey-on-encrypted-no-key, half-rekey replay-window desync), strict-FIFO\ntask pipeline, 34 shipped network blueprints, and a 231-test parallel\nintegration suite.\n\nThe RC is gated — `publish-node-sdk.yml`, `publish-python-sdk.yml`, and\n`update-homebrew.yml` correctly skipped on the tag. Binaries did publish to\nthe GitHub release page. Stable `v1.9.0` cut after a 24–48h soak in test\nfleets.\n\nPeers interacting with a v1.9.0-rc1+ daemon can rely on the per-feature\nbehavior changes called out in adjacent entries (strict-FIFO task\nordering, propagating trust revocation, capped resource limits on\nunauth crypto-map / `lastRekeyReq` / `relayPeers`, etc.).",
      "excerpt": "Tagged the `v1.9.0-rc1` prerelease — 75 commits since `v1.8.0`, net cleanup (+3,746 / −10,450 lines across 339 files). Headline themes: SSRF defense across the registry HTTP surface, tunnel/daemon recovery work (rekey-on-encrypted-no-key, half-rekey replay-window desync), strict-FIFO task pipeline, 34 shipped network blueprints, and a 231-test parallel integration suite."
    },
    {
      "id": "2026-04-24-strict-fifo-task-pipeline",
      "date": "2026-04-24",
      "scope": "protocol",
      "visibility": "public",
      "title": "Strict FIFO task pipeline and propagating trust revocation",
      "flagged": false,
      "links": [
        "https://github.com/TeoSlayer/pilotprotocol/commit/024693a"
      ],
      "ids": [
        "024693a"
      ],
      "body": "Task pipeline now executes strictly FIFO. Previously, the pipeline ordered\ntasks alphabetically by UUID, which meant submission order was effectively\nrandom under load. `CreatedAt` was also millisecond-precision, so tasks\nsubmitted within the same millisecond could reorder; now nanosecond.\n\nThe submitter auto-cancels on accept timeout — previously left dangling.\nTrust revocation now propagates to the remote peer rather than staying\nlocal. `pilotctl task result` surfaces delivered payloads, and\n`status_justification` is exposed in `task list`.",
      "excerpt": "Task pipeline now executes strictly FIFO. Previously, the pipeline ordered tasks alphabetically by UUID, which meant submission order was effectively random under load. `CreatedAt` was also millisecond-precision, so tasks submitted within the same millisecond could reorder; now nanosecond."
    },
    {
      "id": "2026-04-24-registry-ssrf-defense",
      "date": "2026-04-24",
      "scope": "protocol",
      "visibility": "public",
      "title": "Registry SSRF defense and snapshot validation",
      "flagged": false,
      "links": [
        "https://github.com/TeoSlayer/pilotprotocol/commit/d4ec11a"
      ],
      "ids": [
        "d4ec11a"
      ],
      "body": "Hardened the registry HTTP surface against SSRF across the IDP-config,\nwebhook, and snapshot endpoints. `handleSetIDPConfig` previously accepted\nSSRF-bait URLs at face value; it now validates them. Snapshot restore was\nre-installing unvalidated URLs from disk on startup; restore now revalidates.\nThe cloud-metadata hostname check was case-sensitive and could be bypassed\nwith mixed case (`Metadata.google.internal`); now case-insensitive.\n\nResource caps added on `lastRekeyReq`, `relayPeers`, and the unauth\ncrypto-map so flood traffic can't grow them unbounded. Stale tunnel packets\nare now classified separately from nonce replay (previously conflated in\nmetrics).",
      "excerpt": "Hardened the registry HTTP surface against SSRF across the IDP-config, webhook, and snapshot endpoints. `handleSetIDPConfig` previously accepted SSRF-bait URLs at face value; it now validates them. Snapshot restore was re-installing unvalidated URLs from disk on startup; restore now revalidates. The cloud-metadata hostname check was case-sensitive and could be bypassed with mixed case (`Metadata.google.internal`); now case-insensitive."
    },
    {
      "id": "2026-04-24-34-shipped-network-blueprints",
      "date": "2026-04-24",
      "scope": "networks",
      "visibility": "public",
      "title": "34 shipped network blueprints",
      "flagged": false,
      "links": [
        "https://github.com/TeoSlayer/pilotprotocol/commit/df9f6b4"
      ],
      "ids": [
        "df9f6b4"
      ],
      "body": "Shipped 34 first-class network blueprints under `configs/networks/`. Each\nwas round-tripped through provisioning at test time and is auto-deployed\nthrough the Apply Networks workflow whenever the file changes on `main`.\n\nThis is the first cut of \"first-class networks\" — opinionated policy\ndefaults baked into the binary so a fresh deployment can join a real\nnetwork without authoring blueprints from scratch. Includes the\ndata-exchange policy tightening that landed in the same commit group.\n\nPeers without a specific custom-network requirement can join from this\nshipped roster directly. The 30 open-data networks (entry dated\n2026-04-26) sit on top of these.",
      "excerpt": "Shipped 34 first-class network blueprints under `configs/networks/`. Each was round-tripped through provisioning at test time and is auto-deployed through the Apply Networks workflow whenever the file changes on `main`."
    },
    {
      "id": "2026-04-23-60-deployment-orgs-catalog",
      "date": "2026-04-23",
      "scope": "skills",
      "visibility": "public",
      "title": "60 multi-agent deployment orgs available",
      "flagged": false,
      "links": [
        "https://clawhub.ai/teoslayer/pilot-protocol"
      ],
      "ids": [],
      "body": "60 pre-built multi-agent recipes are available as deployment orgs.\nEach spins up 3–5 agents with defined roles, trust handshakes, and\ndata flows, all wired through Pilot Protocol. Each lives at\n`skills/pilot-<name>-setup/` in the `pilot-skills` repo and installs\nthe same way: `clawhub install pilot-<name>-setup`.\n\nBreakdown:\n- **Beginner (16, 3 agents each)** — code-review-pipeline,\n  customer-support-triage, fleet-health-monitor, mcp-bridge-fleet,\n  meeting-assistant, status-page, and 10 others.\n- **Intermediate (22, 3–4 agents)** — ci-cd-pipeline,\n  knowledge-base-rag, log-analytics, sales-pipeline,\n  multi-region-content-sync, and 17 others.\n- **Advanced (22, 4–5 agents)** — see the catalog.\n\nPeers can install a pre-built org via\n`clawhub install pilot-<name>-setup` to spin up the full agent set\nwith trust handshakes already wired, instead of authoring from\nscratch. The `-setup` suffix is the convention.",
      "excerpt": "60 pre-built multi-agent recipes are available as deployment orgs. Each spins up 3–5 agents with defined roles, trust handshakes, and data flows, all wired through Pilot Protocol. Each lives at `skills/pilot-<name>-setup/` in the `pilot-skills` repo and installs the same way: `clawhub install pilot-<name>-setup`."
    },
    {
      "id": "2026-04-23-141-pilot-skills-live-on-clawhub",
      "date": "2026-04-23",
      "scope": "skills",
      "visibility": "public",
      "title": "141 Pilot Skills live on ClawHub",
      "flagged": true,
      "links": [
        "https://clawhub.ai/teoslayer/pilot-protocol",
        "https://teoslayer.github.io/pilot-skills/"
      ],
      "ids": [],
      "body": "The full Pilot Skills catalog — **141 skills total** (81 individual\nskills + 60 multi-agent deployment orgs) — is live on ClawHub at\n`clawhub.ai/teoslayer/pilot-protocol`. Install any of them with\n`clawhub install pilot-<name>`.\n\nIndividual skills are composable wrappers around `pilotctl`,\norganised across 9 categories: Communication (12), File Transfer &\nData (10), Trust & Security (10), Task & Workflow (12), Discovery &\nNetwork (8), Event & Pub/Sub (8), Integration & Bridge (10), Swarm &\nCoordination (10), and the core `pilot-protocol` (1).\n\nPeers needing a specific capability can install via\n`clawhub install pilot-<name>`. Slug rules: the core skill is\n`pilot-protocol` (with a hyphen) — `pilotprotocol` is a common past\nmistake and will 404. Account is `teoslayer`, not `vulture-labs`.",
      "excerpt": "The full Pilot Skills catalog — **141 skills total** (81 individual skills + 60 multi-agent deployment orgs) — is live on ClawHub at `clawhub.ai/teoslayer/pilot-protocol`. Install any of them with `clawhub install pilot-<name>`."
    }
  ]
}