d-bis/Sankofa
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
6f28146ac303a225bce4a89c0658fe1c7b98ec13
Sankofa/docs/brand/product-naming.md
defiQUG 6f28146ac3 Initial Phoenix Sankofa Cloud setup 
- Complete project structure with Next.js frontend
- GraphQL API backend with Apollo Server
- Portal application with NextAuth
- Crossplane Proxmox provider
- GitOps configurations
- CI/CD pipelines
- Testing infrastructure (Vitest, Jest, Go tests)
- Error handling and monitoring
- Security hardening
- UI component library
- Documentation
2025-11-28 12:54:33 -08:00

7.4 KiB
Raw Blame History

Phoenix Sankofa Cloud: Product Architecture Naming System

Core Brand Name

Phoenix Sankofa Cloud™

The sovereign cloud born of fire and ancestral wisdom.

Product Architecture Names

Compute Services

PhoenixCore Compute

  • Purpose: Core compute engine
  • Meaning: Phoenix fire powering computation
  • Use Cases: Virtual machines, containers, serverless

SankofaEdge Nodes

  • Purpose: Edge computing nodes
  • Meaning: Edge nodes that remember and return data
  • Use Cases: CDN, edge processing, regional compute

AkanFire VM Engine

  • Purpose: Virtual machine engine
  • Meaning: Akan heritage + Phoenix fire power
  • Use Cases: High-performance VMs, specialized workloads

Storage Services

OkraVault Storage

  • Purpose: Object and block storage
  • Meaning: Okra = soul; Vault = secure storage
  • Use Cases: General-purpose storage, backups

Nananom Archive

  • Purpose: Long-term archival storage
  • Meaning: Nananom = ancestors; Archive = memory
  • Use Cases: Compliance archives, cold storage, historical data

Egg of the Phoenix Object Store

  • Purpose: Object storage for transformation
  • Meaning: Egg = rebirth symbol; Phoenix = transformation
  • Use Cases: Data lakes, transformation pipelines, staging

Networking Services

SankofaGrid Global Mesh

  • Purpose: Global network mesh
  • Meaning: Grid that remembers and connects globally
  • Use Cases: Global networking, inter-region connectivity

AkanSphere Edge Routing

  • Purpose: Edge routing and load balancing
  • Meaning: Akan heritage in global routing
  • Use Cases: Edge routing, traffic management, CDN

PhoenixFlight Network Fabric

  • Purpose: High-performance network fabric
  • Meaning: Phoenix flight = fast, powerful movement
  • Use Cases: High-bandwidth connections, data center networking

AI & Machine Learning Services

Firebird AI Engine

  • Purpose: Core AI/ML inference engine
  • Meaning: Firebird = Phoenix + AI transformation
  • Use Cases: Model inference, real-time AI, edge AI

Sankofa Memory Model

  • Purpose: AI models with memory and learning
  • Meaning: Models that remember and learn from past
  • Use Cases: Recursive learning, memory-augmented AI, context-aware models

Ancestral Neural Fabric

  • Purpose: Distributed AI training and inference
  • Meaning: Neural networks informed by ancestral patterns
  • Use Cases: Distributed training, federated learning, knowledge graphs

Security Services

Aegis of Akan Shield

  • Purpose: Comprehensive security platform
  • Meaning: Aegis = protection; Akan = heritage-based security
  • Use Cases: Threat protection, DDoS mitigation, security monitoring

PhoenixGuard IAM

  • Purpose: Identity and access management
  • Meaning: Phoenix = rebirth/transformation; Guard = protection
  • Use Cases: Authentication, authorization, identity management

Nsamankom Sentinel

  • Purpose: Security monitoring and threat detection
  • Meaning: Nsamankom = ancestors' protection; Sentinel = watchful guard
  • Use Cases: Security monitoring, threat detection, compliance

Identity Services

OkraID (Soul Identity Framework)

  • Purpose: Sovereign identity management
  • Meaning: Okra = soul; Identity = true self
  • Use Cases: Self-sovereign identity, decentralized identity, user authentication

