alla-allaos-fullstack/docs/implementation/task-bu-r.0.1-workspace-activity-business-blueprint-2026-07-07.md

Task BU-R.0.1 Implementation Report - 2026-07-07

Scope

• continue BU-R.0 by freezing the remaining business architecture for Activity, Workspace Interaction, Customer Workspace, Calendar Workspace, My Day, Manager Workspace, and Business Event fan-out
• update the main relationship and sales business blueprint without changing previously frozen BU-R.0 principles
• keep the task documentation-only with no schema, API, UI, service, permission, or ADR changes

Review Summary

Reviewed before drafting:

• AGENTS.md
• plans/task-bu-r.0.1.md
• plans/task-bu-r.0.md
• docs/standards/task-contract-template.md
• docs/standards/task-catalog.md
• docs/standards/project-foundations.md
• docs/standards/architecture-rules.md
• docs/standards/ui-ux-rules.md
• docs/standards/task-review-checklist.md
• docs/business/crm-terminology.md
• docs/business/relationship-sales-workspace-blueprint-v1.md
• docs/security/crm-authorization-boundaries.md
• docs/adr/0015-customer-ownership-contact-sharing.md
• docs/adr/0016-won-lost-lifecycle-governance.md
• docs/adr/0017-report-foundation.md
• docs/adr/0018-lead-enquiry-domain-separation.md
• docs/implementation/task-bu-r.0-business-blueprint-freeze-2026-07-07.md
• docs/implementation/task-d.6-crm-activity-foundation-audit-log-separation-2026-07-01.md
• current CRM customer, opportunity, quotation, dashboard, notification, and workspace implementations under src/features/**, src/app/dashboard/**, and src/db/schema.ts

Current-State Findings Used For The Freeze

1. Customer detail already behaves as a relationship context surface with contacts plus linked opportunities and quotations, but it is not yet governed as the official Customer Workspace.
2. Opportunity and quotation features already store follow-up rows, Hot Project flags, and forecast-related dates, which makes them valid current seams for the future shared activity and calendar model.
3. Dashboard already aggregates follow-up and Hot Project signals, but those signals are still oriented around dashboards rather than a broader My Day, Calendar Workspace, or Manager Workspace philosophy.
4. The notification foundation is production-ready, but current event publishing is mainly approval-driven, so activity-driven notification fan-out still needed business governance before implementation.
5. Existing /dashboard/workspaces navigation currently means organization/team administration, not the future business-role workspace model. That distinction had to be frozen explicitly to avoid naming drift.

Documentation Changes

• Expanded relationship-sales-workspace-blueprint-v1.md with:
  • Activity Blueprint Freeze
  • Workspace Interaction Blueprint Freeze
  • Customer Workspace Blueprint Freeze
  • Calendar Workspace Blueprint Freeze
  • My Day Blueprint Freeze
  • Manager Workspace Blueprint Freeze
  • Business Event Matrix
  • Activity State Machine
  • Workspace Navigation Diagram
  • Customer 360 Diagram
  • Daily User Journey for Marketing, Sales, Manager, and Executive
  • Current-system alignment notes for Phase R.1 audit readiness

Freeze Decisions Added In This Pass

• Activity is now the officially governed shared work model and remains distinct from Audit Log.
• Calendar is frozen as a workspace projection over activities and milestone events, not a detached scheduling module.
• My Day is frozen as the personalized action home screen prioritized by urgency and commitment risk.
• Manager Workspace is frozen as an execution-control workspace, not only a KPI dashboard.
• Business events are frozen as the common fan-out source for timeline, notification, reminder, dashboard, audit, and future automation behavior.
• Customer Workspace is frozen as the main relationship execution hub and Customer 360 surface.

Verification

• Documentation-only change.
• No schema, API, UI, service, permission, ADR, or migration files changed.
• No build or test command was required for this pass.

Outcome

BU-R.0.1 now closes the major business architecture gaps left outside BU-R.0 and leaves Phase R.1 with a clearer audit target for:

• follow-up-to-activity unification
• workspace and navigation semantics
• calendar and reminder projections
• activity-driven notification design
• manager and My Day operational surfaces