# Phase 4: Human Business Layer & Ecosystem Value (businessite_business)

## Status (8 September 2026) — eShop pilots + **NINO** · **Cake Couture** · **TA8 foundation = Colourcraft Auto**

### Product focus (TA track)
- **TA5 Done** → next is **TA8 Full Chat OS** (not TA6/TA7 yet). See [TA_TRACK_DEPENDENCIES.md](TA_TRACK_DEPENDENCIES.md).
- **Colourcraft Auto** is the **TA8 foundation business**: co-hosted on BusinesSite infrastructure; owner **Richard Chang**; Odoo 15 → 19; proves **customer + supplier digitization**, **staff digitization**, and **admin cost reduction**.
- Claim path: `join business Colourcraft Auto as owner` → registration docs + certified ID + same-date police affidavit → admin → ERP questionnaire → 3% or deploy+SLA → integration project → support SLA.

### Shipped on platform
- **Dedicated instances**: Environments **Start instance** (see [client_instances.md](client_instances.md)); slug = lowercase underscores; humans get `life_*` envs; businesses get brand slugs.
- **eShop Mall**: https://businessite.online/eshop — chrome-free atrium; search name/type/aura; cards → shelves.
- **Pilot merchants (eShop)**:
  - **madamthamie** — owner Nomathamsanqa Makhubela; `/eshop/madamthamie`.
  - **sevendotseven** — Caroh Chang; Verity Therapeutic; `/eshop/sevendotseven`.
  - **nino** — **NINO Digital Closet** (Carol Nana Shabalala to claim); SuperGrok cream/gold rails; multi-channel **shop / online / app+eyesWallet** prices fully inside cards; full product photo + compact initials placeholder; virtual try-on studio (`/e/nino/studio/`); domain **n-i-n-o.online** pending; team guide `guide eshop-nino`.
  - **cakecouture** — **Cake Couture** (Pamela Mkhize / Sanqa Holdings); brand portal **cakecouture.online** → `/cakecouture/` (story, shop, pre-order savings, eyesWallet, network, register); eShop `/eshop/cakecouture/` with **cake_couture** theme; `guide cakecouture`.
  - **godiscouture** — **Godi's Couture**, first **fashion atelier**. The public name is the house. Domain **godiscouture.online** → `/godiscouture/`. Commission desk (photograph or concept, 50% before processing, balance on delivery or collection). Public reel of photographs and films, no prices, shareable with the tagline Your style, My pride. Profile for the owner, staff, and customers. Deposit and balance invoices. CareerWIL (`CWIL-MILZET-2026`) is the admin back office. Installable on the phone from `/godiscouture/m`. Later houses at `/fashion//`. `guide godiscouture`.
- **Co-hosted business seed**: **colourcraft_auto** — Colourcraft Auto · owner_display_name Richard Chang · `business_type=external_erp`.
- **Shop name gate**: train-me / design eShop asks **business or eShop name first** + **mall vs own domain** (mall free; domain costs).
- **Host identity**: partner = human, company = BusinesSite; `shop_name` + `instance_slug` for brand; People vs Businesses menus.
- **Access**: eShop owner claim; **business owner claims** (`businessite.business.join.request`); platform **3%** or deploy+SLA.
- **Shelf UX + PayFast** + shelf ops (`deactivate product`, `end promo`) + multi-channel / pre-order pricing.
- **Access channel + domain ISP**: web / mobile / both; Porkbun; `guide isp-domains`.
- Docs: [ta8_colourcraft_foundation.md](ta8_colourcraft_foundation.md), [ESHOP_BACKEND_INTEGRATION.md](../ESHOP_BACKEND_INTEGRATION.md), [eshop_guides/](../eshop_guides/).

### Next (TA8 on Colourcraft)
- Full commercial mother-tongue POS (cash/card/credit/change)
- Digitize Colourcraft **customers, suppliers, and staff** on the business instance
- Voice/chat → Odoo process → reply loop for operations admins
- Cost-reduction visibility (administration overhead)
- Then open TA6 (Sensi) / TA7 (NATIVEnvoy) as verticals on the hardened Chat OS

## Objectives
- Create the `businessite_business` module for businesses registered by human (client) users.
- Enable linking of digital customer and supplier profiles to reduce costs.
- Allow support providers (during shifts) to process real tasks on the business's isolated Odoo instance.
- Introduce per-business feature flags and value-add tools (cost reduction, ecosystem linking).

## Key Technical Deliverables
- New module `businessite_business`.
- Models: `businessite.business`, `businessite.digital_profile` (customer/supplier), linking relations, `businessite.business_task`.
- Integration with client Odoo instances under `/client//` for task execution.
- Support provider task intake from the business layer (via `businessite_support`).
- Feature flag system (extend for per-business enablement from UAT).
- Chat commands: "register my business", "link customer X", "show my suppliers", "request task for sales".

## Homepage Impact
- Major "For Growing Businesses" section with customer/supplier linking demo, task processing example, and "Register Your Business" flow.

## Recruitment & Adoption Value
- Shows the real economic value (ecosystem + support + cost reduction).
- Primary hook for attracting paying business customers and demonstrating ROI to investors.

## Dependencies
- Phase 2 client instances and folders.
- Phase 3 support provider queue and shifts.
- Existing business_client and environment models.

## Success Criteria
- Human users can register businesses that get proper client instances.
- Support providers can process tasks originating from businesses.
- Digital profile linking and cost insights are functional and visible in chat.

## Further Reading
- [Business Layer & Digital Profiles Design](business_layer_design.md)
- [Task Processing Flow from Support to Client Odoo](business_task_flow.md)
- [Per-Business Feature Flags](feature_flags.md)

## Detailed Tasks by Layer and Role (for full implementation)

### Data Layer
- **Architect**: Define data models and relations for this phase (e.g. new tables for phase-specific entities).
- **Analyst**: Specify data validation rules, reports, and analytics for the phase.
- **Admin**: Seed initial data, configure access rights, and set up data migration scripts.
- **Developer**: Implement CRUD operations, constraints, and data sync logic.

### System Layer
- **Architect**: Design system architecture, services, and integration points for the phase.
- **Analyst**: Map system workflows, error handling, and performance requirements.
- **Admin**: Configure system parameters, cron jobs, and environment setups.
- **Developer**: Code the backend services, APIs, and background jobs for the phase.

### User Layer
- **Architect**: Design user interfaces and UX flows for the phase (web and mobile).
- **Analyst**: Define user stories, permissions, and role-based access for the phase.
- **Admin**: Set up user training, roles matrix, and onboarding for the phase.
- **Developer**: Build the UI components, controllers, and client-side logic for user interactions.

### Security Layer
- **Architect**: Design security model, authentication, and audit for phase features.
- **Analyst**: Identify security risks and compliance requirements for the phase.
- **Admin**: Configure groups, rules, and access controls; review logs.
- **Developer**: Implement security checks, encryption, and access decorators in code.

### App Layer
- **Architect**: Define app-specific features, integrations with mobile and external apps.
- **Analyst**: Specify app data models and sync requirements.
- **Admin**: Manage app configurations, publish settings, and user grants.
- **Developer**: Code the app-specific models, views, and integration points (e.g. chat commands, mobile features).