Skip to content

waggle 0.3.0 — the substrate at every radius

Choose a tag to compare

View all tags
@conikeec conikeec released this 08 Jul 22:47
v0.3.0
9d29956

The reference, now working at every radius — one machine, many machines, and Cloudflare's edge — with trust underneath and a spec on top.

Since 0.1.0

  • Surgical content access: mint --snapshot pins bytes content-addressed; search and read work through the token under byte budgets — the grep travels, the artifact stays. Markdown/JSON lenses; the format boundary for binary artifacts.
  • The daemon, managed: waggle daemon start|stop|restart|status|purge — no orphans, race-safe binds, idle exit.
  • Federation: daemon-to-daemon over token-gated TCP and HTTPS upstreams; --level strict (revocations bite now) vs eventual (the author's declared freshness window); the plain CLI transparent through every tier.
  • The edge: a Durable Object per tenant running the same certified engine on Cloudflare Workers; R2 snapshot blobs; the KV unfurl cache with revocation-aware invalidation; waggle edge status|push|smoke. The full E1–E13 completeness matrix runs in CI (Miniflare) and was verified end-to-end against a real account — mint on a laptop, grep on Cloudflare.
  • Trust: Ed25519 signatures over the manifest's immutable core (lifecycle mutations never invalidate — by construction); waggle identity; resolve reports signature status; --private capability-URL tokens.
  • The spec: normative document + conformance vectors generated from the implementation and drift-checked in CI.
  • Fluency hardening: every operation's envelope reports what it cost (mechanically enforced); guides 06–10; the documentation map; the WHY essay.

Full local loop → federation → edge: ~170 tests, three-OS + wasm + live-edge-matrix CI, all measured numbers in PERF.md.

Assets 2
Loading