Where the code comes from

Mikronix is AI-developed. Every line of C in this project was written by language-model agents — a small fleet of Qwen3.6-35B instances on local llama.cpp servers, working a kanban board under agent orchestration. There is no human author behind the code.

**Konrad Lother, the project's inventor, had no plan of his own.** He did not write the C, he did not design the modules, he did not sketch the architecture in advance. He steers, decides, fixes the hardware, and reads the result to learn from it. The system is his learning instrument, not his engineering product.

You run this at your own risk. The code passes its regression suite and boots on real hardware, but no person fully understands every line. It is a transparent, auditable AI artefact — not battle-tested system software.

Why this page exists

Because the honest statement is more interesting than a quiet one. An operating system whose entire provenance is machine-made is an unusual object: you can read the git log and watch an AI team build a Unix, decision by decision, mistake by mistake.

Every commit carries the responsible agent persona as author (pagefault, groff, valgrind, jtag). The controller's journal (records what was achieved and what had to be corrected) is in the repository under refs/journal/. The statement of provenance travels with the code: see AI-PROVENANCE.md in the repo, and sys/mnx/provenance.h — a header included by every public kernel header, so the fact is physically present in every compilation unit.

The fork rule

If you fork or redistribute Mikronix, keep this statement with the code. That is the only license condition beyond the BSD 2-clause text in each file.