СТАНДАРТЫ ВЫДЕЛЕНИЯ РЕСУРСОВ

Server (физический сервер)
└── Instance (процесс postgres)
    └── Database (catalog)
        └── Schema (namespace)
            └── Tables (таблицы)

Server
└── Instance (mysqld)
    └── Database (= Schema в MySQL)
        └── Tables

business-unit:
  name: pirotehnika

  resources:
    database:
      isolation: isolated          # Отдельная схема
      instance: shared-postgresql  # Общий инстанс
      schema: piro_*               # Схема с префиксом
      naming: "{unit_code}_*"      # piro_products, piro_orders

    storage:
      isolation: isolated          # Отдельный bucket/path
      type: s3
      bucket: hub
      path: "/business-units/pirotehnika/"

    network:
      domains:
        - pirotehnika.spb.ru
        - www.pirotehnika.spb.ru

    credentials:
      isolation: dedicated         # Свои credentials
      storage: vault
      path: "/business-units/pirotehnika/"

channel:
  name: retail
  business_unit: pirotehnika

  resources:
    database:
      isolation: shared            # Префикс внутри схемы бизнеса
      schema: piro_retail          # Схема канала
      naming: "retail_*"           # retail_orders, retail_customers

    storage:
      path: "/business-units/pirotehnika/channels/retail/"

    network:
      domains:
        - pirotehnika.spb.ru       # Основной домен бизнеса

system:
  name: pim
  type: service

  resources:
    database:
      isolation: isolated          # Отдельная схема
      instance: shared-postgresql
      schema: pim_*
      naming: "pim_*"              # pim_products, pim_brands

    storage:
      isolation: isolated
      path: "/systems/pim/"

    compute:
      isolation: shared            # Общий Docker/K8s
      type: container
      limits:
        cpu: "1"
        memory: "2Gi"

    network:
      ports:
        - 8080                     # API port
      internal_domain: pim.internal

    credentials:
      isolation: dedicated
      path: "/systems/pim/"

client-project:
  name: ozon-integration

  resources:
    database:
      isolation: shared            # Обычно использует существующие
      # ИЛИ временная БД для разработки:
      schema: temp_ozon_integration
      lifetime: 3_months           # Временная

    storage:
      path: "/client-projects/ozon-integration/"
      lifetime: 6_months           # Архивируется после завершения

    compute:
      isolation: shared            # Dev окружение

Формат: {entity_type}_{entity_name}_{resource_type}

Примеры:
├── bu_pirotehnika               ← Business Unit schema
├── bu_lideravto
├── sys_pim                      ← System schema
├── sys_crm
├── chan_retail                  ← Channel schema
└── temp_project_ozon            ← Temporary (client project)

Формат: {prefix}_{table_name}

Примеры:
Business Unit (pirotehnika):
├── piro_products
├── piro_orders
├── piro_customers
└── piro_analytics

System (PIM):
├── pim_products
├── pim_brands
└── pim_categories

Channel (retail):
├── retail_cart
├── retail_wishlist
└── retail_reviews

Формат: /{level}/{type}/{name}/

Примеры:
/business-units/pirotehnika/
/business-units/pirotehnika/channels/retail/
/systems/pim/
/systems/crm/
/client-projects/ozon-integration/
/temp/2025-12-22-experiment/

Формат: {type}-{name}-{env}

Примеры:
sys-pim-prod                     ← System в production
sys-pim-dev                      ← System в dev
bu-pirotehnika-site-prod         ← Business Unit site
temp-ozon-integration-dev        ← Temporary project

# Template: business-unit-resources.yaml
business_unit:
  code: "{unit_code}"              # 4-6 букв, например: piro, lider
  name: "{full_name}"

  allocate:
    database:
      instance: /L3-INFRA/database-engines/postgresql-001
      action: create_schema
      schema: "bu_{unit_code}"
      owner: "bu_{unit_code}_owner"
      credentials:
        user: "bu_{unit_code}_rw"
        password: generate_random
        vault_path: "/business-units/{unit_code}/db"

    storage:
      provider: /L3-INFRA/storage/object/s3/hub
      action: create_path
      path: "/business-units/{unit_code}/"
      credentials:
        access_key: generate_random
        secret_key: generate_random
        vault_path: "/business-units/{unit_code}/s3"

    network:
      action: register_domain
      primary_domain: "{unit_code}.example.com"

  inherit_from:
    - /GROUP/shared/connectors/postgresql
    - /GROUP/shared/templates/business-unit

# Создать ресурсы для новой бизнес-единицы
architect create business-unit --code piro --name "Pirotehnika"

# Создаст:
# - Schema: bu_piro
# - DB User: bu_piro_rw
# - S3 Path: /business-units/piro/
# - Credentials в vault

