Operating principle
2026-05-05
4 min read
Why the technical record exists
A public operating layer for recording what Virtus Nemeton actually built, changed, confirmed, and learned.
Public technical record
What changed, what was confirmed, and what still needs follow-through.
This record is where Virtus Nemeton publishes the grounded layer of platform work: architecture decisions, operational lessons, deployment truth, and the exact distinction between what is live and what is still blocked.
Reading posture
Entries here should read as operating notes, not launch copy.
When a system is live, we say it is live. When it is blocked, we say what is blocking it.
Main site: https://virtusnemeton.co.uk
Read entry
Architecture direction
2026-05-05
6 min read
Hybrid boundary: Supabase, Neo4j, and .nkt
The graph layer is infrastructure, while the moat moves upward into governed ingestion, approvals, replay, and decision outputs.
Reliability lesson
2026-05-05
5 min read
What a model-promotion incident taught us
A retrain flow can say success while still failing the only thing that matters: changing the live active model safely and visibly.