alla-allaos-fullstack/docs/implementation/task-bu-r.0-business-blueprint-freeze-2026-07-07.md

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

Scope

• start Phase R.0 as a documentation-only business architecture task
• review current governance, CRM business rules, ADRs, security boundaries, and current schema direction
• produce the first frozen business blueprint artifact and record the baseline findings

Review Summary

Reviewed before writing the blueprint:

• AGENTS.md
• plans/task-bu-r.0.md
• docs/standards/project-foundations.md
• docs/standards/architecture-rules.md
• docs/standards/ui-ux-rules.md
• docs/standards/task-review-checklist.md
• docs/standards/task-catalog.md
• docs/business/crm-terminology.md
• docs/security/crm-authorization-boundaries.md
• docs/adr/0011-lead-enquiry-ownership-model.md
• docs/adr/0015-customer-ownership-contact-sharing.md
• docs/adr/0016-won-lost-lifecycle-governance.md
• docs/adr/0018-lead-enquiry-domain-separation.md
• plans/task-d.5.md
• plans/task-d.6.2.md
• task-d55-opportunity-sales-workspace-refinement.md
• schema.ts
• crm-access.ts

Baseline Findings

1. The codebase has already moved materially toward a split lead + opportunity + quotation model in schema and UI direction, even though older ADR history still contains enquiry-centric language.
2. crm_leads and crm_opportunities already exist in schema.ts, which makes the unresolved terminology conflict a governance problem more than an implementation absence.
3. Hot-project and delivery timeline behavior already exist technically in opportunity and quotation fields, but the business definitions for Hot Project, Expected Award Date, and Expected Delivery Date were not frozen in one business document.
4. The repo has strong foundations for ownership, authorization, approval, PDF, reporting, and audit, so Phase R.0 should not redesign foundations. It should clarify business meaning that later phases must map onto those foundations.
5. Calendar and timeline concepts appear in plans and feature discussions, but there was no single approved statement that timeline is a generated view and calendar is a role-based workspace.

Artifacts Created

• Created the official blueprint draft: relationship-sales-workspace-blueprint-v1.md

Freeze Decisions Captured in This Pass

• ALLA OS is frozen as a Relationship-Driven Sales Workspace.
• Opportunity is frozen as the official sales-owned project lifecycle term.
• Quotation is frozen as the document lifecycle owner.
• Hot Project is frozen as a governed priority signal, not a lifecycle status.
• Timeline is frozen as a generated business view.
• Calendar is frozen as an operational workspace, not a standalone isolated module.
• Expected Award Date and Expected Delivery Date are frozen as governed business forecast concepts.
• Activity is frozen as the shared operational model that should unify follow-up-oriented work over time.

Remaining Governance Gaps

1. ADR reconciliation is still needed where accepted historical ADRs use enquiry while current schema and blueprint use opportunity.
2. The blueprint freezes the target activity model, but implementation still contains domain-specific follow-up structures that Phase R.1 should audit for consolidation strategy.
3. Calendar Workspace and generated Timeline are frozen conceptually here, but not yet decomposed into implementation contracts, datasets, or APIs.

Verification

• No schema, API, UI, service, or permission code was changed.
• No build or test command was needed because this pass only added documentation.

Next Recommended Step

Use this blueprint as the required input for Phase R.1 Business Capability Audit, with special focus on:

• terminology conflicts
• activity model duplication
• timeline / calendar capability mapping
• dashboard and forecast metric alignment