# Template: system-resources.yaml
system:
  name: "{system_name}"
  type: "{service|data|integration}"

  allocate:
    database:
      instance: /L3-INFRA/database-engines/postgresql-001
      action: create_schema
      schema: "sys_{system_name}"
      owner: "sys_{system_name}_owner"

    storage:
      provider: /L3-INFRA/storage/object/s3/hub
      path: "/systems/{system_name}/"

    compute:
      provider: /L3-INFRA/compute/containers/docker
      action: create_container
      image: "{system_name}:latest"
      resources:
        cpu: "1"
        memory: "2Gi"
      ports:
        - 8080

  inherit_from:
    - /GROUP/shared/connectors/postgresql
    - /GROUP/shared/templates/system

# Template: channel-resources.yaml
channel:
  name: "{channel_name}"
  business_unit: "{parent_unit_code}"

  allocate:
    database:
      # Наследует схему от бизнес-единицы
      schema: "bu_{parent_unit_code}"
      # Создаёт таблицы с префиксом
      table_prefix: "{channel_name}_"

    storage:
      # Наследует path от бизнес-единицы
      path: "/business-units/{parent_unit_code}/channels/{channel_name}/"

  inherit_from:
    - /L0-ORG/business-units/{parent_unit_code}
    - /GROUP/shared/templates/channel

Parent → Child наследует по умолчанию

Business Unit (pirotehnika)
├── database: bu_piro
├── storage: /business-units/pirotehnika/
├── credentials: vault:/business-units/pirotehnika/
    ↓ inherits

Channel (retail)
├── database: bu_piro                              ← Наследовано
├── table_prefix: retail_                          ← Добавлено
├── storage: /business-units/pirotehnika/channels/retail/  ← Специализировано
└── credentials: vault:/business-units/pirotehnika/        ← Наследовано

# Пример: Channel требует отдельную схему (переопределение)
channel:
  name: ozon
  business_unit: pirotehnika

  override:
    database:
      reason: "High load, needs isolation"
      schema: "bu_piro_ozon"           ← Отдельная схема
      isolation: isolated               ← Повышена изоляция

  allocate:
    compute:
      reason: "Critical integration"
      type: dedicated                   ← Выделенный контейнер
      resources:
        cpu: "2"
        memory: "4Gi"

# Development
pim-dev:
  database:
    schema: dev_common
    prefix: pim_
  storage:
    path: /dev/pim/
  compute:
    host: dev-shared

# Staging
pim-staging:
  database:
    schema: staging_pim
  storage:
    path: /staging/pim/
  compute:
    container: pim-staging

# Production
pim-prod:
  database:
    schema: pim_prod
  storage:
    path: /production/pim/
  compute:
    container: pim-prod
    resources:
      cpu: "2"
      memory: "4Gi"

1. REQUEST     → Запрос на ресурсы (template + params)
2. REVIEW      → Проверка необходимости
3. APPROVE     → Утверждение (для dedicated+)
4. ALLOCATE    → Выделение ресурсов
5. CONFIGURE   → Настройка и подключение
6. DOCUMENT    → Документирование в index.yaml
7. MONITOR     → Мониторинг использования
8. CLEANUP     → Удаление при необходимости

# Создать бизнес-единицу
architect resource allocate business-unit \
  --code piro \
  --name "Pirotehnika" \
  --template business-unit-resources.yaml

# Создать систему
architect resource allocate system \
  --name pim \
  --type service \
  --isolation isolated \
  --template system-resources.yaml

# Создать канал
architect resource allocate channel \
  --name retail \
  --parent pirotehnika \
  --template channel-resources.yaml

# Создать временные ресурсы для проекта
architect resource allocate temp \
  --name ozon-integration \
  --lifetime 3months \
  --template temp-project-resources.yaml

# L0-ORG/business-units/pirotehnika/index.yaml
name: "Pirotehnika"
type: business-unit
code: piro

resources:
  allocated:
    database:
      instance: /L3-INFRA/database-engines/postgresql-001
      schema: bu_piro
      user: bu_piro_rw
      connection: /L2-DATA/connections/bu-piro-db

    storage:
      provider: /L3-INFRA/storage/object/s3/hub
      path: /business-units/pirotehnika/
      connection: /L2-DATA/connections/bu-piro-s3

    credentials:
      vault_path: /business-units/pirotehnika/

  inherited_by:
    - /L0-ORG/business-units/pirotehnika/channels/retail
    - /L0-ORG/business-units/pirotehnika/channels/ozon

temp_resources:
  retention:
    client_projects:
      active: keep
      completed: 6_months      # Архивировать через 6 месяцев
      archived: 2_years        # Удалить через 2 года

    dev_experiments:
      active: keep
      inactive_30d: archive    # Архивировать если не используется 30 дней
      archived: 3_months       # Удалить через 3 месяца

