Feature flags

architect is wasm-clean with no default features. Everything optional is behind a flag, and flags compose in one direction only (an implication arrow never points back up). Two umbrella features cover the common profiles; the à la carte flags below them exist for fine-grained builds.

Profiles (start here)#

A typical app:

# apps/web (wasm UI)
architect = { workspace = true, features = ["client"] }

# apps/server (axum binary)
architect = { workspace = true, features = ["server"] }

# features/foo (one crate per feature, see layout.md) — forward vox so
# each consumer decides whether the RPC stack compiles:
[features]
vox = ["dep:vox", "dep:vox-types", "architect/vox"]

server is a strict superset of the old server = ["server-seaorm"] back-compat alias — consumers that wrote features = ["server"] for the SeaORM bridge keep working and additionally get the transport + dispatcher.

À la carte flags#

Implication graph#

client ─┬─ vox
        ├─ atom ◄────── form
        └─ form

server ─┬─ vox
        ├─ server-seaorm
        ├─ server-axum ─┬─ telemetry ── vox
        │               └─ platform
        ├─ dispatch-tokio
        └─ http

host ─┬─ server-axum
      └─ http
otlp-forward ── host
testing ─┬─ testing-alloc
         └─ host

schedule ── platform
local ───┬─ vox
         └─ platform
connect ─┬─ vox
         └─ platform
iroh-lan ── iroh ── vox
release ── blob
atom-turso ── atom-persist ── atom

Nothing implies atom except form and client — server-side flags never pull Dioxus, and atom/form never pull tokio’s runtime, so the wasm build stays clean no matter which side of the graph you’re on.

Gotchas the matrix resolves#

• form without vox compiles — fields and validation work — but submit() has no transport to post through. If you’re using forms against a server, you want client.
• vox off on a proto crate means no clients, no dispatchers, no RPC machinery at all; the emitted repo trait is a plain async trait you can call in-process. This is a feature (CLI/embedded use), not a broken build.
• dispatch-tokio off makes dispatch::DefaultDispatcher the inline CurrentThreadDispatcher — fine for tests, wrong for a server wrapping blocking work. server turns it on for you.
• architect-atom direct dependency vs architect/atom: the primitive crate is wasm-clean and Dioxus-only; the re-export through architect additionally lights up vox-aware hooks when vox is on.