Skip to main content
Actions are declarative requests. defineAction gives the model a name, description, risk, approval requirement, and optional input schema.
Risk sets a minimum approval level: The renderer validates the registered name and input schema before emitting a frozen action event. Approval metadata does not mean the user approved anything.
The host must authenticate, authorize against current state, present trusted confirmation UI, apply rate limits, execute effects, audit outcomes, and persist idempotency. Never trust the action payload because it passed client-side validation. Retries and duplicate browser events are possible; Rixx UI does not maintain a production deduplication ledger.