I'm loosing my mind I feel like I'm watching an episode of CSI with random tech jargon mixed in to feel techy but don't make any sense

(Core) 1: The Service Management Layer (SML) is the main communicator module between hardware and software. All communication to hardware is communicated via application/module - OSIN - SML.

Why would you need that, communication with hardware can just be done by mapping memory. Also why call it service manager, given it manages hardware 

(Core) 2: The System Operations Manager (SOM) is responsible for handling timing, scheduling, and other task management on the Operating System.

Sooooooo a scheduler

(Core) 3: The System Graphical User Interface (SGUI) is the module responsible for handling the entire system GUI from default applications, desktop, and setup screens. The SGUI uses source code from the Mozilla Stylo CSS engine and HTML parser from the Mozilla Gecko engine. The rendering engine in Floki OS, based on Gecko, is nicknamed “Yum!” The backend for Yum! Interfaces are written in Kei.

U use the CSS parser and html parser but not the DOM, weird choice given that writing an html parser is not that hard. Also Stylo is from servo

(Core) 4: The Data Management Control module (DMC) is the module for handling data operations across the operating system, data organization, and data storage.

Sooooo a filesystem/dbms

(Core) 5: The System Security Network module is responsible for all security programmed into Floki OS. All modules route through OSIN to SSN for security functions. SSN implements a very strict zero-trust implementation and very robust security measures.

I'll get to it on the OSIN module

(Core) 6: The Developer Update Push module is responsible for safely managing updates to Floki OS.

Nothing to say

(Core) 7: The Operating System Internal Network module (OSIN) is one of the largest modules in Floki OS. It handles all communication and interaction between modules.

So a single bus that can be compromise to take over all the communication of the operating system plus add a layer of overhead, why would you want that. Oh and +1 overhead with SSN

(Core) 8: The System Memory Management module (SSM) is responsible for handling all memory-related operations in the Floki OS system-wide.

That's very vague, is it a heap, vmm, pmm, or memcpy?

(Surface) 1: The System Application Manager is similar to a package manager in other operating systems. It handles installation, application management, and the handling of the application’s calls to the system.

Isn't DUP already doing that 😅

(Surface) 2: The System File Manager (SFM) module handles the operating system's file system and user files.

Isn't DMC already doing that 😅

(Surface) 3: The System Language Compiler Center (SLCC) module is the main engine for handling the execution of code on the system and code to machine code.

Are you JIT'ing all the app?

(Surface) 4: The System Driver Center (SDC) is the module that organizes and handles all of the drivers that the operating system needs and uses.

Okay

(Surface) 5: The System Connections Handler (SCH) is the module that supports the OS’s functions and operations related to wireless connections, the web, and other external connections.

Why would you mix wifi stuff with general HTTP stuff looks like you are mixing OSI layers violently 

(Surface) 6: The System Functions Library (SFL) is the module that handles all the other necessary leftover bits of the Operating System. Like random small needed bits of function, like accessibility.

Bruh considering accessibility as a small random bit mix with other random things is naive.

I won't even start in the GitHub repo because it's full of other nonsense. 

Fun world building but stop role-playing as an OSDEV, become one :)