GlouOSAI Use
GlouOS uses AI to help write and maintain this wiki. This page explains exactly how, and where the limits are, so you know what you are reading.
What AI writes here
The pages in this wiki are documentation, not the operating system itself. AI is used to draft and update that documentation. It reads the parts of GlouOS that are publicly available, the source and configuration in the project's repository and released packages, and turns what they do into plain language.
So when a page says GlouOS sets a particular kernel option or ships a particular tool, that description is meant to come from the actual configuration, not from guesswork.
Grounded in the released code
Everything here is meant to map to something real in GlouOS. The optimisations, defaults and tools these pages describe are the ones committed to the public repository at github.com/Nonay-GB/GlouOS and shipped in the released packages. If a wiki page describes a setting, you should be able to find that setting in the source.
The source is the source of truth
Where the wiki and the code ever disagree, the code is correct. These pages describe it; they do not define it.
What AI does not decide
AI does not design the operating system. The kernel choices, the scheduler, the package defaults and every tuning decision are made by the maintainer and live in the code; AI only documents them after the fact.
It also does not run benchmarks or invent performance figures. Where these pages talk about performance, the wording is kept modest and tied to what a setting actually does, rather than promising numbers that have not been measured.
Accuracy and corrections
AI-written documentation can still be wrong, or fall behind changes to the code. The pages are reviewed, but mistakes get through. If something here does not match what GlouOS actually does, that is a bug in the docs: please flag it on the forums or open an issue on GitHub, and it will be corrected. Checking a claim against the source is always the final word.
Why we work this way
GlouOS is a small project. Using AI to keep the documentation in step with the code lets the wiki stay current and readable without a dedicated docs team, so the effort can go into the system itself.