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/change-log.md
+38
View File
@@ -18,6 +18,44 @@ Follow-ups:
---
### CL-2026-06-18-CRM-CASE-PROGRESS-CONTEXT: record CRM Case Progress Display investigation conclusions
date: 2026-06-18
author: Cline
scope: `context/current-platform-state.md`, `memory-bank/{techContext,productContext,change-log}.md`
type: change
rationale: Preserve the completed CRM Case Progress Display investigation conclusions in project context so future contributors do not re-open the same status/lifecycle ambiguity without need.
impact: Documentation/context only; improves architectural clarity around case status display ownership and inputs; no runtime, auth, i18n, API, or behaviour change.
status: completed
Summary:
- Updated project context to record that the Case Status tab is a portal-owned journey interpretation layer.
- Recorded the active input model as:
- CRM `statuscode`
- appeal type
- specialist process (Rights of Way only)
- Recorded that `pinswg_casestage` is not a significant active input to current status-tab lifecycle resolution.
- Recorded that stage catalogues are best understood as:
- user-facing journey models
- appeal-type interpretation models
- presentation-layer progress visualization
- Recorded that shared catalogue families (`PLANNING_S78`, `ENFORCEMENT`, `DNS/SIP`, Rights of Way specialist-process variants) reflect a mixture of shared journey structures, presentation reuse, and historical consolidation.
- Recorded the architectural conclusion that this area is presentation architecture / journey interpretation, not a new business-policy domain boundary candidate.
Validation:
- Documentation/context update only.
- No application code changed.
- No tests changed.
- Lint/tests skipped because this was documentation-only work.
Follow-ups:
- Reopen only if a future business-validation or behaviour-change initiative requires deeper lifecycle/status decision work.
---
### CL-2026-06-18-RPA-DOCS: representation participation availability documentation + context update
date: 2026-06-18