My name is Ernst Renner. I immigrated to Canada from Austria, and my journey has been defined by a lifetime spent at the intersection of faith, music, education, and technology. My early years as a music teacher and musician instilled a love for creation; my subsequent exploration of technical systems revealed the mechanics through which that creation is preserved. Now, retired on the West Coast, I dedicate my time to the convergence of Local AI and knowledge sovereignty.
Alongside formal training in Web Design and CAD Technology, I spent years developing music education tools under the Little Composers brand, designed for children who possess a musical ear but have not yet reached the reading stage. Over time, it became evident that the machine values these children more as consumers than as students. This realization was a catalyst, prompting me to step back and recognize that the internet no longer functions as it once did.
I have tried to step away from the machine before, but I always failed. I could not reconcile the desire for autonomy with the necessity of utility. Local AI changes that equation. It allows me to shed the shackles of dependency and, for the first time, succeed in becoming the architect of my own space.
THE EXIT PROTOCOL
The Exit Protocol is my blueprint for cognitive sovereignty: a deliberate effort to replace platforms that monetize presence with tools under my own control. My environment is built upon three core principles:
- Private Intelligence: I prioritize local inference, utilizing tools like llama.cpp to run Large Language Models on my own hardware, ensuring my intellectual explorations are never harvested by external datasets.
- Technical Autonomy: I build my workflows around self-hosted, open-source systems that I can audit and manage, ensuring the digital infrastructure obeys the user rather than the vendor.
- Creative Focus: I decouple my tools from the tracking-heavy ecosystems of the modern web, maintaining a workspace dedicated to deep work, including music sequencing and software development, free from algorithmic interference.
This is not about technical perfection; it is about autonomy. I believe you should be able to examine a tool's code and revoke its permissions with absolute certainty. By automating the mechanical, I preserve space for the things that do not scale: face-to-face conversation, music composed from genuine emotion, and time with family where devices are simply off.
WHY THIS SITE EXISTS
These pages exist for those who feel stuck in the noise. Instead of vague theories, I offer practical paths and functional tools. I show what works in practice and let those who care figure out the rest.
If your interest lies with technical specifics, such as stack details or real-world Local AI setups, you will find them noted in the Reading Room.
You may contact me if you wish to discuss any part of this path, whether practical or philosophical.
I remain online only as long as it serves this aim: helping others regain their focus, and reminding myself why I stepped away in the first place.