pub struct WorldMeta {
pub name: String,
pub description: Option<String>,
pub time_of_day: Option<f32>,
pub tags: Option<Vec<String>>,
pub source: Option<String>,
pub variation_group: Option<String>,
pub variation: Option<(String, String)>,
pub style_ref: Option<String>,
pub compliance: Option<ComplianceMeta>,
pub ext_provenance: Option<ExtProvenance>,
}Expand description
World metadata.
The LLM lineage fields (prompt, model,
generation_duration_ms, biome, semantic_category) moved to
the ext-provenance extension — the core
schema is governed independently of any single producer
(spec/extensions/provenance.md).
Fields§
§name: StringWorld name (used as skill name / directory name).
description: Option<String>Human-readable description.
time_of_day: Option<f32>Time of day (0.0-24.0, for lighting presets).
Free-form style tags for gallery filtering.
source: Option<String>Generation source: “interactive”, “headless”, “experiment”, “mcp”.
variation_group: Option<String>If part of a variation experiment, the group ID.
variation: Option<(String, String)>Variation axis and value (e.g., (“lighting”, “sunset”)).
style_ref: Option<String>Style name from memory (if applied).
compliance: Option<ComplianceMeta>Compliance metadata for distribution and regulatory classification.
ext_provenance: Option<ExtProvenance>LLM lineage, under the ext-provenance extension’s namespace —
the one extension the core types carry, because generation tools
were already writing these fields and must not silently lose
them in the move. In the generated core schema the block is
free-form (true): an extension’s shape belongs to its registry
entry, not the core.