Weft

The old web ships instructions and hopes; the Thread ships intent and verifies. Weft is not a nicer syntax or a faster bytecode — it is the decision that what crosses the wire stays semantic: a typed, total, effect-explicit, content-addressed program graph, verified as-is by the receiver, compiled locally into whatever each machine runs best.

Why it can work this time

• Nervous system, not muscles. Weft never sits in a frame or vertex path — rendering belongs to the browser's native loop. A conformant browser MUST NOT need Weft to produce a frame. The performance bet doesn't depend on the language.
• WASM stays as the floor. Any language targets the Thread through the public Behavior ABI. Weft is the native path, never a wall.
• Built for the agent era. Weft has no source text — the canonical form is a verified graph; human-readable projections are derived, in any style or language. Its target author is the coming world where software writes software, and what machines exchange is contracts, not diffs.

Packages: hashes that can't move

A weft-pack distributes content-addressed definitions — identity is the hash of canonical bytes. Unpublishing can't break you (anyone holding the bytes holds the truth), version conflicts dissolve into set-union, typosquatting has nothing to squat (names are local petnames), and a registry is just a static file host — there is no publish endpoint to breach:

{
  "name": "weft-form",
  "exports": { "ring": "weft:9e3d…", "lerp": "weft:834f…" },
  "defs":    { "weft:9e3d…": { …definition… }, "weft:834f…": { …definition… } }
}

Verification is local and total: a conformant tool refuses a package where any hash doesn't match its bytes, any export dangles, or the definitions fail the verifier.

Where it stands, honestly

• Reference implementation in progress inside the Infinite workspace: canonical encoding + content addressing, a verifier with transitive effect rows and static fuel bounds, contracts, and a deterministic reference interpreter.
• First packages exist (a geometry vocabulary and a motion vocabulary) and are being wired into live worlds through the Behavior ABI.
• The weft & weft-pack spec drafts are graduating into the public thread-spec repo; the CLI tooling is not yet on crates.io. When those land, this page will say so — nothing here will ever claim more than what you can verify.

Want in early? Start by shipping a world (build page) — behaviors via the WASM ABI work today, and Weft will meet you where you already are.