cleanup_policy:
  database:
    empty_schemas:
      check: monthly
      action: notify_owner

    unused_30d:
      check: monthly
      action: archive_candidate

  storage:
    empty_paths:
      check: weekly
      action: delete_after_30d

  compute:
    stopped_containers:
      check: daily
      action: delete_after_7d

access_policy:
  business_unit:
    owner: full_access
    members: read_write
    guests: read_only

  system:
    service_account: read_write
    developers: read_only_prod, read_write_dev
    ops: full_access

  temporary_project:
    project_team: full_access
    expires_with_project: true

Правило: Каждая сущность имеет собственные credentials

Business Unit: bu_piro_rw / bu_piro_ro
System: sys_pim_rw / sys_pim_ro
Channel: наследует от Business Unit ИЛИ собственные

Хранение: HashiCorp Vault
Path: /{level}/{type}/{name}/credentials

Shared → Isolated → Dedicated → Standalone
  ✅       ✅          ✅           ✅

Standalone → Dedicated → Isolated → Shared
   ❌           ❌          ❌         ❌

# Можно временно повысить для нагрузочных тестов
load_test:
  duration: 7_days
  isolation: dedicated
  rollback_to: isolated

/PLATFORM/
├── applications/          ← ЗДЕСЬ
│   ├── nocodb/
│   ├── n8n/
│   ├── metabase/
│   └── minio/
│
└── infrastructure/        ← Базовая инфраструктура
    ├── postgresql/
    ├── redis/
    └── nginx/

platform_application:
  name: nocodb
  type: platform_app
  scope: shared              # Доступно всем

  resources:
    database:
      isolation: isolated    # Своя схема
      instance: /L3-INFRA/database-engines/postgresql-001
      schema: platform_nocodb

    storage:
      isolation: isolated
      path: /platform/applications/nocodb/

    compute:
      isolation: dedicated   # Свой контейнер
      container: platform-nocodb-prod
      resources:
        cpu: "2"
        memory: "4Gi"

    network:
      domain: nocodb.platform.internal
      ports:
        - 8080

  used_by:
    - /L0-ORG/business-units/pirotehnika/services/pim
    - /L0-ORG/business-units/lideravto/services/crm

  usage_tracking:
    enabled: true
    metrics:
      - api_calls
      - storage_used
      - active_users

# L0-ORG/business-units/pirotehnika/services/pim/index.yaml
service:
  name: pim
  business_unit: pirotehnika
  type: business_unit_service

  resources:
    database:
      # Наследует от бизнес-единицы
      schema: bu_piro
      prefix: pim_

    uses_platform_apps:
      - name: nocodb
        app: /PLATFORM/applications/nocodb
        workspace: piro-pim
        credentials:
          vault_path: /business-units/pirotehnika/services/pim/nocodb

    uses_infra:
      - /L3-INFRA/database-engines/postgresql-001

# Template: platform-app-resources.yaml
platform_application:
  name: "{app_name}"
  version: "{version}"

  allocate:
    database:
      instance: /L3-INFRA/database-engines/postgresql-001
      action: create_schema
      schema: "platform_{app_name}"

    storage:
      provider: /L3-INFRA/storage/object/s3/hub
      path: "/platform/applications/{app_name}/"

    compute:
      provider: /L3-INFRA/compute/containers/docker
      action: create_container
      image: "{app_name}:{version}"
      resources:
        cpu: "2"
        memory: "4Gi"
      ports:
        - 8080

    network:
      domain: "{app_name}.platform.internal"

  multi_tenancy:
    enabled: true
    isolation_level: workspace

  inherit_from:
    - /PLATFORM/templates/platform-app

/L0-ORG/business-units/pirotehnika/
├── index.yaml
├── SPECIFICATION.md
├── services/              ← ЗДЕСЬ
│   ├── pim/
│   ├── analytics/
│   └── integration-hub/
└── channels/
    └── retail/

business_unit_service:
  business_unit: pirotehnika
  name: pim
  type: service

  resources:
    database:
      # Наследует от бизнес-единицы
      schema: bu_piro
      prefix: pim_                    # Префикс таблиц
      tables:
        - pim_products
        - pim_brands
        - pim_categories

    storage:
      # Специализирует путь
      path: /business-units/pirotehnika/services/pim/

    compute:
      isolation: shared               # В контексте бизнес-единицы
      # ИЛИ использует платформенное приложение:
      uses_app: /PLATFORM/applications/nocodb

  uses_platform_apps:
    - nocodb                          # Использует NocoDB

  credentials:
    # Наследует от бизнес-единицы
    vault_path: /business-units/pirotehnika/services/pim/

business_unit:
  code: lider
  name: "LiderAvto"

