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

Merged PR 2443: added docs

Browse Source 
added docs

Related work items: #23754
This commit is contained in:
Robert Bond
2026-06-29 17:58:10 +00:00
parent ff699735c7
commit 49aa258fd9
6 changed files with 1366 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/architecture.md
+21
View File
@@ -30,6 +30,27 @@ Portal authorization hardening / consistency planning (documentation-first, impl
- preserve stable authorization architecture model
- use the model as a baseline for future hardening/change review
## Portal Business Capability Context
PEDW Portal should be understood as supporting two principal business capabilities:
1. **Digital Appeal Submission**
- currently applies to supported digital appeal processes only
- current MVP implementation scope is Section 78 (`S78`)
- may be extended in future to additional supported appeal processes
2. **Statutory Public Information & Public Participation**
- the portal surfaces CRM-managed statutory case information to the public
- includes case details, documents, progress, events, and participation routes where applicable
- applies across multiple statutory case types, not only appeal-submission journeys
Business responsibility clarification:
- CRM / PEDW administers the statutory planning and casework processes
- the portal provides the statutory public-facing digital service layer
This architectural reference builds on those business concepts but does not replace the more detailed terminology guide in `context/business-domain-overview.md`.
## Portal API Platform Assessment Status (2026-06-20)
### Stream status