Layers And Ownership

What problem does it solve?

Understand how L0, L1, and L2 placement and ownership affect repository assets, and how to resolve read/write permissions across groups and users before storing or overriding frontend assets.

Core Features & Use Cases

• Document the three-layer model (L0 firmware, L1 group customware, L2 user customware) and their access rules.
• Define the canonical structure for groups and users (L1/_all, L1/_admin, L2/<username>/mod, group.yaml, etc.) and how histories may be enabled.
• Provide guidance on applying ownership and override resolution in real work scenarios such as introducing new frontend assets or policies.

Quick Start

Describe and apply the L0/L1/L2 layering rules to determine where new files belong and how overrides resolve across users and groups.