1 catalog source map and record routing
forgejo-actions edited this page 2026-07-15 12:43:13 +00:00

Catalog Source Map And Record Routing

Purpose

Catalog source maps tell tools which shard owns each game-data record so editors and migrations write the shard, not the generated aggregate.

Steps

  1. Read the game-data shard manifest.
  2. Compose the aggregate from declared sections and source paths.
  3. Record source map entries for each authored and generated record.
  4. Route editor saves, repairs, and refactors through the source map.
  5. Preserve generated-family provenance when rows come from generators.

Expected Outputs

Each record should have a source owner or generated provenance. Dependency paths should explain which shard invalidates the aggregate. Editor writes should target the owning shard.

Common Mistakes

Common mistakes include editing assets/generated/gameplay/game_data_catalog.json directly, declaring the same section twice, moving shards without updating the manifest, or losing generated-family provenance.

Recovery Paths

Regenerate the aggregate from shards, inspect duplicate section/path diagnostics, and repair source map ownership before applying item or vendor-stock refactors.