Centralized Systems Overview

Purpose

Centralized systems keep Amvionlie consistent. They are the shared rails that prevent every addon from inventing its own tiny government.

Use central helpers

Use central helpers for:

• permissions and frontend access checks
• CSRF validation and fields
• notices and response helpers
• list controls, pagination, search, and sorting
• identity, UUID, slug, and key generation
• admin shell rendering
• public target records
• user preferences and sortable order
• changelog records

Why this matters

Central systems make behavior predictable. An admin list should feel like other admin lists. Permission checks should resolve the same way everywhere. Public targets should be selectable by Menu Manager without each addon inventing a new vocabulary.

Developer habit

When adding behavior, search for an existing central helper before writing a local helper. The fastest local helper often becomes tomorrow's cleanup report.

Common central rails

• `core/security/permissions.php` for permission and access evaluation.
• `core/security/csrf.php` for CSRF fields and validation.
• `core/http/list_controls.php` for list state.
• `core/http/response.php` for response helpers.
• `core/identity/*` for UUID, slug, and admin handle helpers.
• Admin shared template/list helpers for shell-safe admin UI.

Rule

If three addons need the same behavior, it probably belongs in a central rail. If one addon needs it, keep it in the addon.