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.
• 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.

Next likely discovery candidate

• Case Lifecycle / Status Decision Model Discovery
  • Investigate how the portal interprets case progress, stages, statuses, closed states, dashboard grouping, and user-facing lifecycle messaging.
  • Treat this as discovery only until the new representation participation documentation has been reviewed and business validation feedback is available.