Materialization
A Materialization is a physical representation of a Logical Artifact.
Logical Artifact
↓
Materialization Profile
↓
Physical Representation
Explicit profiles
Reference profiles include concepts such as:
kristal.materialization/inline-json/1
kristal.materialization/native-blob/1
kristal.materialization/segmented-jsonl/1
kristal.materialization/kristal-state-v6/1
Advanced columnar/runtime profiles may evolve independently from the core.
Factorization
Repeated logical metadata may be stored once and applied to many records if reconstructability is preserved.
DEFAULTED METADATA != LOST METADATA
Dictionaries
A physical representation may replace repeated semantic IDs with local ordinals.
LOCAL ORDINAL != SEMANTIC IDENTITY
Ordinals may change during repack and must never become external stable IDs.
Segments
A Segment is an immutable physical unit. Segment boundaries are not semantic boundaries by default.
SHARD != SEGMENT
Partitioning
Physical partition strategies are hidden implementation/materialization choices. A logical query must not depend on whether an artifact uses 16, 256 or 1024 physical buckets.
Planner boundary
The Standard defines valid profiles, not a mandatory optimizer. Tooling may recommend a profile, but the chosen profile must be explicit and reproducible.