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/013-verifiable-compute.md

@@ -0,0 +1,27 @@
+# Codex 13 — Verifiable Compute — Trust the Result, Not the Box
+
+**Fingerprint:** `23064887b1469b19fa562e8afdee5e9046bedf99aa9cd7142c35e38f91e6fef2`
+
+## Aim
+Prove remote computation was executed correctly without re-running it locally.
+
+## Core
+- Model the workload as a succinct non-interactive argument of knowledge (SNARK) relation \(R(x, w)\) with constraint system \(C(x, w) = 1\).
+- Enforce soundness so that \(\Pr[\text{V accepts} \land (x, w) \notin R] \leq \text{negl}(\lambda)\).
+- Achieve verification time \(T_{\text{verify}} = \tilde{O}(|x|)\), independent of prover runtime.
+
+## Runbook
+1. Compile the workload into a circuit or other arithmetization and fix the public input \(x\).
+2. Have the prover return the output \(y\) alongside a proof \(\pi\); the verifier checks \(\pi\).
+3. Archive \((x, y, \pi, \mathsf{vk})\) into the Civilizational ECC and pin the digest on-chain or in an immutable log.
+
+## Telemetry
+- Proof size and amortized cost per proof.
+- Verification time and failure rate.
+- Prover runtime and resource consumption.
+
+## Failsafes
+- If the prover times out, fall back to redundant execution across diverse hardware targets.
+- If proof verification fails, quarantine the output and trigger incident response.
+
+**Tagline:** Believe the math, not the metal.