70 lines
3.0 KiB
Markdown
70 lines
3.0 KiB
Markdown
|
# 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
|
||
|
|
|
||
|
|
1. **[Phoenix Ledger Service](./ledger-service.md)** - Double-entry ledger with virtual accounts
|
||
|
|
2. **[Phoenix Identity Service](./identity-service.md)** - Identity, auth, and policy management
|
||
|
|
3. **[Phoenix Wallet Registry](./wallet-registry.md)** - Wallet mapping and signing policy
|
||
|
|
|
||
|
|
### Orchestration Services
|
||
|
|
|
||
|
|
4. **[Phoenix Transaction Orchestrator](./tx-orchestrator.md)** - On-chain/off-chain workflow orchestration
|
||
|
|
5. **[Phoenix Messaging Orchestrator](./messaging-orchestrator.md)** - Multi-provider messaging with failover
|
||
|
|
6. **[Phoenix Voice Orchestrator](./voice-orchestrator.md)** - TTS/STT with caching and routing
|
||
|
|
|
||
|
|
### Platform Services
|
||
|
|
|
||
|
|
7. **[Phoenix Event Bus](./event-bus.md)** - Durable events, replay, versioning
|
||
|
|
8. **[Phoenix Audit Service](./audit-service.md)** - Immutable audit logs and WORM archive
|
||
|
|
9. **[Phoenix Observability Stack](./observability.md)** - Distributed tracing, structured logs, SLOs
|
||
|
|
|
||
|
|
## Guiding Principles
|
||
|
|
|
||
|
|
1. **No provider is System of Record (SoR)**
|
||
|
|
- Provider outages must not affect balances, identity, wallets, audit, or message delivery.
|
||
|
|
|
||
|
|
2. **Own the primitives; outsource the commodity**
|
||
|
|
- Ledger, identity, wallet registry, orchestration, audit = internal.
|
||
|
|
- Provider integrations are adapters behind stable internal contracts.
|
||
|
|
|
||
|
|
3. **API-first + event-driven**
|
||
|
|
- Every domain emits events; all state transitions are auditable.
|
||
|
|
|
||
|
|
4. **Security by design**
|
||
|
|
- Keys, PII, and money movement are the highest-risk domains; isolate, minimize, and monitor.
|
||
|
|
|
||
|
|
5. **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
|
||
|
|
|
||
|
|
1. Browse services in the [Sankofa Marketplace](https://portal.sankofa.nexus/marketplace)
|
||
|
|
2. Review service documentation for integration details
|
||
|
|
3. Subscribe to services via the marketplace
|
||
|
|
4. Use API keys for authentication
|
||
|
|
5. Monitor usage and costs via the billing dashboard
|
||
|
|
|
||
|
|
## Support
|
||
|
|
|
||
|
|
- **Documentation**: [docs.sankofa.nexus](https://docs.sankofa.nexus)
|
||
|
|
- **Support**: [support.sankofa.nexus](https://support.sankofa.nexus)
|
||
|
|
- **Community Forum**: [forum.sankofa.nexus](https://forum.sankofa.nexus)
|