feat: Add domain architecture and extract core services from Prism Console

## Domain Architecture
- Complete domain-to-service mapping for 16 verified domains
- Subdomain architecture for blackroad.systems and blackroad.io
- GitHub organization mapping (BlackRoad-OS repos)
- Railway service-to-domain configuration
- DNS configuration templates for Cloudflare

## Extracted Services

### AIops Service (services/aiops/)
- Canary analysis for deployment validation
- Config drift detection
- Event correlation engine
- Auto-remediation with runbook mapping
- SLO budget management

### Analytics Service (services/analytics/)
- Rule-based anomaly detection with safe expression evaluation
- Cohort analysis with multi-metric aggregation
- Decision engine with credit budget constraints
- Narrative report generation

### Codex Governance (services/codex/)
- 82+ governance principles (entries)
- Codex Pantheon with 48+ agent archetypes
- Manifesto defining ethical framework

## Integration Points
- AIops → infra.blackroad.systems (blackroad-os-infra)
- Analytics → core.blackroad.systems (blackroad-os-core)
- Codex → operator.blackroad.systems (blackroad-os-operator)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

services/codex/entries/017-erasure-coded-resilience.md

@@ -0,0 +1,27 @@
+# Codex 17 — Erasure-Coded Resilience — Lose Shards, Keep Truth
+
+**Fingerprint:** `23064887b1469b19fa562e8afdee5e9046bedf99aa9cd7142c35e38f91e6fef2`
+
+## Aim
+Survive faults, sabotage, or regional failures without losing data integrity.
+
+## Core
+- Encode \(k\) source blocks into \(n\) coded blocks (Reed–Solomon) so any \(k\) suffice to recover the original data.
+- Tolerate \(f = n - k\) faults with rate \(k / n\) tailored to the threat model.
+- Use regenerating codes (MSR/MBR) to optimize repair bandwidth when restoring lost shards.
+
+## Runbook
+1. Select \((n, k)\) parameters aligned with durability and latency requirements, then geo-distribute shards.
+2. Rotate shards periodically and audit decode success under simulated failure scenarios.
+3. Pair storage with zero-knowledge audits proving shards belong to the same file lineage.
+
+## Telemetry
+- Decode success probability under sampled fault sets.
+- Time to repair missing shards and restore redundancy.
+- Entropy measurements of stored shards to detect drift or tampering.
+
+## Failsafes
+- If shard loss exceeds \(f\), trigger emergency replication and pause writes until redundancy is restored.
+- Investigate anomalous entropy or audit failures before resuming regular operations.
+
+**Tagline:** Fragment boldly, recover surely.