Skip to main content

mapv10 Schemas

Schemas and binary sidecar manifest contracts for generated artifacts.

M0-M10 ships concrete schema contracts for:

  • config.schema.json - deterministic scale preset generator config for province-slice, regional-slice, realm-slice, and the implemented continent fixture.
  • manifest.schema.json - run envelope loaded manifest-first by the viewer, with the same contract across known scale presets.
  • stage-index.schema.json - per-stage product/preview index with concrete paths, categories, and byte lengths.
  • stage-manifest.schema.json - per-stage product and validation wiring.
  • raster-product.schema.json - JSON, graph/vector/anchor JSON references, and binary product references, including f32, rg16, u8, u32, and rgba8 raster dimensions, units, and ranges.
  • influence-types.schema.json, influence-sources.schema.json, and influence-rules.schema.json - generic influence registry, source-anchor, and rule contracts. Corruption is the first registered preset, not renderer-only state.
  • tile-product.schema.json - tile coordinate indexes plus sharded raster, vector, semantic, and mesh tile family manifests with z/x/y bounds, source raster windows, LOD metadata, shard refs, and byte lengths.
  • mesh-product.schema.json - mesh family manifests for terrain chunks, water meshes, and route ribbons with local origins, byte layout, counts, and byte lengths. Borders are generated as raster/SDF products, not mesh-family manifests.
  • semantic-display-policy.schema.json - generated display-policy contract separating strategic semantic zoom from physical tile residency, including influence product requirements.
  • readiness-report.schema.json - M9 budget, aggregate artifact-size, coordinate precision, and many-tile streaming readiness report.
  • valenar-world.schema.json and valenar-world-mesh.schema.json - run-local Valenar bridge products generated by stage 15-valenar-worlddata. These define the data shape Valenar may explicitly import later while its default runtime can keep using the small dummy fixture.

These schemas document the generator/viewer boundary. The Rust generator writes the matching JSON shape, and the TypeScript viewer treats the manifest as the source of loading truth. PNG previews remain inspection artifacts only.