resources_allocated:
  database:
    instance: /L3-INFRA/database-engines/postgresql-001
    schema: bu_lider
    tables: []
    user: bu_lider_rw

  storage:
    path: /business-units/lideravto/
    size_limit: 100GB

  network:
    domain: lideravto.ru

  credentials:
    vault_path: /business-units/lideravto/

connections_created:
  - /L2-DATA/connections/bu-lider-db
  - /L2-DATA/connections/bu-lider-s3

platform_application:
  name: nocodb
  version: "0.200.0"

resources_allocated:
  database:
    instance: /L3-INFRA/database-engines/postgresql-001
    schema: platform_nocodb

  storage:
    path: /platform/applications/nocodb/

  compute:
    container: platform-nocodb-prod
    image: nocodb/nocodb:0.200.0
    resources:
      cpu: "2"
      memory: "4Gi"
    ports:
      - 8080

  network:
    domain: nocodb.platform.internal

used_by:
  - /L0-ORG/business-units/pirotehnika/services/pim
  - /L0-ORG/business-units/lideravto/services/crm

connections_created:
  - /L2-DATA/connections/platform-nocodb-db

business_unit_service:
  business_unit: pirotehnika
  name: pim
  type: service

resources_allocated:
  database:
    # Наследует схему от бизнес-единицы
    instance: /L3-INFRA/database-engines/postgresql-001
    schema: bu_piro             # Схема бизнеса
    prefix: pim_                # Префикс для таблиц
    tables:
      - pim_products
      - pim_brands
      - pim_categories
      - pim_attributes

  storage:
    # Специализирует путь
    path: /business-units/pirotehnika/services/pim/

  uses_platform_apps:
    - name: nocodb
      app: /PLATFORM/applications/nocodb
      workspace: piro-pim
      credentials:
        vault_path: /business-units/pirotehnika/services/pim/nocodb

inherited_from:
  - /L0-ORG/business-units/pirotehnika

connections_created:
  - /L2-DATA/connections/bu-piro-pim-nocodb

# /PLATFORM/applications/pim/SPECIFICATION.md
type: platform_application
name: pim
description: "Product Information Management"

components:
  database:
    tables:
      - name: pim_products
        fields:
          - id: bigint
          - name: varchar
          - sku: varchar
          - brand_id: bigint

      - name: pim_brands
        fields:
          - id: bigint
          - name: varchar

      - name: pim_categories
      - name: pim_attributes

    functions:
      - get_product_by_id(id bigint)
      - search_products(query text)
      - update_product_attrs(id bigint, attrs jsonb)

  api:
    type: REST
    endpoints:
      - method: GET
        path: /products
        description: "Список товаров"

      - method: GET
        path: /products/{id}
        description: "Один товар"

      - method: POST
        path: /products
        description: "Создать товар"

  ui:
    type: web_interface
    pages:
      - products-list
      - product-editor
      - brands-management

# /L0-ORG/business-units/pirotehnika/connections/pim.yaml
connection:
  name: pim-pirotehnika
  type: service_connection

  service_definition: /PLATFORM/applications/pim

  deployment:
    database:
      instance: /L3-INFRA/database-engines/postgresql-001
      schema: bu_piro              # Схема бизнес-единицы
      prefix: pim_                 # Префикс таблиц

      # Реально созданные таблицы:
      tables:
        - bu_piro.pim_products     # В схеме bu_piro
        - bu_piro.pim_brands
        - bu_piro.pim_categories
        - bu_piro.pim_attributes

    api:
      base_url: https://pim.pirotehnika.internal
      credentials:
        vault_path: /business-units/pirotehnika/connections/pim

    ui:
      url: https://pim.pirotehnika.spb.ru
      access:
        roles:
          - manager       # Полный доступ
          - operator      # Только просмотр и редактирование

Сервер: postgresql-001                    ← L3-INFRA (физический сервер)
└── Инстанс: postgres:5432                ← L3-INFRA (процесс PostgreSQL)
    └── База данных: postgres             ← L3-INFRA (catalog, общий)
        └── Схема: bu_piro                ← L0-ORG (namespace бизнес-единицы)
            └── Таблицы:                  ← L0-ORG/services
                ├── pim_products          ← Префикс pim_ (сервис PIM)
                ├── pim_brands
                ├── pim_categories
                ├── retail_cart           ← Префикс retail_ (канал retail)
                └── retail_orders

Оператор открывает UI:
  https://pim.pirotehnika.spb.ru
    ↓
UI подключается к API:
  https://pim.pirotehnika.internal/api/products
    ↓
API читает данные:
  SELECT * FROM bu_piro.pim_products
    ↓
Данные через CONNECTION:
  /L0-ORG/business-units/pirotehnika/connections/pim.yaml
    ↓
Connection ссылается на SERVICE:
  /PLATFORM/applications/pim/