Meticulous control over the laboratory's software ecosystem is imperative to enhance experimental reproducibility, increase transparency, and mitigate production failures. As such, achieving complete transparency necessitates stringent management of the software state within a laboratory with dependency conflicts due to incompatible software versions posing a well-recognized challenge in this regard. To address these concerns, the core design of ChemOS 2.0 incorporates an orchestration fog device that runs the necessary software layers for laboratory operations while keeping each of the laboratory modular for streamlined integration. To ensure reproducibility, robustness, and seamless deployment, the fog orchestration platform is equipped with NixOS, a declarative package manager-based (Nix) operating system known for its ability to provide precise control over system state and software versions. Nix provides precise control over the system state by enabling an accurate selection of software versions and dependencies. Defining local and global system states in NixOS revolves around the use of .nix files, containing a declarative system state recipe. Researchers can use configuration files to share digital experimental environments and deploy pre-configured operating systems on different platforms. Thus, .nix files are pluggable modules, whose addition or removal will change the state of the system. While some of the code may be hardware-specific, these files serve as a foundation for building unique SDL architectures. In our work, we have prepared a collection of .nix files containing the environmental state used for our experiments.