Add system requirements to README

Author: TriangularDev

README.md

@@ -42,6 +42,39 @@ That’s why I made **TriOS**.
 
 **Note:** TriOS is currently in **pre-beta**. It’s functional and (mostly) stable in testing, but I **don’t recommend using it as your primary daily driver** just yet. Things are still evolving rapidly.
 
+---
+
+## System Requirements
+
+TriOS is built to run on a wide range of hardware — from modest machines to powerful workstations.
+However, for the best experience, especially when gaming or developing, stronger hardware is recommended.
+
+### Minimum Requirements
+
+| Component   | Minimum Specification                                     | Example Hardware                                    |
+| ----------- | --------------------------------------------------------- | --------------------------------------------------- |
+| **CPU**     | Dual-core 64-bit processor                                | Intel Core i3-6100, AMD FX-6300, or newer           |
+| **GPU**     | Integrated or low-end discrete GPU capable of running KDE | Intel HD Graphics 530, AMD Radeon R5, NVIDIA GT 710 |
+| **RAM**     | 2–4 GB                                                    | 4 GB strongly recommended                           |
+| **Storage** | 32 GB (SSD or HDD)                                        | SSD highly recommended for speed and reliability    |
+| **Display** | 1366×768 or higher                                        | Any modern 720p+ display                            |
+| **Network** | Internet connection required for installation             | Ethernet or supported Wi-Fi adapter                 |
+
+### Recommended Requirements
+
+| Component   | Recommended Specification                               | Example Hardware                                              |
+| ----------- | ------------------------------------------------------- | ------------------------------------------------------------- |
+| **CPU**     | Quad-core or higher, modern 64-bit architecture         | Intel Core i5-12400, AMD Ryzen 5 5600, or newer               |
+| **GPU**     | Mid-to-high tier GPU suitable for gaming or development | NVIDIA GTX 1660 Ti / RTX 3060, AMD RX 6600 XT, Intel Arc A580 |
+| **RAM**     | 8–16 GB                                                 | 16 GB ideal for development workloads                         |
+| **Storage** | 512 GB+ SSD                                             | NVMe SSD preferred for fastest performance                    |
+| **Display** | 1920×1080 (Full HD) or higher                           | 1080p or 1440p recommended for workstation use                |
+| **Network** | Broadband connection                                    | Useful for updates, Steam, and package downloads              |
+
+TriOS will **run fine on older or modest systems**, but for a smooth KDE experience and creative workloads, modern midrange hardware or better is encouraged.
+
+---
+
 ## Version Naming
 
 TriOS version names follow a simple and consistent format:
@@ -55,7 +88,9 @@ For example:
 
 Future versions will continue this naming pattern, aligning with each major Debian release and a unique TriOS codename for clarity and identity.
 
-For TriOs development, you can see surface-level progress in the [Trello board](https://trello.com/b/PD5ehPOS/trios-operating-system).
+For TriOS development, you can see surface-level progress in the [Trello board](https://trello.com/b/PD5ehPOS/trios-operating-system).
+
+---
 
 ## License
 
@@ -67,6 +102,8 @@ Please note:
 * Non-free firmware and proprietary drivers are redistributed under the terms provided by their respective vendors.
 * For full license information, see `/usr/share/doc/*/copyright` within the installed system.
 
+---
+
 ## Downloads
 
 TriOS is built for **amd64**. Future builds may also be available for **i386 (32-bit)** and **arm64**.
@@ -86,6 +123,8 @@ You MUST have a working internet connection when installing TriOS.
 **Important:** The official TriOS Updater (once released) **will not support updating from non-production builds**.
 If you’re running a nightly or dev build, you’ll need to manually reinstall the production version to continue receiving official updates.
 
+---
+
 ## Building the ISO from Source
 
 I spent **way too much time** getting this automatic build system to work, **for your convenience.**
@@ -106,7 +145,8 @@ Pull requests containing extra data generated by `lb build` or other temporary c
 
 When compiling, the branch you use depends on your purpose:
 
-* If you want to test the latest changes or peek in on developer status, use the **dev** branch. (Or you could, y'know, use the already compiled build)
+* If you want to test the latest changes or peek in on developer status, use the **dev** branch.
+  (Or you could, y'know, use the already compiled build.)
 * If you don't trust me and just want the production system but built by yourself, use the **prod** branch.
 * If you want to run TriOs with your own modifications, use **your own directory**, whatever that may be.
 
@@ -115,5 +155,3 @@ When compiling, the branch you use depends on your purpose:
 Boot the ISO in a VM or from a USB stick to verify functionality before distributing it.
 
 But seriously, **please** test your builds before telling other people they’re safe to use.
-
-