Add ISAC weapon data management

2026-07-25 00:49:08 -04:00
parent 3f78f0f9d8
commit e528f18d8f
12 changed files with 555 additions and 13 deletions
@@ -34,6 +34,21 @@ or revise a reusable design decision do not require a documentation update.

 If uncertain whether a visual change is significant, update the design system.

+## ISAC editor lifecycle
+
+All ISAC data-management editors must follow the same successful-save behavior:
+
+1. Saving an edit to an existing record closes the editor and returns the user
+   to the registry.
+2. Saving a newly added record keeps the editor open with a fresh blank record
+   so consecutive data entry remains fast.
+3. Validation errors keep the editor open and preserve the entered values.
+4. Server actions must return the add/edit mode and a unique result token;
+   client-side reactive handling must consume each token only once to avoid
+   repeated state updates.
+
+Apply this convention whenever an ISAC editor is added or materially changed.
+
 ## Database preservation

 Development data is valuable and may be entered by non-technical contributors.