robbond/pedwfrontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merged PR 2404: case stage analysis

Browse Source 
Related work items: #23754
This commit is contained in:
Robert Bond
2026-06-18 16:02:40 +00:00
parent 81a6276f44
commit 60a2ff4594
6 changed files with 941 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory-bank/techContext.md
+9
View File
@@ -54,6 +54,15 @@
- representation participation is best understood as one coherent decision model with layered exceptions
- known consumer divergences and CRM compatibility behaviours are part of the current live contract
- future technical adoption/expansion work should wait for business validation before changing behaviour or broadening policy boundaries
- CRM Case Progress Display investigation has now been concluded as a technical characterization stream.
- Current technical conclusion:
- the Case Status tab is a portal-owned journey interpretation layer
- active inputs are CRM `statuscode`, appeal type, and Rights of Way specialist-process routing only
- `pinswg_casestage` is not a significant active input to status-tab lifecycle resolution
- stage catalogues are not raw CRM lifecycle states and not business-policy decision models
- stage catalogues are best understood as user-facing journey models plus appeal-type interpretation plus presentation-layer progress visualization
- shared catalogue families (`PLANNING_S78`, `ENFORCEMENT`, `DNS/SIP`, Rights of Way specialist-process variants) reflect a mixture of shared journey semantics, presentation reuse, and historical consolidation
- this area is not currently a candidate for a new business-policy domain boundary
## CI/CD and deployment artifacts