Estado actual real
Section titled “Estado actual real”Control plane
Section titled “Control plane”- Hostname:
ubuntu-ialab - IP principal:
192.168.1.30 - Rol:
primary-control-plane - Hermes Enterprise status endpoint:
192.168.1.30:8095(GET /hermes/status) - Servicios: ailab-gateway (:8008), ailab-router (:8083), ailab-live-api (:8084), ailab-hermes-status (:8095)
Observability
Section titled “Observability”- Prometheus:
192.168.1.40:9090— source of truth - Grafana:
192.168.1.40:3000— visualization layer (15 dashboards, TIER 1 + TIER 2) - Alert rules: 19 reglas activas, todas health=ok
- Métricas: 100+
ailab_*covering profiles, latency, tools, memory, quality, streaming, GPU, SLO, governance, sensor fusion - Loki: log layer
- Los sensores del runtime se alimentan de Prometheus y del API de LM Studio.
Inference backend activo
Section titled “Inference backend activo”- GPU:
RX9070 - Host:
192.168.1.50 - Estado:
online - Fuente operativa:
Prometheus GPU exporter + LM Studio API
Inference backend inventariado
Section titled “Inference backend inventariado”- GPU:
RX7900XT - Host:
192.168.1.60 - Estado:
expected_offline / inventory - No activo
- No routable
- No debe generar métricas inventadas
Storage
Section titled “Storage”- Runtime vivo:
/opt/ai-lab - Runtime data:
/opt/ai-lab-data - Modelos:
/mnt/ai-models - Archives históricos:
/mnt/opencode/ai-lab-archives
Enterprise layer (Hermes Enterprise Core)
Section titled “Enterprise layer (Hermes Enterprise Core)”Hermes Enterprise Core is deployed as a read-only declarative layer exposing AI-LAB’s enterprise semantics via GET /hermes/status on port :8095. All components are in validation-only mode — no active enforcement, no hooks executing.
| Component | Status | Description |
|---|---|---|
| SOUL | ✅ Implemented | Ontological seed: truth_model, boundaries, protocols, domains, identity, schema |
| Capability Registry | ✅ Implemented | Runtime capability catalog with cross-validation (24 capabilities) |
| Operator Registry | ✅ Implemented | 12 deep validations per operator (IDs, capabilities, MCP, protocols, execution_mode, domains, forbidden_actions) |
| Hook Registry | ✅ Implemented | Lifecycle hooks skeleton (all enabled: false, mode: declarative_only) |
| MCP Registry | ✅ Implemented | Declared MCP servers (prometheus, marketplace-mcp as planned, no active tools) |
| Dynamic Governance | ✅ Implemented | 4 modes (NORMAL/ELEVATED/DEGRADED/LOCKDOWN), 6 trigger signals, anti-flapping 30s, capability-governance matrix |
| Status Endpoint | ✅ Implemented | GET /hermes/status → :8095, 14 response blocks, always-on 200 |
185 tests PASS. Checkpoint: CP-HERMES-ENTERPRISE-CORE-01.
Knowledge Base (AnythingLLM Enterprise)
Section titled “Knowledge Base (AnythingLLM Enterprise)”AnythingLLM Enterprise provides the RAG knowledge layer for AI-LAB. All workspaces are configured with LM Studio backend (192.168.1.50:1234) and text-embedding-multilingual-e5-small embedder.
| Resource | Value |
|---|---|
| Host | 192.168.1.50:3001 |
| Active workspaces | 7 |
| Total vectors | 1304 |
| Embedder | text-embedding-multilingual-e5-small (Q8_0) |
| Document corpus | Architecture (84 canonical), Evidence reports (53), Marketplace (7), Observability+IDS (2), Runbooks+Stack (8), MCP+A2A (19) |
| RAG validation | ✅ E2E 100% |
| Baseline | Frozen at CP-ANYTHINGLLM-ENTERPRISE-04-COMPLETE |
Qué cambió con 30I
Section titled “Qué cambió con 30I”Antes:
LLM + routing + promptsDespués:
Runtime observacional cognitivo→ Prometheus-backed evidence→ Sensor fusion→ Evidence-bound reporting→ GPU operational summaries→ source_of_truth / freshness / confidenceCheckpoints relevantes
Section titled “Checkpoints relevantes”Bloques 28–30 — Agentes, streaming, SLO enforcement, sensor fusion
Section titled “Bloques 28–30 — Agentes, streaming, SLO enforcement, sensor fusion”CP-28.1-PLANNER-RUNTIME-SKELETON-STABLECP-28.2-READONLY-EXECUTOR-STABLECP-28.2-B-READONLY-BURNIN-STABLECP-28.3-SANDBOX-WRITE-STABLECP-28.3-B-SANDBOX-WRITE-BURNIN-STABLECP-29.2-B-STREAMING-BURNIN-STABLECP-29.3-THREE-MODEL-RUNTIME-STABLECP-29.4-SLO-ENFORCEMENT-STABLECP-29.4.4-ERROR-TAXONOMY-STABLECP-29.4.4-C-SLO-HEALTH-ENDPOINT-STABLECP-29.4.4-D-PARALLEL-TOOLCALL-HARDENING-STABLECP-30A-RUNTIME-STATE-FOUNDATION-STABLECP-30B-MODEL-STATE-AWARE-STABLECP-30E-GOVERNANCE-VISIBILITY-STABLECP-30F-ROUTE-SEMANTICS-STABLECP-30G-OPERATIONAL-REPORTING-STABLECP-30H-RUNTIME-EVIDENCE-ENFORCEMENT-STABLECP-30H.1-UNIVERSAL-EVIDENCE-GUARD-STABLECP-30H.2-RUNTIME-CONTEXT-INJECTION-STABLECP-30I-RUNTIME-SENSOR-FUSION-STABLECP-30I-B-SENSOR-FUSION-HARDENED-STABLECP-30I-C-SENSOR-SUMMARY-EXPOSURE-STABLECP-30I-D-SENSOR-SEMANTICS-NORMALIZED-STABLECP-30I-E-OPERATIONAL-RESPONSE-FORMATTING-STABLECP-30I-F-RUNTIME-COGNITIVE-COMPRESSION-STABLECP-30I-F0-RUNTIME-MODEL-ROUTING-CLEANUP-STABLECP-30I-G-RUNTIME-GROUNDING-STABLEBloques 31–36 — Madurez semántica, cognición, precisión
Section titled “Bloques 31–36 — Madurez semántica, cognición, precisión”CP-OBS-31A-OBSERVABILITY-SOURCE-OF-TRUTH-STABLECP-OBS-31A.1-PROMETHEUS-AUTHORITY-AUDIT-STABLECP-OBS-31A.2-GRAFANA-DRIFT-AUDIT-STABLECP-OBS-31A.3-RUNTIME-OBSERVABILITY-ALIGNMENT-STABLECP-OBS-31A.4-OBSERVABILITY-REMEDIATION-PLAN-STABLECP-OBS-31A.5-EXECUTOR-STABLECP-31B-RUNTIME-SEMANTIC-MATURITY-STABLECP-31B-HF1-OPENCODE-CONTEXT-ALIGNMENT-STABLECP-31C-OPERATIONAL-REPORTING-DISCIPLINE-STABLECP-35C-LIVE-AUTHORITY-BACKED-COGNITION-STABLECP-35D-OPERATIONAL-FAST-PATH-STABLECP-35D-HF1-FASTPATH-ROUTING-PRIORITY-STABLECP-36A-OPERATIONAL-INCIDENT-INTELLIGENCE-STABLECP-DEV-36X-CODEBASE-MEMORY-INTEGRATION-STABLECP-DOC-36X-GITNEXUS-STRUCTURAL-COGNITION-STABLECP-DOC-36X-SPANISH-LOCALIZATION-STABLECP-36B-RUNTIME-PRECISION-MODE-STABLEBloques 37–40 — Estabilidad, release hardening, SLO drift watch
Section titled “Bloques 37–40 — Estabilidad, release hardening, SLO drift watch”CP-38A-RUNTIME-DEEP-AUDIT-01-STABLECP-38B-GATEWAY-SHUTDOWN-GRACEFUL-01-STABLECP-38C-GITNEXUS-NAPI-ERROR-TRIAGE-01-STABLECP-38D-RUNTIME-STABILITY-SNAPSHOT-01-STABLECP-39A-OPENCODE-GATEWAY-CONTRACT-HARDENING-01-STABLECP-39B-RUNTIME-OBSERVABILITY-ALERTS-01-STABLECP-39C-COGNITIVE-HEALTH-FOLLOWUP-01-STABLECP-39E-RUNTIME-STABILIZATION-RELEASE-CLOSE-01-STABLECP-40A-POST-RELEASE-SLO-DRIFT-WATCH-01-STABLEGobernanza, routing, multi-GPU readiness
Section titled “Gobernanza, routing, multi-GPU readiness”CP-GITNEXUS-FIRST-ACTIVATION-01CP-SLO-ENFORCEMENT-01CP-VALIDATION-AUTHORITY-01CP-AUTONOMOUS-OBSERVABILITY-TRIAGE-01CP-OPERATOR-INTENT-REASONING-01CP-MULTIGPU-READINESS-01CP-DYNAMIC-NODE-REGISTRY-01CP-AI-LAB-MULTI-NODE-ROUTING-01CP-INTELLIGENT-FALLBACK-ENGINE-01CP-CAPABILITY-SCHEDULER-01CP-49A-POOL-ADMIN-API-READONLY-01CP-DOC-AUTOMATION-STABLECP-DOCS-ASTRO-ARCHITECTURE-UPDATE-01-STABLECP-DOCS-AILAB-MCP-INFRASTRUCTURE-UPDATE-01-STABLECP-MCP-OPENCODE-WINDOWS-CONNECTION-01-STABLECP-MCP-SEMANTIC-GATEWAY-01-STABLEHermes Enterprise
Section titled “Hermes Enterprise”CP-E01A-SOUL-ENTERPRISE-SKELETON-STABLECP-E02A-CAPABILITY-REGISTRY-SKELETON-STABLECP-E02B-CAPABILITY-REGISTRY-VALIDATOR-STABLECP-E02C-OPERATOR-REGISTRY-VALIDATOR-STABLECP-E03A-OPERATOR-REGISTRY-SKELETON-STABLECP-E04A-HOOK-REGISTRY-SKELETON-STABLECP-E05-MCP-REGISTRY-SKELETON-STABLECP-E06-DYNAMIC-GOVERNANCE-STABLECP-E07-ENTERPRISE-RUNTIME-STATUS-ENDPOINT-STABLECP-HERMES-ENTERPRISE-CORE-01CP-HERMES-ENTERPRISE-FOUNDATION-01CP-HERMES-OPERABILITY-TUNING-01CP-HERMES-DOCS-ASTRO-ENTERPRISE-01Knowledge Base (AnythingLLM)
Section titled “Knowledge Base (AnythingLLM)”CP-ANYTHINGLLM-ENTERPRISE-04-COMPLETELímite explícito
Section titled “Límite explícito”Este estado es pre-Multi-GPU. RX7900XT sigue siendo inventario. No hay scheduler Multi-GPU documentado como implementado. Aunque las precondiciones semánticas (30H–31B) están cerradas desde CP-31B, el nodo RX7900XT permanece apagado y no hay plan activo de reactivación.