a11oy · WASI-RIKUQ — the House-Watcher · Doctrine v13 §2.3
homechaskiwallpawasi-rikuq

WASI-RIKUQ — the House-Watcher

Quechua wasi (house) + rikuq (one who watches, from rikuy = to see/watch over). The founder's dashboard of everything: it watches every flagship, owns the incident log + runbooks, runs 2-person-gated chaos, and computes one health number. Factor: Wasi(a)=(∏ₒ hₒ)·𝟙[error-budget intact] ∈ [0,1] — advisory only; HUKLLA stays the sole halt-authority.

A watchman atop a tower, eyes on every organ. Node color = health. Drag to orbit.

Health of the empire — single number

GET /api/a11oy/wasi-rikuq/health-of-the-empire
—
—
— one number in [0,1] expressing overall house health —

Single-pane dashboard

GET /api/a11oy/wasi-rikuq/dashboard
— uptime · latency · error rate · Khipu DAG depth · Yuyay distribution · HUKLLA firings · wire pulse —

Incidents + auto-loaded runbook

GET /incidents · GET /runbook?incident_type=…
— live + 30d incident log; runbook auto-loads by incident type —

Chaos experiment — 2-person Yuyay gate

POST /api/a11oy/wasi-rikuq/chaos
— chaos is gated: needs 2 DISTINCT approvers, each with 13-axis yuyay_score ≥ 0.90 —
Honest labels (Doctrine v13 §5 + HARD RULES): WASI-RIKUQ is advisory only — it informs HUKLLA but never usurps it (INV-1 preserved). It wires into Wires D–H from the resilience mesh. Chaos requires a 2-person Yuyay gate. Every action emits a Khipu receipt (SHA3-256 hash-chain; signature DSSE PLACEHOLDER). Durable metrics DB / Prometheus / Grafana is the P1 backend; this surface is the P0 single-pane face.