Merged PR 2433: assessment api grouping

assessment api grouping Related work items: #23754
2026-06-25 09:52:15 +00:00
parent 94b19f9697
commit 3960a357dc
3 changed files with 1087 additions and 415 deletions
@@ -419,6 +419,32 @@ UI journey
    - legacy endpoint handlers remain canonical
    - no route migration, deletion, contract change, auth change, storage change, or behaviour change has occurred

+#### Workflow boundary assessment checkpoint
+
+- A bounded follow-on assessment of the remaining major API families established that the current additive façade pattern has a natural stop point.
+- Main conclusion:
+
+> The current façade rollout pattern is proven for bounded read-style journey families, but it should not be stretched across workflow/orchestration-heavy areas without a different design.
+
+- Classification outcome from the representative family assessment:
+    - **B — Possible façade candidate with caution**
+        - account / registration / personal-details family, but only for a narrowly bounded future read-support slice
+    - **C — Workflow / orchestration boundary**
+        - notifications / email
+        - appeals / drafts / finalisation
+        - representations / drafts / finalisation
+    - **D — Leave unchanged for now**
+        - storage / blob / file operations
+        - auth / session
+        - admin / reporting
+- What this means for rollout discipline:
+    - the obvious low-risk read-family slices are now largely exhausted
+    - remaining complex areas are complex because they cross identity, storage, queue, Notify, PDF, or finalisation boundaries
+    - those areas do not meet the original checkpoint criteria for the same read-style façade rollout pattern
+- Recommended next step after the completed façade baseline:
+    - prefer a workflow/orchestration design assessment rather than another broad façade slice
+    - if one more implementation slice is ever chosen first, the only reasonable candidate is a **narrow account read-support cautious slice** that excludes create/update/bootstrap-critical behavior
+
 ---

 ### Stage 3 — Documentation Maturity