Public pages from copec’s homelab wiki.
topics/homelab
- About this homelab — A small home datacenter run like production — Proxmox and Ceph, VyOS with VLANs, InfiniBand, ZFS, FreeIPA, a self-hosted DNS primary, WireGuard failover, all declared in Salt and changed through merge requests, with an AI agent working alongside the operator.
topics/saintcon
- Arena Fighter: copec bot versions — Which copec bot name and version played on the Arena Fighter ladder (arena.bagofassets.com), and when: the development line copec-dev@next, the numbered releases copec@r
- , the sparring bots that play fixed old builds, and the history before numbered releases, with match counts, records and rating change. - Arena Fighter — tester observations and feedback (2026-10-05) — Public tester notes on Arena Fighter (arena.bagofassets.com), the SAINTCON bot game by Tristan Rhodes. What we built and played, ladder-wide numbers from 416 archived matches, what works well, and feedback (a centre-pillar stalemate, docs links that 404 on the hosted ladder, no local test path for outside players, small inconsistencies).
- Arena Fighter: a fresh context’s plan (2026-10-25) — The answer a fresh Claude context gave to the game brief (topics/saintcon/arena-game-brief) with no tools and no knowledge of our attempts: search-centred (exact engine port, simultaneous-move matrix search at depth 1-2) with learned opponent model + leaf value, a belief tracker for step parity / attack cooldowns / fog, and a league + held-out-clone gauntlet for evaluation.
- Arena Fighter: a self-contained game brief for a fresh mind — Complete, method-neutral description of the Victris Arena Fighter game (rules v0.22.1): grid, maps, fighters, weapons, tick order, fog, zone, protocol limits, ladder and matchmaking, what real matches look like, and the resources available to a bot author. Written to be pasted into a fresh context to get its intuitive approach.
- Arena Fighter: rename request for copec’s bot versions (for the ladder operator) — A precise, machine-readable request to the Arena Fighter ladder operator: re-attribute 311 already-played matches of copec’s bots to the version names they really were, so the ladder’s per-bot version history matches copec’s naming scheme (development copec-dev@next, releases copec@r
- ) from the start.
topics/salt
- mcp-salt: letting AI agents operate a SaltStack fleet — mcp-salt is an MCP server that lets AI agents inspect and change a SaltStack fleet through salt-api, under their own per-identity credentials. This page covers its architecture, its tool families (fleet operations, two-phase changes, an LLM-maintained wiki, GitLab merge requests, mTLS client certificates and an ‘external brain’ of facts and reasoning), the master-side runners behind them, and the security model: the server only advises and Salt decides, writes go through runners, every change is previewed and confirmed, secrets stay out of job space, everything is audited, and humans merge.