allagroup/alla-allaos-fullstack
Template
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
e0fcb3992b006eafe26d2b5b64ae6985c797f697
alla-allaos-fullstack/plans/task-bu-r.0.md
phaichayon 3b5fede134 r0
2026-07-07 10:02:28 +07:00

598 lines
6.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Phase R.0 – Business Blueprint Freeze
Status: In Progress
Priority: Critical
Type: Business Discovery / Architecture
---
# Objective
Freeze the long-term business architecture and business terminology of ALLA OS before performing any schema refactoring or implementation work.
This phase focuses on validating business concepts, ownership boundaries, user workflows, lifecycle definitions, and workspace philosophy.
No database schema, API, UI, or implementation changes are allowed during this phase.
The output of this phase becomes the official Business Blueprint for all future development.
---
# Background
ALLA OS has evolved from a traditional CRM into a Relationship-Driven Sales Workspace.
Several new business concepts have emerged during Business Discovery:
- Relationship First
- Activity-Centric Workspace
- Opportunity owns Project Lifecycle
- Quotation owns Document Lifecycle
- Calendar as a Workspace instead of a standalone module
- Timeline as a generated business view
- Customer Account Type (Customer / Prospect)
- Expected Award Date
- Hot Project Business Model
These concepts must be frozen before auditing the existing implementation.
---
# Review Required
Review all existing business decisions before making any proposal.
Must review:
- AGENTS.md
- Project Standards
- Architecture Rules
- Task Catalog
- Existing CRM Blueprint
- Business Discovery notes
- Previous ADRs
- Existing Schema
- Existing API structure
- Existing Workspace design
Do not assume any undocumented business rule.
---
# Scope
## 1. Product Vision
Freeze:
- Product Vision
- Product Mission
- Design Philosophy
- Core Principles
Validate that ALLA OS is positioned as
Relationship-Driven Sales Workspace
instead of a traditional CRM.
---
## 2. Business Terminology
Freeze official definitions.
Examples:
Customer
Prospect
Lead
Opportunity
Quotation
PO
Activity
Follow-up
Task
Reminder
Visit
Meeting
Site Survey
Presentation
Timeline
Workspace
Pipeline
Forecast
Expected Award Date
Expected Delivery Date
Hot Project
Status
Process Status
Outcome
Every business term must have exactly one official definition.
---
## 3. Customer Relationship Model
Review and freeze
Customer
↓
Contacts
↓
Activities
↓
Leads
↓
Opportunities
↓
Quotations
↓
PO
Validate
Customer Account Type
- Customer
- Prospect
Confirm that Customer remains the master entity.
---
## 4. Activity Model
Determine whether Activity becomes the single business activity model.
Review:
Follow-up
Visit
Meeting
Reminder
Task
Email
Phone Call
Presentation
Site Survey
Internal Task
Determine
Activity ownership
Reference strategy
Timeline strategy
Calendar strategy
Notification strategy
Future automation capability
---
## 5. Project Lifecycle
Freeze
Lead
↓
Opportunity
↓
Quotation
↓
PO
Review ownership of each stage.
---
## 6. Status Strategy
Review
Lead
Opportunity
Quotation
Determine
Process Status
Operational Status
Business Outcome
Ownership
Transition Rules
State Machine
Confirm that
Opportunity owns Project Process
Quotation owns Document Status
---
## 7. Hot Project Strategy
Freeze business definition.
Determine
Purpose
Owner
Calculation
Manual Override
Approval
Dashboard behavior
Forecast relationship
---
## 8. Forecast Strategy
Freeze
Expected Award Date
Definition
Business meaning
Forecast usage
Dashboard usage
Calendar usage
Reminder usage
Freeze
Expected Delivery Date
Definition
Business meaning
Operation usage
---
## 9. Workspace Model
Review
Marketing Workspace
Sales Workspace
Manager Workspace
Executive Workspace
Determine
Daily workflow
Workspace navigation
Primary landing page
Calendar philosophy
My Day philosophy
Timeline philosophy
---
## 10. Timeline Strategy
Determine
Timeline owner
Timeline generation
Timeline source
Timeline ordering
Timeline visibility
Timeline permission
Confirm whether Timeline is generated dynamically instead of stored.
---
## 11. Calendar Strategy
Determine
Calendar data source
Activity synchronization
Opportunity synchronization
Quotation synchronization
Reminder synchronization
Manager View
Team Calendar
Personal Calendar
---
## 12. Dashboard Strategy
Review
Sales Dashboard
Manager Dashboard
Executive Dashboard
Forecast
Pipeline
Hot Project
Overdue Activities
Follow-up
KPI
---
# Deliverables
The implementation must produce
## 1
Relationship & Sales Workspace Blueprint v1
---
## 2
Business Terminology Dictionary
---
## 3
Core Business Principles
---
## 4
Business Capability Map
---
## 5
Business Lifecycle Diagram
---
## 6
Workspace Architecture
---
## 7
Customer Journey
---
## 8
Project Journey
---
## 9
Activity Journey
---
## 10
State Machine Diagram
Lead
Opportunity
Quotation
---
## 11
Gap Summary
Current System
vs
Business Blueprint
---
## 12
Recommended Refactoring Strategy
Categorize into
No Change
Enhancement
Refactor
New Capability
---
# Constraints
During this phase
DO NOT
- modify schema
- modify migrations
- modify database
- modify API
- modify services
- modify UI
- modify permissions
- modify business logic
This phase is documentation and architecture validation only.
---
# Success Criteria
Business terminology is fully standardized.
Every entity has a single owner.
No duplicated responsibility exists.
No conflicting business rules remain.
Customer Journey is finalized.
Project Journey is finalized.
Workspace philosophy is finalized.
Timeline philosophy is finalized.
Calendar philosophy is finalized.
Ready for
Phase R.1 – Business Capability Audit
without changing the core architecture.
Architecture Protection Rules
- Reuse existing Foundation whenever possible.
- Prefer Extension over Replacement.
- Prefer Composition over Duplication.
- Preserve existing API compatibility unless a breaking change is approved.
- Preserve Organization, RBAC, Approval, PDF, and Document foundations.
- Any schema refactoring must include backward compatibility analysis.
- Business Blueprint has higher priority than implementation details.
---
# Implementation Progress
## 2026-07-07
Status: In Progress
Summary:
- Reviewed governance, standards, CRM terminology, security boundaries, ADR lineage, and current schema before proposing any freeze output.
- Created the first official blueprint draft:
`docs/business/relationship-sales-workspace-blueprint-v1.md`
- Recorded the review baseline, freeze decisions, and current governance gaps:
`docs/implementation/task-bu-r.0-business-blueprint-freeze-2026-07-07.md`
Current outcome:
- Phase R.0 has started as a documentation-only architecture task.
- The repo now has one central draft document for business vision, terminology, lifecycle ownership, workspace philosophy, timeline, calendar, forecast, Hot Project, and gap summary.
- Historical `enquiry` vs `opportunity` conflicts are documented for follow-up reconciliation in Phase R.1.
Reference in New Issue View Git Blame Copy Permalink