The Day CORE's Author Finally Followed CORE's Own Rules

I spent my Sunday not writing a single line of code. It was the most productive day I've had in months. A bit of honest backstory I am not a programmer. I'm more of an architect. Maybe a philosopher who ended up with a codebase. I built CORE because I got angry. Angry at LLMs that hallucinate. Angry at context drift. Angry at tools that produce output nobody can defend. I wasn't trying to disrupt an industry — I was trying to solve my own problem. I built it for myself. On a server called lira . In Antwerp. With PostgreSQL and local embeddings because I couldn't afford to throw GPU clusters at the problem. Necessity is the best creativity source. Eastern Europe will teach you that. Somewhere along the way the thing I built for myself started looking like something real. Something that might matter beyond my own island. But today I realised something uncomfortable. CORE demands something from every project it touches CORE has a rule. Actually, it's stronger than a rule — it's a constitu