Merged PR 2401: docs: document representation participation availability model

docs: document representation participation availability model

Related work items: #23754

memory-bank/open-questions.md

@@ -88,3 +88,37 @@ Technical lead + DevOps owner
 
 Decision deadline:
 Before runtime-affecting refactor or next deployment process update
+
+---
+
+### Q-004: Representation Participation Availability business validation
+
+date: 2026-06-18  
+author: Cline  
+scope: representation participation availability across summary/search/domain policy  
+type: question  
+rationale: Technical characterization is complete, but several compatibility-sensitive behaviours may be historical rather than intentional and need business confirmation before any further representation-policy adoption or behaviour change work.  
+impact: User-facing participation availability, blocked messaging, cross-portal consistency, and future domain-boundary decisions.  
+status: open
+
+Question:
+Which current representation participation behaviours are intended business rules, and which are historical compatibility behaviours only?
+
+Needed from:
+Product owner + business analyst + relevant SME/CRM data owner
+
+Decision deadline:
+Before any further representation-policy adoption, expansion, normalization, or behavioural change work
+
+Current context:
+
+- Technical characterization and documentation are now recorded in:
+    - `docs/representation-participation-availability.md`
+    - `docs/representation-participation-business-review.md`
+- Business validation is especially needed for:
+    - Rights of Way behaviour when process information is incomplete or stored differently
+    - Advertisement behaviour when process information is incomplete or conflicting
+    - whether all portal areas should behave consistently
+    - Householder blocked-message suppression
+    - CPO ended-message / deadline consistency
+    - missing or conflicting process information handling