Núcleo en Rust, permisos mínimos, paquetes pequeños, comandos tipados entre la UI y el núcleo.
Constitution — Tauri app
Version 1.0.0 · Ratified 2026-11-10
These principles hold for every spec, plan and task of the project. A spec may add rules; it never weakens these.
-
Rust core. Business rules, file access, networking and storage live in the Rust core. The web frontend only renders and calls commands.
-
Minimal permissions. Tauri 2 capabilities give each window only the permissions it uses, with scopes narrowed to the paths and URLs it needs. A wildcard scope for
fsorshellfails the review, and a new permission needs a reason in the plan. -
Small bundles. The release profile uses
lto,stripandopt-level = "s", and the installer stays under 15 MB. CI checks the size and fails above the budget. -
Typed commands between UI and core. Every
#[tauri::command]takes and returns serde types and returns aResultwith a serializable error. TypeScript bindings are generated (for example with tauri-specta), so a hand-writteninvokestring fails the review. -
Locked-down webview and signed updates. A strict Content Security Policy is set in
tauri.conf.jsonand no remote content is loaded. The updater verifies every update with the app's public key, and release builds are signed. -
Tested and lint-clean. The core is covered by
cargo testandcargo clippy -- -D warningspasses. Critical flows have WebDriver end-to-end tests, all green before the merge.