weft

pre-1.0

Local-first infrastructure for coding agents: one seam — a shared identity spine and hub-blessed joins — supported by six small tools, each authoritative for exactly one concern.

Cross-member joins are authored at the hub, so no member quietly becomes load-bearing for another.

weftRust · PythonMIT
What it is

The unit of value is the federation, not the member. The seam — the shared SEI identity spine plus honest, hub-blessed joins — is the part that matters; the roster is a supporting, open-ended suite and a snapshot rather than the identity. Provenance-honesty is a hard admission gate: no result is emitted without its cause, reason_class and fix. weft itself is the interop layer — documentation and contracts, no code and no runtime. There is nothing called weft to install; you install the members.

The one sentence
the federation axiom
Each member is authoritative for one domain,
solo-useful, meaningfully composable pairwise,
and enrich-only — never load-bearing — when composed.
The roster — six admitted members
loomweaveRustCode structure, and the SEI identity authority every other member keys on.
filigreePythonWork state and issue lifecycle — race-free claims and a dependency-aware ready queue.
wardlinePythonTrust-boundary and taint analysis. Silent until you decorate — silence is not a clean bill.
legisPythonGit and CI governance. A discipline, not a hardened security boundary.
warplinePythonTemporal change-impact, keyed on the SEI spine. Advisory only; it never gates.
plainweavePythonCode-grounded intent — a node with no upward edge to a requirement is a reviewable question.

lacuna is not a member — it is the deliberately-flawed specimen the suite is run against. The roster is designed to grow; the count is never the thesis.