Weft Federation ~/weft
Authoritative · interop layer · documentation only

Distinct threads,
woven on purpose.

Weft Federation is an agent-first family of small, local-first developer tools. Each member is authoritative for one domain, useful on its own, and meaningfully composable with any sibling — enrich-only, never load-bearing when composed.

The federation axiom
Each member is authoritative for one domain, solo-useful, meaningfully composable pairwise, and enrich-only — never load-bearing — when composed.
5 realized members local-first · no cloud no runtime · no broker · no store Shuttle — roadmap
The roster — click to expand
Answers “what is this codebase, where do I touch, what is the durable identity?” github.com/foundryside-dev/clarion
Answers “what work exists, what state is it in, what happened?” github.com/foundryside-dev/filigree
Answers “what is allowed, and does this still satisfy the constraints?” github.com/foundryside-dev/wardline
Answers “what changed, and is this change governed?” github.com/foundryside-dev/legis
Answers “what must be true, and how do we know it is?” github.com/foundryside-dev/charter
Answers “carry this approved change through the weave, under guard rails.” no repo yet — roadmap thought-bubble
Adjacent — not a member
Lacuna demo suite A separate sample codebase, seeded with deliberate bugs — point the Weft tools at it and they pick them up. github.com/foundryside-dev/lacuna
Product cheat-sheets

Each realized member has a curated cheat-sheet — what it does, how to use it, how it composes, and a short snapshot of its most-used commands. The full reference stays in each repo.

Loomweave Rust Code structure + identity authority (SEI) Turns a codebase into a queryable, identity-stable graph an agent reads instead of grepping — and mints the SEI every binding keys on. Cheat-sheet → Filigree Python Work state / issue lifecycle Turns a swarm of stateless agents into a coordinated workforce — race-free work claims, a dependency-aware ready queue, pre-computed orientation. Cheat-sheet → Wardline Python Trust-boundary analysis Answers, statically, whether the data each trust-annotated function works with is as trusted as it claims — a semantic-tainting analyzer with SARIF output. Cheat-sheet → Legis Python Git/CI governance & attestations Makes every governed action at the git/CI boundary produce one attributable, tamper-evident audit record, and grades who must answer server-side. Cheat-sheet → Charter Python Requirements, traceability, verification The obligations system-of-record — what must be true, kept separate from proposed or stale guesses, with how each is verified and when it goes stale. Cheat-sheet →

Shuttle is a roadmap thought-bubble, not a realized member — it has no cheat-sheet. See the product index for how each cheat-sheet is structured.

The composition law

Any member must satisfy all three modes. Pairwise composability is a hard rule, not an aspiration.

Combined with any one sibling it creates a meaningful capability — Wardline findings become tracked Filigree work; never a broken fragment.

How they compose

Every binding is enrich-only and keys on one durable identity. Remove any sibling and the others' core flows keep working — two structural facts hold the weave together.

The connective tissue
SEI — Stable Entity Identity
One durable id per code entity, owned by Loomweave. Every cross-tool binding keys on it, so a link survives a rename tomorrow. LOCKED · 2026-06-05
The transport
Filigree’s weft HTTP generation
Siblings pin to a named, versioned API surface. Evolution is additive — a new generation, never a mutation of the old one.
Representative bindings

Full 5×5 matrix in federation-map. Two named asterisks tracked in asterisk-register.