task-j1

docs/implementation/technical-debt.md

@@ -297,3 +297,51 @@ Future:
 - decide whether approved quotation snapshots or another immutable reporting snapshot should become the historical source of truth
 - define how reporting should behave if project parties change after quotation approval or after a won/lost outcome
 - add backfill or reconciliation tooling if historical party drift becomes a business issue
+
+## After Task J
+
+### Closed-won lifecycle fidelity
+
+Task J ships a live CRM dashboard, but the current schema still lacks a first-class enquiry `closed_won` lifecycle field and dedicated close timestamps.
+
+Current:
+
+- dashboard won-stage metrics currently use quotation status `accepted` as the practical proxy for `closed_won`
+
+Future:
+
+- add explicit enquiry lifecycle support for `closed_won`
+- add `closedWonAt` to support precise won-date analytics
+- remove dashboard proxy logic once the lifecycle model is formalized
+
+### Follow-up completion semantics
+
+Task J adds follow-up analytics, but the follow-up model still has no explicit completion flag.
+
+Current:
+
+- dashboard `Completed` follow-up metrics infer completion from `outcome` presence
+
+Future:
+
+- add an explicit completion state or activity outcome model for follow-ups
+- separate scheduled, completed, cancelled, and skipped follow-up reporting cleanly
+
+### Dashboard own-scope policy
+
+Task J introduces `crm.dashboard.read`, but sales users still view organization-wide KPI data for now.
+
+Future:
+
+- add own-scope dashboard filtering for sales roles
+- define whether mixed-role users see own, team, or organization scope by default
+- keep exports aligned with the same scope policy once enforced
+
+### Global project-party filter coverage
+
+Task J adds a global `Project Party Role` filter in the dashboard UI, but the strongest enforcement today is in revenue analytics and export sections.
+
+Future:
+
+- decide which non-revenue widgets should fully honor project-party role filtering
+- add a unified filtered reporting projection if cross-widget party-role filtering becomes a hard requirement