What problem does it solve? When building admin panels that create or edit records, teams often diverge on how asides open, how mutations are handled, and how stores respond. This rule standardizes entity editing across an Angular workspace so every panel and store follows the same architecture. ## Core Features & Use Cases - Route-based aside panels: Edit panels open via a route in the ro outlet using a shared RtRouteAsideComponent<T> base, surviving reloads and staying linkable. - Standardized mutation flow: Saving goes through runMutation, mutations must emit a value or error, and success triggers a list re-read before closing. - Entity store conventions: Stores extend a shared list-store base, answer with streams instead of booleans, and use entity-generic names like save, remove, load. - Use Case: When adding a new admin section with a create/edit panel, load this rule to wire the route, base class, guard on all four closing paths, and store correctly the first time. ## Quick Start Load the entity-conventions rule before editing any admin store or panel that creates or edits a record.
