tawasuyu/llimphi

Sovereign retained-mode GPU UI framework in Rust (wgpu+vello+taffy+parley), Elm loop, 40+ widgets.

Rust 229TOML 101Markdown 82Shell 24052 Definitions

Clone over HTTPS, with plain git

⎇ main llimphi-wasm-registry/README.md Markdown · 24 lines · 1.0 KB History raw

chore: refresco desde el monorepo — 27 crates nuevos (anim, lottie, svg, mesh, image, layer, test, wire-view, widgets rag-sidebar/router/lazy-list/rive-button) y sync de los 95 existentes 93253cc22 · Sergio · 2 months ago

1# llimphi-wasm-registry
2
3Data-driven bridge to public WASM app registries.
4
5Our own catalog (`llimphi-wasm-core::Catalog`) answers "which apps exist" over the
6sovereign mesh. This crate opens the other door: **connecting to registries that
7already exist on the internet** (wasmer/WAPM, a static index, anything
8REST+JSON) agnostically and configurably, so there are real catalogs to test
9against without publishing anything first.
10
11The bet is the same as `shared/foreign-platform` (whose pattern it copies): a
12**RON descriptor** describes the listing endpoint and the domain-field →
13JSON-path mapping; adding a compatible registry means writing a `.ron`, not Rust.
14
15## Honest scope
16
17This brings **metadata plus a download URL** per app, and `ingest` fetches the
18module and turns it into a resolvable `CatalogEntry` (hashing it into the CAS —
19that is where the bytecode hash comes from, same as `--install`). What it does
20**not** guarantee is that any given module follows the Tier 3 ABI.
21
22---
23
24Part of **llimphi** — see [llimphi](../README.md).

README.md

llimphi-wasm-registry

Data-driven bridge to public WASM app registries.

Our own catalog (llimphi-wasm-core::Catalog) answers "which apps exist" over the sovereign mesh. This crate opens the other door: connecting to registries that already exist on the internet (wasmer/WAPM, a static index, anything REST+JSON) agnostically and configurably, so there are real catalogs to test against without publishing anything first.

The bet is the same as shared/foreign-platform (whose pattern it copies): a RON descriptor describes the listing endpoint and the domain-field → JSON-path mapping; adding a compatible registry means writing a .ron, not Rust.

Honest scope

This brings metadata plus a download URL per app, and ingest fetches the module and turns it into a resolvable CatalogEntry (hashing it into the CAS — that is where the bytecode hash comes from, same as --install). What it does not guarantee is that any given module follows the Tier 3 ABI.

Part of llimphi — see llimphi.