proxmox/docs/02-architecture/EXPECTED_WEB_CONTENT.md

# Web Properties — Ground Truth & Validation

**Last Updated:** 2026-01-31  
**Document Version:** 1.0  
**Status:** Active Documentation

---

_Last reviewed: authoritative alignment checkpoint_

This document reconciles **expected intent**, **current deployment state**, and **functional role** for each public-facing or semi-public web property.

---

## 1. phoenix.sankofa.nexus
**Service Name:** Phoenix API / Cloud Platform Portal  
**Role:** Cloud Service Provider (CSP) for Sankofa  
**Comparable To:** AWS Console, Azure Portal, GCP Console

### Intended Function
- Sovereign-grade cloud infrastructure control plane
- Multi-tenant resource provisioning
- Service orchestration and lifecycle management

### Expected Capabilities
- GraphQL API endpoint: `/graphql`
- WebSocket endpoint: `/graphql-ws`
- Health check endpoint: `/health`
- Cloud resource management (compute, network, storage)
- Tenant, IAM, and billing controls
- Internal service catalog / marketplace

### Current Deployment
- **Status:** ✅ Deployed and active
- **VMID:** 7800
- **Address:** 192.168.11.50:4000
- **Access Model:** API-first (not a marketing site)

### Notes
- This is **not** a public brochure site  
- UI is assumed to be console-style or API-driven  
- Sovereign / operator-facing only

---

## 2. sankofa.nexus
**Service Name:** Sankofa Portal  
**Role:** Corporate & Product Website  
**Comparable To:** Microsoft.com, Google.com, Amazon.com

### Intended Function
- Public-facing corporate presence
- Brand narrative and philosophy
- Product overview and entry point to Phoenix

### Expected Content
- Company overview and mission
- Sankofa brand philosophy:
  **"Remember → Retrieve → Restore → Rise"**
- Phoenix product introduction
- Navigation to services
- Contact and inquiry paths

### Current Deployment
- **Status:** ✅ Deployed
- **VMID:** 7801
- **Address:** 192.168.11.51:3000
- **Technology:** Next.js

### Observed Behavior
- Portal currently presents a **login-gated interface**
- Authentication handled via **Keycloak**
- Dashboard requires credentials

### Alignment Note
- ⚠️ **Decision point:**
  - Either split into:
    - `www.sankofa.nexus` (public marketing)
    - `portal.sankofa.nexus` (authenticated)
  - Or intentionally maintain a gated-first model

---

## 3. explorer.d-bis.org
**Service Name:** SolaceScanScout  
**Role:** Block Explorer for ChainID 138  
**Technology:** Blockscout-based  
**Comparable To:** Etherscan, PolygonScan, BscScan

### Intended Function
- Public transparency layer for ChainID 138
- Settlement and transaction inspection

### Expected Capabilities
- Latest blocks viewer
- Transaction browser
- Address explorer (balances, history)
- Token explorer (ERC-20 or equivalents)
- Network metrics and statistics
- Search (block / tx / address)
- ChainID 138 network identification

### Current Deployment
- **Status:** ✅ Active, separate service
- **VMID:** 5000
- **Address:** 192.168.11.140
- **Isolation:** Independent from Phoenix & Sankofa Portal

### Notes
- Correctly positioned as **public infrastructure**
- No coupling to portal auth systems

---

## 4. blockscout.defi-oracle.io
**Service Name:** Blockscout Explorer (Generic)  
**Role:** Independent / Reference Blockscout Instance

### Intended Function
- General-purpose blockchain explorer
- Testing, comparison, or alternate network usage

### Capabilities
- Standard Blockscout UI
- Smart contract verification
- API access for blockchain data

### Current Status
- Separate and unrelated to ChainID 138 branding
- **Not** the canonical DBIS explorer

---

## Canonical Alignment Summary

| Domain | Purpose | Public | Auth Required | Canonical |
|--------|---------|--------|---------------|-----------|
| sankofa.nexus | Corporate / Brand | Yes | Partial | ✅ |
| phoenix.sankofa.nexus | Cloud Control Plane | No | Yes | ✅ |
| explorer.d-bis.org | ChainID 138 Explorer | Yes | No | ✅ |
| blockscout.defi-oracle.io | Generic Explorer | Yes | No | ❌ |

