# FrostWing Philosophy
1. Absolute User Control
FrostWing does not assume what you want.
If /proc, /dev, /sys, or even / is not mounted, that is intentional.
The system starts minimal. You build your environment.
- No automatic mounts
- No hidden abstractions
- No forced structure
You decide:
- What exists
- What runs
- What gets access
This is not inconvenience. This is raw power.
---
2. Minimalism Over Assumptions
Most operating systems try to be helpful by doing things behind your back.
FrostWing does the opposite.
- Nothing is pre-configured unless necessary
- No background processes without your knowledge
- No silent services
If something is running, you allowed it.
---
3. Privacy is Non-Negotiable
FrostWing rejects invasive system design.
Modern systems increasingly allow deep, kernel-level access for third-party software, especially in areas like anti-cheat systems.
While preventing cheating is valid, FrostWing believes that no software should have unrestricted access to your system without your explicit awareness and control.
There is no guarantee what such software may inspect:
- Personal files
- Development work
- Private data
FrostWing takes a clear stance:
- No forced kernel-level modules
- No hidden monitoring systems
- No trust without transparency
---
4. Transparency Over Trust
FrostWing does not ask you to trust it.
Instead, it ensures that you can:
- Inspect everything
- Understand everything
- Control everything
The system should be:
- Predictable
- Inspectable
- Honest
---
5. Power Users First
FrostWing is designed for users who want to:
- Understand their system deeply
- Build their environment from the ground up
- Avoid unnecessary layers
This may feel unfamiliar at first. That is intentional.
---