Projects

The repo atlas, trimmed down to the projects that still have a point and the families that actually belong together.

This section is the public workbench for the GameCult GitHub org. Some repos are live systems. Some are research bursts that still smell faintly of ozone. Some are support machinery for the support machinery. The point is not to pretend every public repository deserves the same amount of ceremony. The point is to make the shape of the work legible without building a second museum for our own breadcrumbs.

GameCult

All the reusable parts that were tired of being copy-pasted between larger disasters.

CultLib

3 min read

CultLib is the shared runtime and protocol family for GameCult code. The C# repo is the anchor, but the public shape is now larger than one language: cultcache-ts, cultcache-rs, cultcache-py, cultnet-ts, and cultnet-rs are all part of the same push to stop persistence and wire contracts from being rewritten as local folklore every time a new tool appears.

GitHub Repo cultcache-ts cultcache-rs cultcache-py cultnet-ts cultnet-rs

Started

18 Apr 2026

Last Public Push

06 May 2026

Stack

C# / TypeScript / Rust / Python

Status

Active repo family

Founding Idea

The founding idea was not glamorous. It was correct. Shared runtime machinery should live in a shared home instead of being smeared across project codebases until nobody can tell which copy is the cursed one.

Trajectory

CultLib starts with dependency updates, JSON backing store work, I/O fixes, security cleanup, and a full CultUI port away from legacy prefab residue. Then the focus hardens around schema, persistence, and wire contracts. On 06 May 2026 the family abruptly flowers outward: cultcache-ts ships the TypeScript port, cultcache-rs lands the Rust cache crate, cultcache-py appears as the Python control-plane sibling, cultnet-ts becomes the TypeScript client, and cultnet-rs becomes the Rust peer. All of them are one day old and already clearly related, which is either encouraging or a warning sign depending on how much sleep anyone got.

The point is that CultLib stopped being “some useful C# libraries” and started becoming the canonical home for the studio’s persistence and messaging vocabulary. The separate language repos are real, but they are satellites around the same core idea.

Ambition

The ambition is to become the boring center of gravity other repos can lean on: storage that behaves, schemas that survive, message formats that stay compatible, and runtime helpers that do not need to be reinvented whenever somebody opens a new runtime with fresh ideas and insufficient restraint.

Repo Family

  • CultLib: the C# anchor repo where the schema and interop story first hardened.
  • cultcache-ts: TypeScript CultCache port with schema-backed MessagePack storage.
  • cultcache-rs: Rust CultCache crate for typed envelopes and slot-safe persistence.
  • cultcache-py: Python CultCache port aimed at control-plane and bootstrap surfaces.
  • cultnet-ts: TypeScript CultNet client and cross-runtime contract surface.
  • cultnet-rs: Rust CultNet peer with schema discovery and raw replication lanes.

History Tells On Itself

  • 2026-04-18 JSON backing store, I/O fixes, Networking Security
  • 2026-04-18 Complete CultUI Port and remove legacy UI prefabs and scripts
  • 2026-05-06 Initial CultCacheTS port
  • 2026-05-06 Create Rust CultCache crate
  • 2026-05-06 Scaffold cultcache-py
  • 2026-05-06 Add schema discovery messages to CultNet
  • 2026-05-06 Build the first CultNet TypeScript client
  • 2026-05-06 Create CultNet Rust core
  • 2026-05-06 Bring legacy CultNet into the schema-v0 fold
  • 2026-05-06 Add CultNet C# interop peer harness

Backlinks