Files
blackroad-operating-system/infra/analysis/prism-console.md
Claude abdbc764e6 Establish BlackRoad OS infrastructure control plane
Add comprehensive infrastructure management system to centralize all service
definitions, deployment configurations, and operational tooling.

## New Infrastructure Components

### 1. Service Manifest (infra/blackroad-manifest.yml)
- Complete catalog of all active and planned services
- Deployment configuration for each service
- Environment variable definitions
- Domain mappings and routing
- Database and cache dependencies
- Health check endpoints
- CI/CD integration specifications

### 2. Operations CLI (scripts/br_ops.py)
- Command-line tool for managing all BlackRoad services
- Commands: list, env, repo, open, status, health
- Reads from service manifest for unified operations
- Colored terminal output for better readability

### 3. Service Analysis Documents (infra/analysis/)
- Detailed technical analysis for each service
- Active services:
  - blackroad-backend.md (FastAPI backend)
  - postgres.md (PostgreSQL database)
  - redis.md (Redis cache)
  - docs-site.md (MkDocs documentation)
- Planned services:
  - blackroad-api.md (API gateway - Phase 2)
  - prism-console.md (Admin console - Phase 2)

### 4. Infrastructure Templates (infra/templates/)
- railway.toml.template - Railway deployment config
- railway.json.template - Alternative Railway config
- Dockerfile.fastapi.template - Multi-stage FastAPI Dockerfile
- github-workflow-railway-deploy.yml.template - CI/CD workflow
- .env.example.template - Comprehensive env var template

### 5. Documentation (infra/README.md)
- Complete guide to infrastructure control plane
- Usage instructions for ops CLI
- Service manifest documentation
- Deployment procedures
- Troubleshooting guide
- Phase 2 migration plan

## Architecture

This establishes BlackRoad-Operating-System as the canonical control plane
for all BlackRoad services, both current and planned:

**Phase 1 (Active)**:
- blackroad-backend (FastAPI + static UI)
- postgres (Railway managed)
- redis (Railway managed)
- docs-site (GitHub Pages)

**Phase 2 (Planned)**:
- blackroad-api (API gateway)
- blackroad-prism-console (Admin UI)
- blackroad-agents (Orchestration)
- blackroad-web (Marketing site)

**Phase 3 (Future)**:
- lucidia (AI orchestration)
- Additional microservices

## Usage

# List all services
python scripts/br_ops.py list

# Show environment variables
python scripts/br_ops.py env blackroad-backend

# Show repository info
python scripts/br_ops.py repo blackroad-backend

# Show service URL
python scripts/br_ops.py open blackroad-backend prod

# Show overall status
python scripts/br_ops.py status

# Show health checks
python scripts/br_ops.py health blackroad-backend

## Benefits

1. **Single Source of Truth**: All service configuration in one manifest
2. **Unified Operations**: One CLI for all services
3. **Documentation**: Comprehensive per-service analysis
4. **Templates**: Reusable infrastructure patterns
5. **Migration Ready**: Clear path to Phase 2 microservices

## References

- MASTER_ORCHESTRATION_PLAN.md - 7-layer architecture
- ORG_STRUCTURE.md - Repository strategy
- PRODUCTION_STACK_AUDIT_2025-11-18.md - Current state

Implemented by: Atlas (AI Infrastructure Orchestrator)
Date: 2025-11-19
2025-11-19 21:04:14 +00:00

88 lines
2.0 KiB
Markdown

# Service Analysis: prism-console (PLANNED)
**Status**: 📋 PLANNED (Phase 2)
**Target Date**: Q1 2026
**Service Type**: Admin Console UI
**Repository**: `blackboxprogramming/blackroad-prism-console` (to be created)
---
## Overview
Standalone admin console for job queue monitoring, system observability, and operator dashboards. Currently exists as static files in `prism-console/` directory.
---
## Current State
### Location
- **Source**: `prism-console/` in monolith
- **Status**: Built but not integrated
- **Access**: Should be served at `/prism` by backend
### Features (Implemented)
- Job queue dashboard
- System metrics display
- Event log viewer
- Multi-tab navigation
- Dark theme UI
---
## Phase 2 Plan
### Extraction Strategy
1. **Immediate (Phase 1.5)**:
- Integrate into backend: `app.mount("/prism", StaticFiles(...))`
- Deploy and test
2. **Phase 2**:
- Extract to separate repo
- Build as React/Next.js app (or keep Vanilla JS)
- Deploy to Railway/Vercel
### Technology Options
**Option A: Keep Vanilla JS**
- Pros: Zero dependencies, fast load
- Cons: Limited scalability for complex features
**Option B: React 18+**
- Pros: Component reusability, rich ecosystem
- Cons: Build complexity, larger bundle
**Option C: Next.js 14+**
- Pros: SSR, routing, optimizations
- Cons: More infrastructure needed
---
## Configuration
### Environment Variables
```bash
REACT_APP_API_URL=https://blackroad.systems/api
REACT_APP_CORE_API_URL=https://api.blackroad.systems
REACT_APP_AGENTS_API_URL=https://agents.blackroad.systems
```
### Domains
- **Production**: `prism.blackroad.systems`
- **Staging**: `staging.prism.blackroad.systems`
---
## API Integration
### Required Endpoints
- `GET /api/prism/jobs` - Job queue
- `GET /api/prism/events` - Event stream
- `GET /api/system/version` - Version info
- `GET /api/health/summary` - Health status
- `WebSocket /api/prism/stream` - Real-time updates
---
*Analysis Date: 2025-11-19*
*Status: Planning Phase*