The operational record of building a governance-first AI platform.
Architecture decisions, failure modes, and operational lessons from building NiraNexus-OS. Updated as we ship.
A circuit breaker is not a budget control. It is a quality signal. Three yield points in the debate engine catch broken processes before they consume tokens and produce nothing. The code is the policy.
Read →The split-based fenced code block approach was added as a Windows tool corruption workaround. It became the rendering bug that broke the Log for two sessions. The fix wasn't changing the code — it was changing the order.
Read →Promise.race timeouts, FK cascade failures, and the Supabase .catch() that silently dropped 57 of 63 deliberation records over six weeks.
Read →Why NiraNexus-OS exists, what adversarial deliberation actually means, and what this operational record will chronicle.
Read →