Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Vertical Presets (SSOT)

    Ring white-labels share one platform codebase: ring-platform.org. Verticals are selected by preset name in ring-config.json. Typed catalogs live under features/*/presets/<preset>.ts (and home under components/pages/home-presets/<preset>.tsx).

    Two sources of preset modules

    SourceWhat lives thereWhen it wins
    Platform (ring-platform.org)Shared niches (platform, agricultural, …)Base of every build
    Clone project dir (e.g. ring-greenfood-live)Branding, ring-config.json, custom <preset>.ts + registry overlaysOverwrite on collision after platform copy

    Build merge (clone truth prevails)

    Use ringdom-clone-build (ringdom-mcp):

    1. Copy latest ring-platform.org → build tmp (skips node_modules / .next / .git)
    2. Copy all files from the clone project dir onto that tmp — overwrite collisions
    3. Docker / CI build from the tmp dir

    Do not expect a thin overlay alone to be a runnable app — merge first.

    Two tiers of content

    TierWhatWhere
    1 — dataCategory lists, badge tokens, labelsring-config.json maps + locales/
    2 — typed logicEntity catalogs, zod/forms, niche field UIsfeatures/*/presets/<preset>.ts (platform and/or clone overlay)

    Config keys

    GreenFood sets entities / productFields / productBadges to "agricultural" and home.preset to "mvm-landing".

    Accessors (named preset SSOT)

    All use the configured *.preset string. If a singular key is unset, entities and productBadges fall back to productFields.preset, then "platform" — no hard-coded niche if/else.

    • getEntitiesPreset() → features/entities/presets registry
    • getHomePreset() → components/pages/home-presets registry
    • getProductFieldsPreset() / getProductFieldsPresets()
    • getProductBadgesPreset() / getProductBadgesPresets()

    Entities registry

    Rule: preset names appear in ring-config + the registry map. Consumers call getEntityTypes() / getEntityTypeList() — never import agricultural.ts directly.

    Custom niche on a clone: add features/entities/presets/<name>.ts in the clone project, overlay index.ts to register it, set entities.preset to that name, then ringdom-clone-build.

    Bundle discipline: sync catalogs are lightweight UI lists. Heavy ERP field catalogs live in *-erp.ts modules loaded only via async loadErpEntityTypes().

    Copy / icons layering (no hardcoded UI strings)

    • Catalog (presets/<name>.ts): ids, emoji, English fallback names/descriptions
    • Copy: locales/*/modules/entities.json → types.<id> + types.<id>Desc
    • Visual skin: components/entities/entity-type-icons.tsx TYPE_VISUALS map
    • Render: useEntityTypeLabel() / useEntityTypeDescription() — i18n first, catalog fallback

    Home landing registry

    Add a shared vertical (platform)

    1. Add features/entities/presets/<name>.ts (+ optional <name>-erp.ts)
    2. One line in ENTITIES_PRESET_REGISTRY (+ ERP_CATALOG_REGISTRY if needed)
    3. Optional landing → components/pages/home-presets/<name>.tsx
    4. Optional Tier-1 maps under productFieldsPresets / productBadgesPresets
    5. i18n keys in locales/*/modules/entities.json
    6. Document the preset id in ring-config.template.json

    Target roster: platform, agricultural, then tourism, sport, business, pet, auto, connect, technopark, manufacturing.

    Thin exclude (propagation)

    .reggie-propagate-exclude.json protects overlay-only paths from being overwritten by Reggie:

    • ring-config.json
    • public/logo*.svg, favicon.ico, public/branding/
    • locales/{en,uk,ru}/config.json, vendor.json
    • Custom features/*/presets/<clone-only>.ts (+ registry overlay) when not upstreamed yet
    • Tier-3 plug: lib/overlay/registry.ts only (maps). Do not exclude lib/overlay/types.ts or lib/overlay/runtime.ts — those are platform SSOT.

    Tier-3 overlay socket (platform) + plug (clone)

    PathOwnerRole
    lib/overlay/types.tsPlatformContracts
    lib/overlay/runtime.tsPlatformloadOverlayMessages / resolveOverlayHomeRail
    lib/overlay/registry.tsPlatform empty maps; clone overlays mapsDomain feature loaders

    Consumers import from @/lib/overlay/runtime. Clones never duplicate loaders in registry.ts.

    Operator checklist (calculator / Order Lab): Ringization playbook.

    Propagation source remains ring-platform.org → clones for shared code. Clone-local custom presets stay in the clone dir and win at ringdom-clone-build.

    GreenFood cutover

    Deprecated

    • Hard-coded if (productPreset === 'agricultural') in accessors
    • Per-clone custom-types.ts / overrides.ts without a named preset module
    • switch (vertical) in feature code — use the registry
    • Building Docker images from a thin overlay without platform merge

    Vertical Presets (SSOT)

    Ring white-labels share one platform codebase: ring-platform.org. Verticals are selected by preset name in ring-config.json. Typed catalogs live under features/*/presets/<preset>.ts (and home under components/pages/home-presets/<preset>.tsx).

    Two sources of preset modules

    SourceWhat lives thereWhen it wins
    Platform (ring-platform.org)Shared niches (platform, agricultural, …)Base of every build
    Clone project dir (e.g. ring-greenfood-live)Branding, ring-config.json, custom <preset>.ts + registry overlaysOverwrite on collision after platform copy

    Build merge (clone truth prevails)

    Use ringdom-clone-build (ringdom-mcp):

    1. Copy latest ring-platform.org → build tmp (skips node_modules / .next / .git)
    2. Copy all files from the clone project dir onto that tmp — overwrite collisions
    3. Docker / CI build from the tmp dir

    Do not expect a thin overlay alone to be a runnable app — merge first.

    Two tiers of content

    TierWhatWhere
    1 — dataCategory lists, badge tokens, labelsring-config.json maps + locales/
    2 — typed logicEntity catalogs, zod/forms, niche field UIsfeatures/*/presets/<preset>.ts (platform and/or clone overlay)

    Config keys

    GreenFood sets entities / productFields / productBadges to "agricultural" and home.preset to "mvm-landing".

    Accessors (named preset SSOT)

    All use the configured *.preset string. If a singular key is unset, entities and productBadges fall back to productFields.preset, then "platform" — no hard-coded niche if/else.

    • getEntitiesPreset() → features/entities/presets registry
    • getHomePreset() → components/pages/home-presets registry
    • getProductFieldsPreset() / getProductFieldsPresets()
    • getProductBadgesPreset() / getProductBadgesPresets()

    Entities registry

    Rule: preset names appear in ring-config + the registry map. Consumers call getEntityTypes() / getEntityTypeList() — never import agricultural.ts directly.

    Custom niche on a clone: add features/entities/presets/<name>.ts in the clone project, overlay index.ts to register it, set entities.preset to that name, then ringdom-clone-build.

    Bundle discipline: sync catalogs are lightweight UI lists. Heavy ERP field catalogs live in *-erp.ts modules loaded only via async loadErpEntityTypes().

    Copy / icons layering (no hardcoded UI strings)

    • Catalog (presets/<name>.ts): ids, emoji, English fallback names/descriptions
    • Copy: locales/*/modules/entities.json → types.<id> + types.<id>Desc
    • Visual skin: components/entities/entity-type-icons.tsx TYPE_VISUALS map
    • Render: useEntityTypeLabel() / useEntityTypeDescription() — i18n first, catalog fallback

    Home landing registry

    Add a shared vertical (platform)

    1. Add features/entities/presets/<name>.ts (+ optional <name>-erp.ts)
    2. One line in ENTITIES_PRESET_REGISTRY (+ ERP_CATALOG_REGISTRY if needed)
    3. Optional landing → components/pages/home-presets/<name>.tsx
    4. Optional Tier-1 maps under productFieldsPresets / productBadgesPresets
    5. i18n keys in locales/*/modules/entities.json
    6. Document the preset id in ring-config.template.json

    Target roster: platform, agricultural, then tourism, sport, business, pet, auto, connect, technopark, manufacturing.

    Thin exclude (propagation)

    .reggie-propagate-exclude.json protects overlay-only paths from being overwritten by Reggie:

    • ring-config.json
    • public/logo*.svg, favicon.ico, public/branding/
    • locales/{en,uk,ru}/config.json, vendor.json
    • Custom features/*/presets/<clone-only>.ts (+ registry overlay) when not upstreamed yet
    • Tier-3 plug: lib/overlay/registry.ts only (maps). Do not exclude lib/overlay/types.ts or lib/overlay/runtime.ts — those are platform SSOT.

    Tier-3 overlay socket (platform) + plug (clone)

    PathOwnerRole
    lib/overlay/types.tsPlatformContracts
    lib/overlay/runtime.tsPlatformloadOverlayMessages / resolveOverlayHomeRail
    lib/overlay/registry.tsPlatform empty maps; clone overlays mapsDomain feature loaders

    Consumers import from @/lib/overlay/runtime. Clones never duplicate loaders in registry.ts.

    Operator checklist (calculator / Order Lab): Ringization playbook.

    Propagation source remains ring-platform.org → clones for shared code. Clone-local custom presets stay in the clone dir and win at ringdom-clone-build.

    GreenFood cutover

    Deprecated

    • Hard-coded if (productPreset === 'agricultural') in accessors
    • Per-clone custom-types.ts / overrides.ts without a named preset module
    • switch (vertical) in feature code — use the registry
    • Building Docker images from a thin overlay without platform merge

    Vertical Presets (SSOT)

    Ring white-labels share one platform codebase: ring-platform.org. Verticals are selected by preset name in ring-config.json. Typed catalogs live under features/*/presets/<preset>.ts (and home under components/pages/home-presets/<preset>.tsx).

    Two sources of preset modules

    SourceWhat lives thereWhen it wins
    Platform (ring-platform.org)Shared niches (platform, agricultural, …)Base of every build
    Clone project dir (e.g. ring-greenfood-live)Branding, ring-config.json, custom <preset>.ts + registry overlaysOverwrite on collision after platform copy

    Build merge (clone truth prevails)

    Use ringdom-clone-build (ringdom-mcp):

    1. Copy latest ring-platform.org → build tmp (skips node_modules / .next / .git)
    2. Copy all files from the clone project dir onto that tmp — overwrite collisions
    3. Docker / CI build from the tmp dir

    Do not expect a thin overlay alone to be a runnable app — merge first.

    Two tiers of content

    TierWhatWhere
    1 — dataCategory lists, badge tokens, labelsring-config.json maps + locales/
    2 — typed logicEntity catalogs, zod/forms, niche field UIsfeatures/*/presets/<preset>.ts (platform and/or clone overlay)

    Config keys

    GreenFood sets entities / productFields / productBadges to "agricultural" and home.preset to "mvm-landing".

    Accessors (named preset SSOT)

    All use the configured *.preset string. If a singular key is unset, entities and productBadges fall back to productFields.preset, then "platform" — no hard-coded niche if/else.

    • getEntitiesPreset() → features/entities/presets registry
    • getHomePreset() → components/pages/home-presets registry
    • getProductFieldsPreset() / getProductFieldsPresets()
    • getProductBadgesPreset() / getProductBadgesPresets()

    Entities registry

    Rule: preset names appear in ring-config + the registry map. Consumers call getEntityTypes() / getEntityTypeList() — never import agricultural.ts directly.

    Custom niche on a clone: add features/entities/presets/<name>.ts in the clone project, overlay index.ts to register it, set entities.preset to that name, then ringdom-clone-build.

    Bundle discipline: sync catalogs are lightweight UI lists. Heavy ERP field catalogs live in *-erp.ts modules loaded only via async loadErpEntityTypes().

    Copy / icons layering (no hardcoded UI strings)

    • Catalog (presets/<name>.ts): ids, emoji, English fallback names/descriptions
    • Copy: locales/*/modules/entities.json → types.<id> + types.<id>Desc
    • Visual skin: components/entities/entity-type-icons.tsx TYPE_VISUALS map
    • Render: useEntityTypeLabel() / useEntityTypeDescription() — i18n first, catalog fallback

    Home landing registry

    Add a shared vertical (platform)

    1. Add features/entities/presets/<name>.ts (+ optional <name>-erp.ts)
    2. One line in ENTITIES_PRESET_REGISTRY (+ ERP_CATALOG_REGISTRY if needed)
    3. Optional landing → components/pages/home-presets/<name>.tsx
    4. Optional Tier-1 maps under productFieldsPresets / productBadgesPresets
    5. i18n keys in locales/*/modules/entities.json
    6. Document the preset id in ring-config.template.json

    Target roster: platform, agricultural, then tourism, sport, business, pet, auto, connect, technopark, manufacturing.

    Thin exclude (propagation)

    .reggie-propagate-exclude.json protects overlay-only paths from being overwritten by Reggie:

    • ring-config.json
    • public/logo*.svg, favicon.ico, public/branding/
    • locales/{en,uk,ru}/config.json, vendor.json
    • Custom features/*/presets/<clone-only>.ts (+ registry overlay) when not upstreamed yet
    • Tier-3 plug: lib/overlay/registry.ts only (maps). Do not exclude lib/overlay/types.ts or lib/overlay/runtime.ts — those are platform SSOT.

    Tier-3 overlay socket (platform) + plug (clone)

    PathOwnerRole
    lib/overlay/types.tsPlatformContracts
    lib/overlay/runtime.tsPlatformloadOverlayMessages / resolveOverlayHomeRail
    lib/overlay/registry.tsPlatform empty maps; clone overlays mapsDomain feature loaders

    Consumers import from @/lib/overlay/runtime. Clones never duplicate loaders in registry.ts.

    Operator checklist (calculator / Order Lab): Ringization playbook.

    Propagation source remains ring-platform.org → clones for shared code. Clone-local custom presets stay in the clone dir and win at ringdom-clone-build.

    GreenFood cutover

    Deprecated

    • Hard-coded if (productPreset === 'agricultural') in accessors
    • Per-clone custom-types.ts / overrides.ts without a named preset module
    • switch (vertical) in feature code — use the registry
    • Building Docker images from a thin overlay without platform merge
    json
    
    {
      "entities": { "preset": "platform" },
      "home": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" },
      "productFieldsPresets": {
        "platform": { "storeCategories": ["commerce", "education", "…"] },
        "agricultural": { "storeCategories": ["organic-produce", "honey-sweets", "…"] }
      },
      "productBadgesPresets": {
        "platform": { "productBadges": ["new", "featured", "popular"] },
        "agricultural": { "productBadges": ["organic", "local", "regenerative"] }
      }
    }
    text
    
    ringdom-clone-build({ project_name: "ring-greenfood-live", dry_run?: true })
    → .ringdom-build/<project>/<timestamp>
    text
    
    features/entities/presets/
      types.ts             # EntityTypeCatalog contract
      platform.ts          # export const entityTypes (26 industries)
      agricultural.ts      # healthy-living UI catalog (lightweight)
      agricultural-erp.ts  # heavy ERP field catalogs — async-only via loadErpEntityTypes()
      index.ts             # ENTITIES_PRESET_REGISTRY + getEntityTypes()
    text
    
    components/pages/
      home.tsx                       # platform default landing
      home-presets/mvm-landing.tsx   # multi-vendor-marketplace e-commerce landing
      home-content-resolver.tsx      # HOME_PRESET_REGISTRY + getHomePreset()
    text
    
    ensure ring-config: entities/productFields/productBadges = agricultural, home = mvm-landing
    keep branding + locale deltas in ring-greenfood-live
    ringdom-clone-build({ project_name: "ring-greenfood-live" })
    build/deploy from .ringdom-build/ring-greenfood-live/<stamp>
    json
    
    {
      "entities": { "preset": "platform" },
      "home": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" },
      "productFieldsPresets": {
        "platform": { "storeCategories": ["commerce", "education", "…"] },
        "agricultural": { "storeCategories": ["organic-produce", "honey-sweets", "…"] }
      },
      "productBadgesPresets": {
        "platform": { "productBadges": ["new", "featured", "popular"] },
        "agricultural": { "productBadges": ["organic", "local", "regenerative"] }
      }
    }
    text
    
    ringdom-clone-build({ project_name: "ring-greenfood-live", dry_run?: true })
    → .ringdom-build/<project>/<timestamp>
    text
    
    features/entities/presets/
      types.ts             # EntityTypeCatalog contract
      platform.ts          # export const entityTypes (26 industries)
      agricultural.ts      # healthy-living UI catalog (lightweight)
      agricultural-erp.ts  # heavy ERP field catalogs — async-only via loadErpEntityTypes()
      index.ts             # ENTITIES_PRESET_REGISTRY + getEntityTypes()
    text
    
    components/pages/
      home.tsx                       # platform default landing
      home-presets/mvm-landing.tsx   # multi-vendor-marketplace e-commerce landing
      home-content-resolver.tsx      # HOME_PRESET_REGISTRY + getHomePreset()
    text
    
    ensure ring-config: entities/productFields/productBadges = agricultural, home = mvm-landing
    keep branding + locale deltas in ring-greenfood-live
    ringdom-clone-build({ project_name: "ring-greenfood-live" })
    build/deploy from .ringdom-build/ring-greenfood-live/<stamp>
    json
    
    {
      "entities": { "preset": "platform" },
      "home": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" },
      "productFieldsPresets": {
        "platform": { "storeCategories": ["commerce", "education", "…"] },
        "agricultural": { "storeCategories": ["organic-produce", "honey-sweets", "…"] }
      },
      "productBadgesPresets": {
        "platform": { "productBadges": ["new", "featured", "popular"] },
        "agricultural": { "productBadges": ["organic", "local", "regenerative"] }
      }
    }
    text
    
    ringdom-clone-build({ project_name: "ring-greenfood-live", dry_run?: true })
    → .ringdom-build/<project>/<timestamp>
    text
    
    features/entities/presets/
      types.ts             # EntityTypeCatalog contract
      platform.ts          # export const entityTypes (26 industries)
      agricultural.ts      # healthy-living UI catalog (lightweight)
      agricultural-erp.ts  # heavy ERP field catalogs — async-only via loadErpEntityTypes()
      index.ts             # ENTITIES_PRESET_REGISTRY + getEntityTypes()
    text
    
    components/pages/
      home.tsx                       # platform default landing
      home-presets/mvm-landing.tsx   # multi-vendor-marketplace e-commerce landing
      home-content-resolver.tsx      # HOME_PRESET_REGISTRY + getHomePreset()
    text
    
    ensure ring-config: entities/productFields/productBadges = agricultural, home = mvm-landing
    keep branding + locale deltas in ring-greenfood-live
    ringdom-clone-build({ project_name: "ring-greenfood-live" })
    build/deploy from .ringdom-build/ring-greenfood-live/<stamp>
    1. Docs
    2. /Customization
    3. /Vertical Presets (SSOT)

    Updated Jul 14, 20264 min listen

    1. Docs
    2. /Customization
    3. /Vertical Presets (SSOT)

    Updated Jul 14, 20264 min listen

    1. Docs
    2. /Customization
    3. /Vertical Presets (SSOT)

    Updated Jul 14, 20264 min listen