alla-allaos-fullstack/docs/implementation/task-bu-r.1-business-capability-audit-2026-07-07.md

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

Scope

• audit the current ALLA OS implementation against the frozen BU-R.0 and BU-R.0.1 business blueprint
• classify capabilities as Existing, Partial, Missing, Legacy, or Refactor Candidate
• document preservation, dependency, priority, and readiness guidance for later implementation phases
• keep the phase documentation-only with no schema, API, UI, service, permission, or business-logic changes

Review Summary

Reviewed before auditing:

• AGENTS.md
• plans/task-bu-r.1.md
• docs/business/relationship-sales-workspace-blueprint-v1.md
• docs/implementation/task-bu-r.0-business-blueprint-freeze-2026-07-07.md
• docs/implementation/task-bu-r.0.1-workspace-activity-business-blueprint-2026-07-07.md
• docs/standards/project-foundations.md
• docs/standards/architecture-rules.md
• docs/standards/task-review-checklist.md
• docs/security/crm-authorization-boundaries.md
• relevant CRM/foundation source under src/features/crm/**, src/features/foundation/**, src/app/dashboard/crm/**, src/app/api/**, src/config/nav-config.ts, and src/db/schema.ts

Executive Summary

1. Customer, Contact, Opportunity, Quotation, Approval, Dashboard, security, and PDF/document foundations are already mature and should be preserved.
2. Lead capability exists as a real separated workspace and schema, but its follow-up implementation remains lighter and more audit-log-backed than the blueprint target.
3. Follow-up capability is real across lead, opportunity, quotation, and dashboard analytics, but a shared production Activity platform does not exist yet.
4. Timeline, Calendar Workspace, My Day, Manager Workspace, and role-based business workspaces are still mostly target-state architecture, not production capability.
5. Notification foundation is reusable and production-ready, but current live business-event coverage is approval-centric rather than activity-centric.

1. Business Capability Matrix

Domain	Capability	Status	Notes
Relationship	Customer master, profile, related opportunity/quotation linkage	Existing	Customer detail already acts as a relationship context surface with related commercial records.
Relationship	Customer ownership	Existing	Persisted owner assignment plus owner history exists and is governed by ADR-0015.
Relationship	Contact sharing and visibility	Existing	Persisted crm_contact_shares plus share-aware access enforcement exists.
Relationship	Customer account type / prospect classification	Partial	Customer type and status options exist, but relationship-health semantics are not governed in product behavior yet.
Relationship	Customer relationship health	Missing	No governed health model, scoring logic, or dedicated UI module yet.
Relationship	Customer timeline	Partial	Audit Log and related-record links exist, but no generated cross-entity customer timeline exists.
Activity	Lead follow-up	Existing	Lead follow-ups exist, but are stored via audit payloads instead of a dedicated follow-up table.
Activity	Opportunity follow-up	Existing	Persisted child resource with CRUD, UI tab, dashboard aggregation, and report reuse exists.
Activity	Quotation follow-up	Existing	Persisted child resource with CRUD, UI tab, dashboard aggregation, and report reuse exists.
Activity	Shared Activity entity/platform	Partial	Contract-first activity types and permissions exist under src/features/crm/activity/types.ts, but there is no production storage/service/UI yet.
Activity	Meeting / visit / phone / reminder / internal task	Missing	Only follow-up-oriented capability is implemented today.
Activity	Shared activity lifecycle and ownership rules	Partial	Blueprint-ready contract exists; production behavior still fragmented by feature.
Lead	Separate lead workspace	Existing	Dedicated pages, service layer, schema, assignment, follow-up, and linked opportunities are live.
Lead	Marketing handoff into opportunity	Partial	Linked opportunity visibility exists, but explicit governed conversion workflow is still limited.
Lead	Lead outcome derivation from downstream sales	Missing	Lead outcome behavior remains lighter than the blueprint target and ADR-0018 direction.
Opportunity	Opportunity ownership and assignment	Existing	Sales assignment, reassignment, branch/product scope, and linked lead provenance are implemented.
Opportunity	Forecast fields and probability	Existing	expectedCloseDate, projectCloseDate, deliveryDate, chancePercent, and isHotProject are live.
Opportunity	Expected Award Date / Expected Delivery Date semantics	Partial	Underlying dates exist, but exact blueprint naming/behavior still needs semantic reconciliation.
Opportunity	Outcome governance won/lost/reopen/PO	Existing	ADR-0016 behavior is implemented with mark-won, mark-lost, reopen, and PO attachment flows.
Commercial	Quotation CRUD, revision, approval, pricing	Existing	Mature quotation feature with revision chain, approval, preview, PDF, and customer package support exists.
Commercial	Customer package	Existing	Implemented as approved-PDF plus document-library assembly with permission checks.
Commercial	PO integration	Partial	PO capture is implemented on opportunity outcome, but customer-workspace and timeline integration are not yet complete.
Approval	Workflow runtime	Existing	Shared approval runtime, steps, actor resolution, notification publishing, and dashboard analytics exist.
Approval	Approval automation reminders/escalation	Existing	Reminder and escalation policy foundations are present.
Workspace	Customer workspace	Partial	Current customer detail is a strong base, but blueprint sections like Activities, Timeline, Health, Upcoming Work, and Notes are incomplete.
Workspace	Sales workspace	Partial	Lead, opportunity, quotation pages exist, but they are entity pages more than one unified role workspace.
Workspace	Manager workspace	Missing	No first-class manager control-tower page exists yet.
Workspace	Executive workspace	Missing	No dedicated executive workspace exists yet.
Workspace	My Day	Missing	No personalized action-home surface exists yet.
Workspace	Calendar workspace	Missing	No dedicated calendar route, projection layer, or calendar UI exists yet.
Timeline	Generated business timeline	Missing	Audit Log exists, but there is no platform-generated cross-entity timeline model.
Dashboard	CRM dashboard KPI foundation	Existing	Summary, funnel, follow-up, approval, revenue, ranking, and hot projects are implemented.
Dashboard	Manager / executive-specific dashboard layers	Partial	Current dashboard supports broad KPI visibility, but not fully distinct role workspaces.
Notification	Inbox foundation and read/archive flows	Existing	Generic app notifications and inbox UI are production-ready.
Notification	Approval notifications	Existing	Approval runtime publishes notification events and inbox surfaces them.
Notification	Activity / follow-up / assignment notifications	Missing	Business-event coverage for operational activity is not implemented yet.
Event Model	Audit events	Existing	Core audit foundation is widespread and mature.
Event Model	Approval events	Existing	Approval event publishing is live.
Event Model	Activity-driven business events	Partial	Opportunity and quotation mutations exist, but shared fan-out governance is not yet implemented as one event model.

2. Capability Coverage Report

Coverage values below are qualitative readiness estimates based on audited business scope, not literal line-of-code metrics.

Domain	Coverage	Summary
Customer / Relationship	70%	Strong ownership, sharing, profile, and related-record foundation; missing relationship health and generated timeline.
Activity	35%	Follow-up is real, but shared activity platform, meeting/task/reminder families, and unified lifecycle are not implemented.
Lead	70%	Dedicated domain and workspace exist, but downstream derived outcome and richer handoff workflow remain incomplete.
Opportunity	85%	Assignment, forecast fields, follow-up, hot project, and outcome governance are mature.
Quotation	90%	CRUD, revision, approval, document, package, and pricing foundations are strong.
Approval	90%	Runtime, settings, automation, and dashboard visibility are well-established.
Dashboard	80%	KPI dashboard is live and substantial, but role-specialized workspace behavior is still incomplete.
Calendar	10%	Date fields and reminder policies exist, but no true calendar workspace capability exists.
Timeline	20%	Audit Log exists, but blueprint-grade generated business timeline does not.
Notification	50%	Good reusable foundation, but limited current business-event breadth.
Workspace Model	40%	Entity routes exist, but My Day, Manager, Executive, and Calendar workspaces are still future capability.

3. Gap Analysis: Current System vs Business Blueprint

No Change

• Customer ownership and contact sharing foundation
• Opportunity outcome governance
• Quotation approval, document, PDF, artifact, and customer package foundations
• CRM dashboard KPI foundation
• CRM authorization and pricing-visibility enforcement

Enhancement

• Customer detail evolving into Customer Workspace
• Opportunity/quotation date semantics aligning to expected-award and expected-delivery definitions
• Dashboard role layering for manager and executive needs
• Notification foundation expanded from approval-centric events into broader CRM business events
• Lead handoff and downstream outcome synchronization

Refactor

• Fragmented follow-up behavior into a shared Activity platform over time
• Historical enquiry terminology remnants in docs and older lineage
• workspaces navigation semantics, which currently mean organization/team administration rather than business-role workspaces

New Capability

• Generated Timeline
• Calendar Workspace
• My Day
• Manager Workspace
• Executive Workspace
• Activity platform with shared families beyond follow-up

4. Architecture Preservation Report

Keep Unchanged

• src/features/crm/customers/**
• src/features/crm/opportunities/**
• src/features/crm/quotations/**
• src/features/foundation/approval/**
• src/features/foundation/approval-automation/**
• src/features/foundation/notifications/**
• src/features/foundation/pdf-generator/**
• src/features/foundation/document-artifact/**
• src/features/crm/dashboard/**
• src/lib/auth/crm-access.ts and CRM security enforcement

Extend Only

• customer detail and related tabs into Customer Workspace sections
• lead/opportunity/quotation follow-up flows into future Activity adapters
• dashboard into manager and executive role surfaces
• notification event publishing into broader business-event coverage
• nav and workspace routing into clearer role-oriented destinations

Controlled Refactor Required

• shared activity storage/service/UI
• timeline projection layer
• calendar projection and filtering layer
• terminology cleanup across historical docs and edge code paths

Backward Compatibility Concerns

• lead follow-up currently depends on audit-log payloads rather than a dedicated persisted follow-up table
• approval and notification fan-out already exist for approvals, so later activity events must avoid double-publishing behavior
• dashboard/service/reporting logic already depends on current follow-up storage, so activity migration must preserve analytics continuity
• current workspaces routes are already used for organization/team administration and should not be silently repurposed

5. Business Capability Dependency Map

Customer / Contact
|- Lead
|  `- Opportunity
|     |- Follow-up / Future Activity Platform
|     |- Quotation
|     |  |- Approval
|     |  |- PDF / Artifact / Customer Package
|     |  `- Commercial Notifications
|     |- Dashboard / Reports
|     `- Won / Lost / PO
|
`- Future Customer Workspace
   |- Timeline
   |- Calendar Projection
   |- My Day
   `- Manager / Executive Workspace

6. Capability Priority Matrix

Epic / Capability	Priority	Why
Activity Platform	Critical	It is the main missing shared business model and blocks Calendar, Timeline, My Day, and richer notifications.
Customer Workspace	Critical	Customer is the relationship anchor and already has a strong partial base worth extending.
Timeline	High	Required for blueprint-aligned relationship history and event visibility.
Calendar Workspace	High	Strong business need, but depends on activity/event projection clarity.
My Day	High	Key daily operating surface and natural consumer of activity, reminders, and approvals.
Manager Workspace	High	Needed for operational control, workload balancing, and hot-project governance.
Notification Expansion	Medium	Foundation exists; main work is business-event coverage and orchestration.
Executive Workspace	Medium	Valuable, but depends on manager/dashboard/timeline foundations first.
Terminology / legacy cleanup	Medium	Important for governance clarity, but not as blocking as Activity or Workspace delivery.

7. Implementation Readiness Report

Area	Readiness	Notes
Customer Workspace	Requires UI enhancement	Data foundation is strong; sections like health, upcoming work, and relationship summary need expansion.
Activity Platform	Requires schema + service + UI enhancement	Only contract-first types exist today.
Lead lifecycle enhancement	Requires service + UI enhancement	Existing lead feature is usable, but derived outcome/handoff depth is incomplete.
Opportunity forecast semantics	Requires service + UI enhancement	Core fields exist already.
Quotation commercial execution	Ready immediately	Mature enough to preserve and extend.
Approval runtime	Ready immediately	Mature enough to preserve and extend.
Dashboard role layering	Requires UI + service enhancement	Foundation exists and is reusable.
Timeline	Requires schema/service/UI future phase	No true generated timeline capability yet.
Calendar Workspace	Requires schema/service/UI future phase	No production projection layer or UI route exists yet.
My Day	Requires service/UI future phase	Depends on activity, reminder, approval, and hot-project orchestration.
Notification expansion	Requires service enhancement	Foundation exists; business-event coverage does not.

8. Candidate Epics After BU-R.1

• Epic: Customer Workspace
• Epic: Activity Platform
• Epic: Timeline Projection
• Epic: Calendar Workspace
• Epic: My Day
• Epic: Manager Workspace
• Epic: Executive Workspace
• Epic: Notification Event Expansion
• Epic: Lead Handoff and Outcome Alignment
• Epic: Terminology and Governance Reconciliation

Verification

• Documentation-only change.
• No schema, API, UI, service, permission, or business-logic files were modified for runtime behavior.
• No build or test command was required for this audit pass.

Outcome

BU-R.1 confirms that the repo already has a strong production backbone for relationship, opportunity, quotation, approval, document, dashboard, and security work. The biggest blueprint gaps are no longer hidden inside core CRUD; they are concentrated in the cross-cutting operating model: shared Activity, Timeline, Calendar, My Day, Manager Workspace, Executive Workspace, and business-event-driven notifications.