7e915e8c10
Some checks failed
API CI / API Lint (push) Successful in 47s
API CI / API Type Check (push) Failing after 45s
API CI / API Test (push) Successful in 1m1s
API CI / API Build (push) Failing after 47s
API CI / Build Docker Image (push) Has been skipped
CD Pipeline / Deploy to Staging (push) Failing after 26s
CI Pipeline / Lint and Type Check (push) Failing after 30s
CI Pipeline / Build (push) Has been skipped
CI Pipeline / Test Backend (push) Failing after 1m22s
CI Pipeline / Test Frontend (push) Failing after 33s
CI Pipeline / Security Scan (push) Failing after 1m26s
Deploy to Staging / Deploy to Staging (push) Failing after 32s
Test Suite / frontend-tests (push) Failing after 31s
Test Suite / api-tests (push) Failing after 46s
Test Suite / blockchain-tests (push) Failing after 25s
Type Check / type-check (map[directory:. name:root]) (push) Failing after 21s
Type Check / type-check (map[directory:api name:api]) (push) Failing after 20s
Type Check / type-check (map[directory:portal name:portal]) (push) Failing after 19s
CD Pipeline / Deploy to Production (push) Has been skipped
Sovereign Stack Services - Phoenix Cloud Services
This directory contains documentation for all Sovereign Stack services offered by Phoenix Cloud Services in the Sankofa marketplace.
Overview
The Sovereign Stack is a comprehensive set of services designed to replace reliance on external platforms with owned core primitives, while retaining optional provider integrations via adapters. All services follow the principle that no provider is System of Record (SoR) - provider outages must not affect balances, identity, wallets, audit, or message delivery.
Services
Core Services
- Phoenix Ledger Service - Double-entry ledger with virtual accounts
- Phoenix Identity Service - Identity, auth, and policy management
- Phoenix Wallet Registry - Wallet mapping and signing policy
Orchestration Services
- Phoenix Transaction Orchestrator - On-chain/off-chain workflow orchestration
- Phoenix Messaging Orchestrator - Multi-provider messaging with failover
- Phoenix Voice Orchestrator - TTS/STT with caching and routing
Platform Services
- Phoenix Event Bus - Durable events, replay, versioning
- Phoenix Audit Service - Immutable audit logs and WORM archive
- Phoenix Observability Stack - Distributed tracing, structured logs, SLOs
Guiding Principles
-
No provider is System of Record (SoR)
- Provider outages must not affect balances, identity, wallets, audit, or message delivery.
-
Own the primitives; outsource the commodity
- Ledger, identity, wallet registry, orchestration, audit = internal.
- Provider integrations are adapters behind stable internal contracts.
-
API-first + event-driven
- Every domain emits events; all state transitions are auditable.
-
Security by design
- Keys, PII, and money movement are the highest-risk domains; isolate, minimize, and monitor.
-
Provider optionality
- Integrations are adapters behind stable internal contracts.
Architecture
All services follow a consistent architecture pattern:
- Internal Core: Owned primitives that are always internal
- Provider Adapters: Optional integrations via adapters
- Event Bus: All state changes emit events
- Audit Trail: Immutable logging of all operations
- Observability: Distributed tracing and SLO monitoring
Getting Started
- Browse services in the Sankofa Marketplace
- Review service documentation for integration details
- Subscribe to services via the marketplace
- Use API keys for authentication
- Monitor usage and costs via the billing dashboard
Support
- Documentation: docs.sankofa.nexus
- Support: support.sankofa.nexus
- Community Forum: forum.sankofa.nexus