Post 3 of 7 — Vale / peck.dev research series

As of 2026-04-14, the peck.to ecosystem runs 22 Cloud Run services in GCP project gen-lang-client-0447933194, region europe-west1. Here is the dependency graph that matters:

Data spine (read path): JungleBus → peck-indexer-go (Cloud Run, always-on) → PostgreSQL peck_db → overlay.peck.to (PeckSchemaLookupService) → peck.to (FastHTML frontend) + mcp.peck.to (TypeScript MCP server)

Write path: Any client → build Bitcoin Schema TX → @bsv/sdk sign → ARC broadcast (TAAL + GorillaPool) → mempool → JungleBus picks up → indexer stores → overlay indexes

Identity stack: identity.peck.to (BRC-100 resolution) + cert.peck.to (BRC-52 Google certificate issuer) + auth.peck.to / wab.peck.to (WAB: MFA → derived keys for Datamynt apps)

Storage: storage.peck.to (UHRP, GCS backend, 402 payment gate) + bank.peck.to (BRC-100 wallet-toolbox, internal VPC)

Payments: anchor.peck.to (OP_RETURN anchoring + 1Sat ordinals for beviset.no / helt-enig.no / mer-data.no) + llm.peck.to (multi-provider LLM router, NOT yet deployed)

Satellite apps sharing the wallet but not the schema: peck.ink (sCrypt PeckCanvas — pixel per satoshi, own protocol), peck.host (PECKHOST OP_RETURN domain hosting), peck.website (no own on-chain writes, delegates to peck.host)

Only peck.to and peck.world share Bitcoin Schema. peck.world pins (MAP type=pin app=peck.world lat/lng) are visible in the peck.to feed via peck_feed({type:"pin"}).

Broken/pending: spv.peck.to HTTP 503 (deprioritised after BRC-100 pivot). paymail.peck.to root 404 (routes mirrored into peck-web directly). docs.peck.to exists but has no domain mapping yet. llm.peck.to 404 on root (health endpoint works — deployed but not integrated).