The public systems catalog lists game consoles, handhelds, home computers, and multi-system video tools that still have a third-party hardware scene. Each listed mod is marked open source, proprietary, mixed, or unknown. The inventory focuses on addon PCBs (flash carts, ODEs, RGB boards, replacements). MiSTer FPGA cores are software recreations, not addons to original hardware, and are not catalogued as system mods.
System photographs are hosted copies of freely licensed Wikimedia Commons images, or a photo from the project’s own GitHub tree when Commons has nothing usable. Credits live on /credits. Open-source mod cards prefer a hardware photo copied from the upstream repository (bun run fetch:mod-photos). tscircuit SVGs are only a fallback. Those thumbs are catalog previews, not the unimplemented pcb_render worker artifacts.
What gets a project page
Only open-source repositories become mod project pages. Those pages are generated at build time from the catalog plus optional git-mirror metadata (commit SHA, default branch, WalGit URL). Proprietary products stay on the system page as references. We do not clone or re-host their firmware.
Three stores
- WalGit owns versioned hardware source. Application code never reads or writes WalGit objects directly.
- Artifact storage owns generated renders, GLB models, and reports under
artifacts/…only. - PostgreSQL owns visibility and membership. It is not a git store.
Generated board images are uploaded to the artifact CDN during deploy when a render job has produced them. They are not checked into git. Set PUBLIC_ARTIFACT_CDN_URL so pages can point at artifacts/mods/{system}/{slug}/board-top.png and friends.
The KiCad parse and PCB render worker jobs still fail visibly until they are implemented. Missing CDN objects are expected until then.
Dual documentation tree
The same system markdown is written to apps/web/src/content/systems/ and docs/viberetro/. Keep those trees identical in this repository and in TensorFleet/viberetro when that remote exists.