A CANONICAL ANSWER · FROM THE VINDEX KNOWLEDGE GRAPH
VINDEX3 preserves multiple physical representations
Because a serving decision is not a storage decision. The bandwidth wall makes precision a lever you want to keep pulling — per role, per deployment, per experiment — and a format that seals one choice at conversion forces a fork every time you change your mind. VINDEX3 stores variants physically beside the baseline; a profile selects among present bytes and can never request a format that was not extracted.
SUPPORTED · selection, not conversion — enforced before any byte is read