Silo

The problem

Farming Simulator 25 reads a single mods folder, and everything in it is active at once. Players run hundreds of community mods. When the game crashes, finding the one mod responsible can take the whole evening, and conflicts between mods often show up only after a long load.

What was built

Silo adds a management layer on top of that folder without editing inside any mod. It parses the game's log, separates real errors from noise and ranks mods by the errors they caused. It flags conflicts before launch, keeps a tidy library, switches between loadouts and can bisect a broken set automatically. A cross-source catalog, served by a public read API, records where each mod comes from and lets Silo check an installed mod against the build its author published.

Around the app sit the pieces a real product needs: a project site, a Discord bot for the community, signed Windows installers with published verification steps, and a release pipeline.

How it was built

The code was written largely by AI coding agents, in bounded tasks, with a person reviewing each result against what was asked. The agents work inside written roles. The application agent owns the app and its release requests. A separate infrastructure agent owns hosting. Neither merges or releases without the owner's recorded approval.

Every server-side release goes through a request record: what changes, what was tested, how it rolls back and what was actually verified afterwards. Rollback is exercised before the approval is asked for. Health checks ("it answers") are reported separately from functional tests ("it does the job").

What it shows

• A small operation can ship and run a complete product, desktop, API, bot and site, when the agents' speed comes with review discipline.
• Public, checkable artifacts: the source, the release history and the signed installers are all on GitHub.
• The site publishes its own aggregate usage counts, with no IP addresses kept, at silo.hllmr.com/metrics.json.

Limits, stated plainly

Silo is at 1.0. Windows is the tested platform; macOS and Linux builds are a preview. It is a free hobbyist product, not a commercial engagement, so it shows how HLLMR builds, not a client outcome.