UI update initial phase complete. Still need to create schema-mapping for the two many-to-many tables.

docs/ui/README.md

@@ -27,11 +27,32 @@ Use this document to describe:
 - intended target behavior
 - implementation gaps between current code and intended UX
 
+### acceptance-criteria.md
+
+An implementation-ready checklist for CRUD behavior and quality gates.
+
+Use this document to describe:
+- testable acceptance statements by flow (Create, Read, Update, Delete)
+- success and failure behaviors
+- first-release constraints
+- cross-criteria quality gates
+
+### traceability-matrix.md
+
+A criteria-to-code mapping that identifies implementation anchors and status.
+
+Use this document to describe:
+- acceptance criteria group to implementation file mapping
+- delivery status (implemented, partial, planned)
+- ordered implementation priorities
+
 ## Organization Rules
 
 - Store documents under `docs/ui/entities/<entity-name>/`.
 - Create both `user-journey.md` and `schema-mapping.md` for user-facing entities.
+- Create `acceptance-criteria.md` for user-facing entities.
 - Create only `schema-mapping.md` for supporting tables that do not currently have standalone UI.
+- Keep one shared `traceability-matrix.md` under `docs/ui/entities/` to map criteria to implementation anchors.
 - Keep top-level `docs/` reserved for core architecture, requirements, schema, and system-wide reference material.
 
 ## Current Entity Plan