What are functional rights in Noumena, and why does changing them require a deployment?

Functional rights define what actions a user can perform; they are granular, tied to specific business functions, and wired directly into the protocols — so changing them means changing and redeploying code.

A functional right is an atomic capability — "Review activities", "Approve onboarding", "Manual overwrite", "trigger a payment". Good practice is to make them granular and tied to specific business functions; highly regulated entities need an especially fine-grained set, and defining them is crucial before implementation starts. Crucially, functional rights are wired into the protocols themselves — the protocol's permissions and obligations reference them — so they cannot be changed without a deployment. This is deliberate: capability is part of the audited, version-controlled business logic, not a setting an administrator can quietly flip at runtime.

Go deeper:

• Role-based access control (Wikipedia) — the permission/role vocabulary; a functional right is the atomic permission that roles later bundle.