Skip to content
← Log
NiraNexus

NiraNexus Log

The operational record of building a governance-first AI platform.

Architecture

7 entries filed under Architecture.

Log #9·August 18, 2026·7 min read

The Fallback Lie: The Model Swap You Never See

The response card said GPT-5.6 Terra. The Execution Metrics said FALLBACK_TRIGGERED. GPT-4o wrote that analysis. The swap was silent, invisible, and correct by design. This is the fallback lie. The name on the badge is the model you asked for. The model that actually ran is buried in a collapsed data panel most users never expand.

Read →
Log #8·August 17, 2026·7 min read

The Green Checkmark Lie: When AI Self-Verification Fails

Microsoft ran 18 controlled experiments. Coding agents with their own test suite scored 221 out of 222 while the reusable library they were hired to build was completely dead. The Model Council separates making from checking. That is the difference between verification and confirmation.

Read →
Log #7·August 14, 2026·9 min read

The Roster Problem: How the Model Council Survives Production

Every architecture article about the Model Council assumes the roster exists. This one explains where the models come from. Four cognitive personas, four providers, a two-tier fallback chain, and a daily cron audit that checks sixteen endpoints before a debate can fail.

Read →
Log #6·August 13, 2026·11 min read

Three Modes, One Question: Does the Council Work?

Same question. Same four models. Three execution modes. The verdict moved from 54% to 73% as the reasoning topology deepened. Extended and Graph consume the same compute ceiling but spend it on fundamentally different things.

Read →
Log #5·July 21, 2026·9 min read

Three Rounds, One Verdict

The Model Council does not vote. It cross-examines. Tracing a real deliberation through three rounds of structured conflict: code blocks, claim lifecycle, and the dissent protocol that preserves disagreement as evidence.

Read →
Architecture : NiraNexus Log