Content Pack Operations

Content Pack Operations

Audience: Sysadmin Status: ✍️ Draft

Operating content packs on a live fleet: connecting an external content repository, automating the build/publish pipeline, and driving the coordinated pull + hot-reload across shards without dropping players.

Intended contents

• The source-of-truth model: content lives in an external versioned store (git/S3); no in-game editing of canonical content
• The content pipeline: author repo → CI builds/lints a pack tree → publishes a version → the MUD pulls it
• telos-pull and the in-game pull <version>: director leader-only, single-flight coordinated pull; idempotent-by-SHA; NAK-redelivery on leader change
• Version authority: the Postgres content_version row (Model 1 — Postgres stays the serving source); content_pack_registry/pack_meta
• Hot reload: reload scope-mapped to zone/region/world; validate-before-broadcast; live room-graph reconcile with version guard; which changes need a rolling reboot (shared defs)
• Multi-shard consistency: director-coordinated reload broadcast; pack-set divergence fail-closed
• Content-lint in CI and the live prune/advisory guards

---

Scaffold page — full content pending the wiki build-out.