A token is a ~30-byte attributed name for an artifact. Mint one for a file, hand off the one-line reference instead of the contents, and the consumer pulls only the slices it needs — grep and windowed reads through the token, under byte budgets. Every stage lands in a payload-free event log: who resolved, who read, who ran, what stalled. Corrections and revocations travel through the reference to every holder.
The full case — the handoff problem, the bee that solved it, the
architecture at all three radii — lives in
the essay and
WHY.md. The systems-paper treatment, The Dance and
the Field: Name Semantics for Handoffs Between Distributed Agents, is in
paper/ (build with tectonic waggle.tex; the latest CI
build is attached to the
paper-latest
release).
Install & first handoff
# → { "token": "b2uQyZUC",
# "handoff": "resolve b2uQyZUC via waggle for your working context" }
just demo runs the whole arc against a throwaway store. The
documentation map holds the eleven guides in
reading order — five-minute loop, harness wiring, federation, the
Cloudflare edge, the tmux switchboard.
Status
v0.1.0 on crates.io; the 0.3
feature set is complete on main — the full verb loop, snapshots,
federation, the edge tier, Ed25519 trust, the spec with conformance
vectors, and the tmux switchboard. Every claim is a passing test in CI
(three-OS matrix + wasm + live Miniflare edge; ~170 tests). Measured
numbers live in benches/PERF.md.
In design: interrogation telemetry — convergence classification of consumer traces, receipt-driven model routing, and distilling accepted reading paths into scaffolds for weaker model families. This README will be rewritten around the implemented system when that work lands (P5 of the plan).
License
MIT OR Apache-2.0, at your option.