Simundis · Build dossier

What the code says

• The top-level simundis folder is not a git repository: six repositories exist (backend, frontend, governance, minecraft, valheim, workstation) and the earlier monorepo is marked as an archived legacy source

  Source simundis/README.md

• 4,074 tracked files across the six repositories (backend 971, frontend 2055, minecraft 602, governance 206, workstation 190, valheim 50)

  Source git ls-files (6 repos)

• The backend holds 446 Python files, 213 of them in the simundis package, 245 imperative aiohttp route registrations and 1,411 test functions

  Source simundis-backend/simundis/

• The OpenAPI spec lists 264 path keys and 271 operations, but the GenericResponse reference appears 330 times, so response schemas are placeholders

  Source simundis-backend/contracts/openapi/paths/

• Tests total 2,361 Python test functions plus 126 Vitest cases across 21 files; CI is 42 GitHub Actions files, all on self-hosted runners

  Source simundis-workstation/.github/workflows/

• The frontend has 81 Svelte files and 36 page modules, but the 735-file dist is gitignored; the launcher is 20 Rust files with no build output

  Source simundis-frontend/clients/hub/

• Only ru and en exist: SUPPORTED_LOCALES is (ru, en), inlang lists the same two, and only messages/en.json and messages/ru.json are tracked; in the regional contract the code AR means Argentina

  Source simundis-backend/simundis/web/locale_middleware.py

• simundis-minecraft is operational tooling, not a mod: 187 Python files, 36 shell scripts, 24 Java files, 59 mod jars, 29 datapacks, and 107 declared container_name entries overall

  Source simundis-minecraft/simundis/

• The web lane was published on 2026-10-12 on the owner's cloud host (2 vCPU, 4 GB, 80 GB, $8 per month): the container takes 214 MB of its 1 GB limit, the apex, ru and hub pages answer 200 through the Cloudflare tunnel already present there, and wiki, forum, chat and shop answer 502

  Source simundis-backend/docs/PROD_RELEASE_LANE.md

Module state

1. implemented

   The platform backend and the Minecraft operations contour

   Substantial control-plane code with an SRE subsystem, a bot and payment wiring; on the game side, host scripts, an RCON client, automated shutdown and tunnel configurations.

   Source simundis-backend/simundis/

2. partial

   The hub frontend and the launcher

   81 Svelte files, 36 page modules and 126 test cases exist, but no built artifact is in history and the pages depend on the backend. The launcher has no build output directory.

   Source simundis-frontend/clients/hub/

3. partial

   Governance as the contracts repository

   206 files: 47 contracts, 69 documents, 6 ADRs and a v4.4.0 pin vendored into the other repositories. Yet four declared contract emissions are missing, and 23 Python files contradict its own rule that Python does not live here.

   Source simundis-governance/simundis-version.yaml

4. not implemented

   The shop and the catalog portal as modules

   services/vendure is a thin wrapper over the core package, and the services/backstage catalog holds a single README: these are scaffolds, not working modules.

   Source simundis-backend/services/backstage/plugins/README.md

5. on roadmap

   Federation, per-endpoint schemas, Cosign and SBOM, and an open release

   The public roadmap marks federation activation as ready in code but awaiting a second server, raises the coverage floor from 20 to 40 percent, and plans to drop GenericResponse; the open release is scheduled for v2.0.0 and the stated date is admitted as missed.

   Source simundis-governance/docs/PUBLIC_ROADMAP.md

6. illustrative

   The simundis repository as part of the ecosystem

   The archived monorepo survives only as a scratch clone tagged v-final-monorepo; the top folder is not a git repository and its README explicitly forbids using it for new work.

   Source simundis/README.md

How this was checked

• The six-repository topology with version pinning exists

  The workstation README lists exactly six repositories pinned to GOVERNANCE_REF v4.4.0 with CI vendoring; governance contracts restrict owner_repo to backend, frontend, minecraft, valheim and workstation.

  Source simundis-workstation/README.md

• Secrets in tracked files are held as ciphertext

  The tracked environment files hold ENC[AES256_GCM] values with SOPS metadata, the .sops.yaml policy is tracked, and tunnel tokens appear as an environment-variable template rather than a literal. No private encryption key exists in the repositories.

  Source simundis-backend/.sops.yaml

• Its own secret-audit tooling is present in the code

  A 7,648-byte RCON secret-audit script and its test contract are tracked in git.

  Source simundis-minecraft/tools/host/rcon_secret_audit.sh

• The numbers come from counting git, not from copying documentation

  4,074 files, 42 workflows, 2,361 test functions, 126 Vitest cases, 264 OpenAPI paths, 29 CREATE TABLE statements and 107 declared containers were recounted via git ls-files and git grep.

  Source simundis-backend/

Limits of these claims

• The dossier rests on a static audit, but the web lane really is built and running: an image from backend revision d122e1a with vendored frontend 460d122 was verified by public HTTPS requests on 2026-10-12; the game and infrastructure lanes remain unverified.
• The public host is confirmed only for the web lane: the apex, ru and hub pages answered 200 in the 2026-10-12 check, while wiki, forum, chat, shop and sign-in stay 502, so the platform as a whole cannot be called working.
• There is no Arabic interface: the locales are ru and en only, so the dossier cannot claim RTL or MENA support.
• The metrics are file counters (paths, declared containers, test functions): not coverage, throughput or player counts.
• The working trees are dirty by 117 uncommitted lines across six repositories, so HEAD does not describe exactly what was read on disk.
• The eight-repository framing is overstated: its own documents list six, the archived monorepo is flagged as unfit, and the pack repository appears in no contract and exists locally as eight files.
• An open licence is a plan: the tracked wording is All rights reserved, pyproject states MIT in places, and several repositories hold no licence file at all.

Why there is no live build

Why there is no live build

There is no build published from this repository: version control holds no built static artifact (the hub dist folder is gitignored, the hub depends on the backend for pages, authorisation and status, and the launcher has never been built). The public address is not a build from here but the project's own web lane on the owner's cloud host: a backend-plus-hub image raised on 2026-10-12 serves the apex, ru and hub pages with 200, while wiki, forum, chat, shop and sign-in answer 502 because those services are not deployed. The project is presented as still in development.