fuz_forge
apps and sites · early · Rust, Svelte
fuz_forge as this site sees it: what its repo's own files declare, and every record on the coherence and values pages that names it or links it. This page is computed and adds nothing of its own. For what the project is, see the Fuz stack page.
What it uses
| Uses | Kind | Declared in | Through |
|---|---|---|---|
| fuz | runtime | Cargo.toml(path) | fuz_actions, fuz_artifact, fuz_auth, fuz_cell, fuz_cell_actions, fuz_crypto, fuz_db, fuz_db_admin, fuz_fact, fuz_fact_serving, fuz_http, fuz_realtime, fuz_release, fuz_sign, fuz_storage, fuz_sys |
| blake3 | dev | package.json | @fuzdev/blake3-wasm |
| fuz_app | dev | package.json | @fuzdev/fuz_app |
| fuz_code | dev | package.json | @fuzdev/fuz_code |
| fuz_css | dev | package.json | @fuzdev/fuz_css |
| fuz_schema | dev | package.json | @fuzdev/fuz_schema |
| fuz_ui | dev | package.json | @fuzdev/fuz_ui |
| fuz_util | dev | package.json | @fuzdev/fuz_util |
| gro | dev | package.json | @fuzdev/gro |
| mdz | dev | package.json | @fuzdev/mdz |
| pglet | dev | package.json | @fuzdev/pglet-wasm |
| svelte-docinfo | dev | package.json | svelte-docinfo |
| zap | dev | package.json | @fuzdev/zap |
Read from the repos' manifests on . Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev. See every dependency in the stack.
What it declares from outside the stack
- runtime
- Cargo.toml: argh, axum, base64, deadpool-postgres, futures, futures-util, reqwest, serde, serde_json, subtle, thiserror, time, tokio, tokio-postgres, tokio-util, tracing, url, uuid
- peer
- package.json: @sveltejs/kit, svelte
Read from the repo on . What a repo's manifests declare from outside the stack, by name and without versions. The dev tables are left out, so what an app bundles from its dev table is not here. For a Cargo workspace the list is every crate's together, and it is what is declared, not what a release build links. A crate is left out as tooling only when it is named xtask or testing_*, or the release audit marks it dev-only, so what a bench, debug or test-support crate under another name uses is listed with the rest. See everything the stack declares.
Its check script and CI
The check script of its package.json:
gro check
Its CLAUDE.md has no line in a code block that gives gro check or npm run check with a # comment, and none whose comment says to run it before committing.
It may describe its checks another way.
It is among the repos whose check script runs gro check; with a CI step, on a push or a pull request, that runs gro check with --workspace; with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace; with a CI step, on a push or a pull request, that runs gro check with --build; with a Cargo workspace at the root.
.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch
rust on ubuntu-latest
- uses
actions/checkout, pinned to a commit - uses
actions/checkout, pinned to a commit - Install Rust
rustup toolchain install --no-self-update rustup show active-toolchain cargo --version
- uses
Swatinem/rust-cache, pinned to a commit - Format
cargo fmt -p fuz_forge -p fuz_forge_server -p fuz_forge_wire -p testing_fuz_forge_server -p xtask --check
- Clippy
cargo clippy --locked --workspace --all-targets -- -D warnings
- Test
cargo test --locked --workspace
- Test (Postgres)
cargo test --locked -p fuz_forge_server -- --ignored --test-threads=1
- Release dep-graph audit
cargo xtask check-release
- Rustdoc
cargo doc --locked --workspace --no-deps --document-private-items
ts on ubuntu-latest
- uses
actions/checkout, pinned to a commit - Use Node.js 24.14 uses
actions/setup-node, pinned to a commit -
npm ci
- gro check
npx @fuzdev/gro check --workspace --build
Read from the repo on . A workflow's jobs and steps are as the file writes them: a step's command, or the action it uses without its version. An action's inputs, a matrix's values, permissions, environment and working directories are left out, and nothing here says which command is the gate. A line is quoted when it sits in a code block of the repo's CLAUDE.md, has a # comment after the command, and either is the command gro check or npm run check, or has a comment that says to run it before committing. A repo that describes its check command in a sentence or a list, or in another file, has no line here. Every file is read at the repo's main branch as the checkout last fetched it, so nothing uncommitted or unpushed is here. See every repo's checks.
In the opening of the coherence section
Two of the stack's projects are made for that reading. zzz is for reading work on the maintainer's own machine, and its projects page shows each repo's uncommitted work and its distance from origin. fuz_forge is for commits that have landed: it shows a repo's commit log and its diffs to a reader, with no pull request to approve first.
From the coherence section's index.
Holds that name it
- In places: Tool: Drift checks and twin suites — Two copies drift apart
- In places: Person: Review after landing — Green but wrong
- In places: Written: Mark built from designed — A stale statement is trusted
- In places: Tool: Deny rules and dry runs — An unattended session does something irreversible
Comparisons that name it
| Compared | Against | Kind | Runs | Source |
|---|---|---|---|---|
| fuz_forge server, TypeScript | Its Rust server | Twin | Every change: shared case tables On demand: cross-backend suite | parity fixtures |
From Oracles in use.
Gates
- Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. fuz_forge is among the repos whose check script runs gro check.
- Drift in generated files (every change): A generated file that no longer matches its source. fuz_forge is among the repos whose check script runs gro check.
- Drift in the package exports map (ci): An exports map that no longer matches the source, which the local gate rewrites instead of failing on. fuz_forge is among the repos with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace.
- Build (ci): A broken build. fuz_forge is among the repos with a CI step, on a push or a pull request, that runs gro check with --build.
- A clean tree after the run, and no TODO docs at the root (ci): Uncommitted output and a TODO Markdown file at the repo root. fuz_forge is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.
- Release audit (every change): A forbidden crate or a test-only feature in a release build, a broken layering rule, and a copied lint table that has drifted. Where: fuz, fuz_forge and zap. pglet runs an audit of its own, for its test-only crate alone.
From Gates. A gate is listed here when its row names the project or links its repo, or speaks of a class of repos that the snapshot puts this one in.
Actions kept with a person
- Publish a package (permission rule, dry run by default, written rule): The harness denies the publish commands, in settings that are not public. The release scripts of tsv, pglet and blake3 change nothing without an explicit flag, which a session could pass. The publish task of gro and the release task of fuz_forge have no such default.
Rules that moved down
- Look up the home directory one way became: One hardened function, and in fuz and fuz_forge a lint that refuses the standard one. A direct read of the variable is still only a rule.
From Rules that moved down.
Values
- A decision: correctness over simplicity. A TypeScript server kept as the reference twin of the Rust one, held to it by shared tests. Cost: Two implementations to keep in step. overview
- Where the stack falls short of security: gro's runtime says its security is not finished, and fuz_forge says its security is not ready to be trusted.
- What a reader can verify, content addressing: fuz_forge's file store takes a file's BLAKE3 hash as its address and only digest, and
fuzf file getchecks the bytes it receives against it - A limit of what a reader can verify, content addressing: fuz_forge's server streams a file from disk without re-hashing it, so the check is the client's to make
- What a reader can verify, signing: fuz_forge's
fuzf tool publishsigns an artifact with the publisher's key, which the forge never holds - A limit of what a reader can verify, signing: fuz_forge has no published release, and the install it documents checks a SHA-512 file, not a signature
From the values page.