tauri-core

name	tauri-core
description	Shared reference for the Tauri cluster: the v2 security model (capabilities → permissions → scopes), the IPC trust boundary and command contract, the process/runtime model, CSP, and the per-platform distribution matrix. USE WHEN configuring Tauri permissions/scopes/CSP, wiring IPC commands, or planning a release — the interlocking rules every Tauri spoke shares.
cluster	tauri
version	1.0.0

Tauri Core

Shared model for the tauri cluster. The config, IPC, and distribution spokes all depend on these interlocking concepts — keep them consistent here so no spoke contradicts another.

1. The security model (Tauri v2's defining feature)

Access is default-deny. You opt windows into capabilities, which bundle permissions, which may be narrowed by scopes:

Window/Webview ──has──> Capability ──includes──> Permission(s) ──constrained by──> Scope(s)

• Permission — a single allowed command/behavior (often shipped by a plugin, e.g. fs:read-files). Default + custom permissions live in src-tauri/permissions/ and plugin manifests. → configuring-tauri-permissions
• Capability — a JSON file in src-tauri/capabilities/ that grants a set of permissions to specific windows/webviews (by label) and platforms. This is how you wire permissions to surfaces. →