I might accept the premise that inflation is higher than officially reported, but I don't accept the relevance of your evidence in support of that premise.
They faked the ship's destruction, letting the Primarch think he could pursue the objective at his leisure. He could take his time being petty and destroying the Archive. Discovery visibly escaping would put him under time pressure. If he delays to indulge his pettiness, Discovery could get the technology. They'd be using themselves as bait to lure the Breen away from the civilians.
Also, the Primarch only made his threat against the Archive later. If they'd jumped immediately after the away team was aboard, it would have been before the threat was made. It also would have been before the Breen's weapon demonstration, so the Archive would have been 100% intact when they left. At that moment, they had every reason to believe that the Archive was only in danger due to their presence. The logical, civilian-saving response would be to remove their presence.
Sometimes, it seems like they forget about the spore drive. They could have leapt to the other side of the galaxy the instant the away team beamed back from the Archive. The Breen might have the ability to destroy the Archive, but with Discovery gone, it wouldn't gain them anything and how ever long it took them would be time lost for chasing Discovery. When the Breen catch up, Discovery could just jump to the other other side of the galaxy.
Also, why didn't Discovery prepare a fake clue? With 31st century replication, it couldn't have taken more than seconds to prepare a reasonable facsimile of the original. Moll did no more than a visual inspection of the artifact to affirm its authenticity and she had never seen the completed object, only some of the pieces. The real artifact is a small obelisk with a button on top. So, make a small obelisk with a button on top that projects coordinates to a random star system. There would be no way for the Breen to discover the deception except to go there and find nothing.
I think systemd targets work opposite to your expectation. The Wants in [unit] define the things that that unit needs to already be available. For instance, you might add Wants=network.target to the unit for nginx so that it won't try to start until the network is available. When I wrote a unit to start my company's application, I also had Wants=postgresql.service to ensure that the database came up before the application. Remember that sysyemd tries to run as many things in parallel as it can. This is one thing that makes it much faster than classic sysvinit which started things sequentially. But it means race conditions can occur. You use Wants to break those races where necessary. The targets that you'd specify in WantedBy in [install] more closely resemble SysV runlevels. You might want to read how runlevels used to work in SysV, in order to understand systemd targets.
Every user can enable services from /etc/systemd/user for their account. If the user doesn't log in, their instance of the service won't start. There is a way to have user services launch without logging in, but that would obviously be nonsensical for desktop services.
I don't think systemd would find units in /etc/systemd/user/KDE. Look at the mess that is /usr/lib/systemd/system. Organization doesn't seem to be a thing.
For your unit files, you have Wants in the [Install] section. That is not correct. Wants belong in the [Unit] section. The [Install] section is where you define WantedBys. You may want to read the man page for systemd.unit.
To interact with user services, you do have to always use systemctl --user.
If you put your user unit files in /etc/systemd/user, they're accessible to all users. If a particular user wants to enable the service, they can run systemctl --user enable $service. Defining the unit in ~/.config/systemd will mean only the one user will be able to start the service. Defining the unit in /etc/systemd/system indicates it is not a user service but a system service.
Roger, at Cornell University they have an incredible piece of scientific equipment known as the tunneling electron microscope. Now, this microscope is so powerful that by firing electrons you can actually see images of the atom, the infinitesimally minute building blocks of our universe. Roger, if I were using that microscope right now... I still wouldn't be able to locate my interest in [Intuit's] problem.
The danger is that places that don't get cold often get hot. And don't forget about climate change with regard to heat. Some homeless around Houston die every summer when they don't have access to air conditioning.
I'm increasingly of the opinion that settlements should be outlawed in many cases. Settlements mean a case ends without a final ruling. If the parties could resolve their issues without a court, then they never should have sued. If they bring the courts into it, then the court process should be followed to the end.
Paxton made a request of the hospital that 1. He knew they would not comply with and 2. Was not legal. It was pure grandstanding. In a settlement, he escapes any penalty for his abuse of office. At the least, definitely losing the case would look worse for him than just settling.
Companies also use settlements to avoid being judged guilty of various abuses. Settlements almost always include NDAs and no admission of guilt by the company. So, some of the people harmed get a huge monetary payout, but the company can keep on hurting others.
It doesn't have to be the main GPU. I'm not even sure it would be possible to pass through integrated graphics. But if all you need is HDMI output, you can use the absolute cheapest GPU you can find (assuming there's an open PCIe slot). PCIe pass-through does require CPU support (Intel VT-d or AMD-Vi) on the host and may need to be enabled in the BIOS/UEFI. I have an NVIDIA Telsa card passed through to a VM on my Proxmox server, but I'm only using it for compute; my card doesn't even have a video output.