AkanAuth Sovereign Identity Plane

  • Purpose: Authentication and authorization platform
  • Meaning: Akan = heritage-based; Sovereign = self-determined
  • Use Cases: Multi-factor authentication, SSO, identity federation

Database Services

SankofaGraph Database

  • Purpose: Graph database service
  • Meaning: Graph that remembers relationships
  • Use Cases: Knowledge graphs, relationship mapping, network analysis

PhoenixFire NoSQL

  • Purpose: NoSQL database service
  • Meaning: Phoenix fire = fast, powerful data
  • Use Cases: Document stores, key-value stores, time-series

Nananom Time Series

  • Purpose: Time-series database
  • Meaning: Nananom = ancestors; Time = historical data
  • Use Cases: Metrics, monitoring, historical analysis

Analytics Services

Sankofa Insights

  • Purpose: Business intelligence and analytics
  • Meaning: Insights that remember and learn from past
  • Use Cases: Dashboards, reporting, data visualization

PhoenixFlight Analytics

  • Purpose: Real-time analytics
  • Meaning: Fast, powerful analytics like Phoenix flight
  • Use Cases: Real-time dashboards, streaming analytics, live metrics

Integration Services

SankofaConnect Integration Hub

  • Purpose: API and integration platform
  • Meaning: Connections that remember and return
  • Use Cases: API management, service mesh, integrations

PhoenixBridge Data Pipeline

  • Purpose: Data integration and ETL
  • Meaning: Bridge that transforms data like Phoenix rebirth
  • Use Cases: ETL pipelines, data transformation, data movement

Developer Services

SankofaDev Platform

  • Purpose: Developer platform and tools
  • Meaning: Development that remembers best practices
  • Use Cases: CI/CD, developer tools, platform services

PhoenixForge Build Engine

  • Purpose: Build and deployment services
  • Meaning: Forge = creation; Phoenix = transformation
  • Use Cases: Build systems, deployment automation, container builds

Management Services

SankofaControl Plane

  • Purpose: Infrastructure management and orchestration
  • Meaning: Control that remembers and learns
  • Use Cases: Infrastructure as code, orchestration, management

PhoenixRealm Management

  • Purpose: Multi-cloud and multi-region management
  • Meaning: Realms = regions; Phoenix = global power
  • Use Cases: Multi-cloud management, global orchestration

Naming Conventions

Pattern Structure

  1. Phoenix- prefix*: Transformation, rebirth, power
  2. Sankofa- prefix*: Memory, return, ancestral wisdom
  3. Akan- prefix*: Cultural heritage, identity
  4. Okra- prefix*: Soul, identity, essence
  5. Nananom- prefix*: Ancestors, memory, guidance

Suffix Patterns

  • -Core: Core services
  • -Edge: Edge services
  • -Grid: Network/mesh services
  • -Vault: Storage services
  • -Guard: Security services
  • -Realm: Regional/global services
  • -Sphere: Global/distributed services

Product Hierarchy

Tier 1: Core Infrastructure

  • PhoenixCore Compute
  • OkraVault Storage
  • SankofaGrid Global Mesh

Tier 2: Specialized Services

  • Firebird AI Engine
  • Aegis of Akan Shield
  • SankofaGraph Database

Tier 3: Platform Services

  • SankofaDev Platform
  • SankofaControl Plane
  • PhoenixRealm Management

Brand Consistency

All product names should:

  • Reflect Phoenix–Sankofa brand values
  • Honor Akan cultural heritage appropriately
  • Convey technical capability
  • Maintain mythic and sovereign positioning
  • Be memorable and meaningful
  • Support global, multi-cultural audience

Future Product Names

As new services are developed, follow these principles:

  1. Meaningful: Names should have cultural and technical meaning
  2. Consistent: Follow established naming patterns
  3. Respectful: Honor cultural heritage appropriately
  4. Powerful: Convey capability and sovereignty
  5. Memorable: Easy to remember and pronounce globally
Reference in New Issue View Git Blame Copy Permalink