| Filename | Latest commit message | Latest commit date |
|---|---|---|
d14f583d92
The repository tracks the latest stable Rust, pinned at the root. A
`rust-version` key states a *floor* -- the oldest toolchain a crate supports --
which is a different promise, and one this repository does not make. It also
said 1.97 while the pin was 1.98.0 and nothing verified it, so it was a claim in
the wrong direction and unchecked in both.
So it goes, everywhere:
59 rust-version = "1.97" (workspace and package declarations)
417 rust-version.workspace = true (members inheriting them)
476 files, 476 deletions, 0 insertions
The 417 are why this is not the sixty-file change it looks like from a grep for
the value. A member inheriting a key that no longer exists does not fall back to
a default -- its manifest stops resolving. Removing the declarations without the
inherits would have broken every workspace that has members.
Deliberately untouched: `joule-code-rs/vendor/wtransport/Cargo.toml`. That is a
vendored third-party crate declaring a floor about itself, not about us, and our
pin is above it. Editing vendored source to satisfy our own policy would make
the copy diverge from upstream for no benefit.
Verified rather than assumed:
- all 493 `Cargo.toml` files in the tree parse (`tomllib`)
- `cargo metadata --no-deps --locked` resolves on `joule-code-rs`, `wai-rs`,
`openpay`, `mesh-rs`, `sandbox-rs` and `jcp-rs` -- the check that actually
exercises workspace inheritance, which a TOML parse does not
- no `Cargo.lock` changed; `rust-version` is not lockfile state
`wai/wai-verify/Cargo.toml` already carried a comment saying it omits
`rust-version` on purpose, so this makes the rest of the tree agree with the one
crate that had already decided.
What this gives up, stated plainly: cargo can no longer greet an older
toolchain with "requires rustc 1.97" and will instead fail wherever the code
first needs something newer. That is the cost of not maintaining a floor, and
it is the right cost when the floor was fiction.
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| e2e | ||
| src | ||
| templates | ||
| web | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
wai-app
WAI's widgets for joule-ui, and Create: describe a WAI app, watch it build itself
from WAI widgets while a model writes it, try its room, and take it away as a project. A
library with no binary of its own: wai, built with its feature app, is its command line
and its MCP server. The design is in joule-ui/docs/create.md;
the line language a model writes the app in is joule-ui's (joule-ui/SPEC.md §11).
The widgets
A joule-ui registry (src/registry.rs), each widget backed by the room client of
joule-moq-web (web/components.js):
| Widget | What it is | Holds |
|---|---|---|
App(children, title) |
the app | one room; Text, Receipts, EnergyMeter |
Room(children, title) |
a live room: join with camera and microphone, or watch | Player, Chat, and any room's widgets |
WatchTogether(source, children, title) |
a watch room: one file, watched in sync | any room's widgets (a watch room keeps the shared controls alone) |
Show(children, title, audience) |
a show: hosts on camera, an audience that votes | Player, Chat, Poll, and any room's widgets |
Player(title) |
the room's video, laid out from its signed record | |
Chat(title) |
the room's chat, each message a signed, verified event | |
Poll(question, options, seconds) |
a vote the show's lead opens and its clock closes and signs | |
Participants(title) |
who is present, from the room's lifecycle | |
Receipts(title) |
the page's sealed log of every action, verified | |
EnergyMeter(title) |
each action's energy, and how it was obtained | |
Text(text) |
a paragraph |
Any room's widgets: Participants, Receipts, EnergyMeter, Text. An app holds one
room; a poll has 2 to 32 options; a show's audience is 1 to 255; a watch room's source is
a file within the app (src/plan.rs). A line that breaks a rule is refused with its line
and a reason code, and does not render.
The pieces
src/guide.rs: what a model is told before it writes an app, made from the registry (wai app guide, the toolapp_guide).src/lib.rs:checkandCreate, a program as a snapshot the page renders, whole or as it streams, with the room the app needs (wai app check, the toolapp_check).src/export.rs: the files of a starter project for a program, and the facts its project file holds:app.oui,index.html,README.md,AGENTS.md,.gitignore,vendor.json,vendor/(the runtime), and for a watch roommedia/README.md.wai create <dir> --from app.ouiwrites them, withwai.jsonandLICENSEfrom the writer everywai createproject has. No key is ever in it:wai devmakes development keys in.wai/at run time.src/runtime.rs: the runtime an export carries, read by its listing (create/wai-app-runtime.json) and checked file by file.src/bridge.rs: the bridge on 127.0.0.1 that carries a program from a coding agent into the person's open Create page (wai mcp --toolset app, the toolapp_stream).src/web.rs(featureweb): the page's WebAssembly surface, with the interaction log every action on the page is sealed into (joule-ui-interaction).web/: the streaming renderer, the components, the room frame, the Create page and the exported app's page;web/runtime.mjslays the runtime out as the site serves it.
Run it
cargo test # registry, plan, guide, export, runtime, bridge
node --test web/web.test.mjs # the renderer and the model streams
e2e/run.sh # Create in a browser, with wai dev, wai create --from and wai app check
wai app guide # what a model is told (wai built with --features app)
wai app check app.oui # a program's tree, errors and room
wai create my-app --from app.oui --runtime <dir> # a starter project; then wai app check and wai dev in it
wai mcp --toolset app # Create's tools, for a coding agent
Licence
Apache-2.0, and every project wai create writes from an app is too.