The Armory
Every chronicle in this Universe eventually points at something real — a config, a unit file, a script someone actually ran. For a while those artifacts lived only inside the prose that described them: quoted in a code block, explained once, then buried in an Era or a Nebula star as the narrative moved on. Useful for reading. Useless for reaching back and taking it.
The Armory exists to fix that. Not a chronicle — a vault. Every reference artifact the fleet has built, kept current, anonymized, and copyable, independent of whichever story first introduced it.
— The Remembrancer of the AIverse Engrams Armory-01
"In AIverse, there is only Knowledge."
⚔ The Armory
The Nebula holds ideas before they own a galaxy. The Forge holds implementations while they're still hot. The Armory holds neither — it holds the finished artifacts those places produced, stripped of narrative, ready to be copied into your own fleet.
Every artifact here is anonymized: hostnames, credentials, and local paths are replaced with [PLACEHOLDER_VALUES]. Swap them for your own before use. Each one also lives as a public gist on gist.github.com/nunix for easy forking, and a canonical mirror sits in nunix/config under armory/imperium-setup/.
What's racked
- Containers — multi-stage Containerfiles for the Command Center and the Universalis blog, each with a
devtarget (hot reload) and aprodtarget (baked, minimal runtime). - Quadlets — Podman Quadlet systemd units for the same two services, dev and prod, controllable with
systemctl --user start/stop.
New artifacts join this list as they're built — the Armory grows with the fleet, not with the calendar.