pedwfrontend/context/current-platform-state.md

Current Platform State (PEDW) — feature/restart-from-sips

Last updated: 2026-05-13

Summary

PEDW is in a late-stage refactor stabilization phase.

• New Appeal refactor stream (Slices 1–8) is complete per tracker/state docs.
• Representations stream remains structurally complex and only partially decomposed.
• Platform architecture direction remains valid: bounded, behaviour-preserving slices.

What is complete

• New Appeal slice stream documented complete (context/refactor-tracker.md, context/newappeal-refactor-current-state.md).
• Significant route/breadcrumb decomposition and helper extraction completed.
• Broad endpoint contract hardening completed across key clusters.
• Representation Participation Availability investigation completed from a technical discovery/documentation perspective.
• Representation participation behaviour is now documented as one coherent decision model with layered appeal-type, specialist-process, participant-type, consultation, and date-window exceptions.
• CRM Case Progress Display investigation completed from a technical discovery/documentation perspective.
• Case Status tab behaviour is now understood as a portal-owned journey interpretation layer driven by CRM statuscode, appeal type, and Rights of Way specialist-process routing.
• Source documents added:
  • docs/representation-participation-availability.md (developers / architects / maintainers)
  • docs/representation-participation-business-review.md (business / product / SME validation)

What is incomplete

• Auth/session reliability hardening (intermittent re-signin prompts).
• SSR loader resilience normalization across myportal/representation/new appeal.
• Logging hardening consistency in auth/file/account-sensitive paths.
• Remaining decomposition hotspots (components/elements/index.js, representation flow internals).
• Business validation of Representation Participation Availability before any further representation-policy adoption, expansion, or behaviour-change work.

Operational risk profile (current)

Top active risks:

1. Auth/session intermittency (callback/cookie/SSR timing interplay).
2. Fragile nested state assumptions in loader-heavy paths.
3. Production log noise and inconsistent redaction patterns.
4. Manual effort burden for EN/CY parity and journey regression checks.

Notes on stale/legacy guidance

• Some context docs still describe pre-refactor representation baseline; treat those as historical unless updated by active slice evidence.
• Legacy commented code remains in active files (especially journey files) and should be treated as cleanup debt, not source-of-truth runtime behaviour.

Representation Participation Availability — Current State

• Technical discovery/documentation stream is complete.
• Current architectural conclusion: do not continue searching for a new representation domain boundary at this point.
• Representation participation is best understood as one coherent decision model with layered exceptions rather than a set of unrelated CTA rules.
• Known divergences and compatibility-sensitive behaviours are documented and should be preserved unless an explicit business decision authorizes change.
• Current state: awaiting business validation of docs/representation-participation-business-review.md before any further representation-policy adoption, expansion, or behavioural change work.

CRM Case Progress Display — Current State

• Technical investigation stream is complete.
• Current architectural conclusion: do not treat this area as a new business-policy domain boundary.
• The Case Status tab is best understood as a portal-owned journey interpretation layer:
  • inputs: CRM statuscode, appeal type, specialist process (Rights of Way only)
  • resolution model: journey catalogue selection -> user-facing journey representation
• pinswg_casestage is not a significant active input to the current status-tab model:
  • it was historically associated with DNS/SIPS summary support
  • it is not part of active lifecycle resolution for the status tab
• Stage catalogues are best understood as:
  • user-facing journey models
  • appeal-type interpretation models
  • presentation-layer progress visualisation
• Shared catalogue families exist (PLANNING_S78, ENFORCEMENT, DNS/SIP, Rights of Way specialist-process variants) and represent a mixture of:
  • genuine shared journey structures
  • presentation reuse
  • historical consolidation

Discovery candidate update

• Case Lifecycle / Status Decision Model Discovery is no longer an open next-candidate investigation.
• Current conclusion from the completed CRM Case Progress Display stream:
  • this area is primarily presentation architecture + journey interpretation
  • further work should only be reopened if a new business-validation or behavioural-change question emerges