---

## Confirmed Architectural Intent
- **Phoenix** = infrastructure + API + control plane  
- **Sankofa** = sovereign-facing brand & access layer  
- **DBIS Explorer** = public transparency + settlement inspection  
- **No accidental overlap** between marketing, control, and transparency layers

---

## Open Decisions (Explicitly Unresolved)

**Critical:** These decisions remain **explicitly unresolved**. Do not collapse them prematurely.

### 1. Public vs Gated Split for `sankofa.nexus`
**Status:** Open decision point

**Options:**
- Option A: Split into public marketing site and authenticated portal
- Option B: Maintain gated-first model with selective public content
- Option C: Evolve to unified model with public sections

**Authority:** Governance decision, not implementation drift

**Note:** Auth is a policy boundary, not a permanent architectural constraint.

---

### 2. Phoenix UI Exposure
**Status:** Open decision point

**Question:** Whether Phoenix ever exposes a human UI beyond operators

**Current State:** API-first, operator-facing

**Flexibility:**
- API-first does not preclude future UI
- Console-based access patterns are possible
- Delegated interfaces are not precluded

**Note:** Intent document states: "This does not preclude future public or delegated interfaces."

---

### 3. Branding Linkage
**Status:** Open decision point

**Question:** Branding linkage between DBIS Core products and explorer UI

**Options:**
- Maintain independent branding
- Align with DBIS Core products
- Federate with other explorers

**Note:** Explorer independence is intentional, not permanent.

---

### 4. Future Evolution Pathways (Non-Binding)

These are **possible futures**, not commitments:

- Public marketing split (`www` vs `portal`)
- Delegated Phoenix UI development
- Explorer rebrand or federation
- Additional service surfaces

**Why Documented:**
- Signals foresight without commitment
- Prevents future teams from assuming "this was never considered"
- Preserves optionality for governance decisions

---

## Service Relationship Diagram

```
Internet
   ↓
NPMplus (Reverse Proxy + SSL)
   ↓
   ├─→ sankofa.nexus → Sankofa Portal
   │                     └─→ Corporate Brand / Product Website
   │                     └─→ ⚠️ Currently: Login-gated
   │
   ├─→ phoenix.sankofa.nexus → Phoenix API
   │                            └─→ Cloud Control Plane (API-first)
   │                            └─→ Operator-facing only
   │
   ├─→ explorer.d-bis.org → SolaceScanScout
   │                         └─→ Public Block Explorer (ChainID 138)
   │                         └─→ No auth required
   │
   └─→ blockscout.defi-oracle.io → Generic Blockscout
                                    └─→ Reference instance (not canonical)
   
Backend Services:
   ├─→ Keycloak (Authentication) - VMID 7802
   └─→ PostgreSQL (Database) - VMID 7803
```

---

## Deployment Status

### Active Services

| Service | Domain | VMID | IP | Port | Status | Public Access |
|---------|--------|------|-----|------|--------|---------------|
| **Phoenix API** | phoenix.sankofa.nexus | 7800 | 192.168.11.50 | 4000 | ✅ Active | Authenticated |
| **Sankofa Portal** | sankofa.nexus | 7801 | 192.168.11.51 | 3000 | ✅ Active | Partially Public |
| **SolaceScanScout** | explorer.d-bis.org | 5000 | 192.168.11.140 | 80/4000 | ✅ Active | Public |
| **Blockscout** | blockscout.defi-oracle.io | ⚠️ TBD | ⚠️ TBD | ⚠️ TBD | ⚠️ Separate | Public |

---

## Brand/Product Relationship Context

**Sankofa** = Company/Brand (like Microsoft, Google, Amazon)  
**Phoenix** = Cloud Platform/Product (like Azure, GCP, AWS)  
**Sankofa Phoenix** = Complete Product (like Microsoft Azure, Google Cloud Platform, Amazon Web Services)

- **sankofa.nexus** = Company website (like Microsoft.com)
- **phoenix.sankofa.nexus** = Cloud platform portal (like Azure Portal)
- **explorer.d-bis.org** = Blockchain explorer (like Etherscan)
- **blockscout.defi-oracle.io** = Generic explorer instance

---

**Last Updated:** 2026-01-20  
**Review Status:** Authoritative alignment checkpoint