Transit is compiling a platform schema plug-in for authority viewers. What should the build match?
Select an answer to reveal the explanation.
Short Explanation
If the trains run on gauge X, do not build wheels for gauge Y. Match the authority's OpenUSD ABI so the platform schema plug-in actually loads.
Full Explanation
Transit compiling a platform schema plug-in for authority viewers must match the OpenUSD ABI and version used by those deployed viewers. Schema plug-ins participate in runtime type/schematics loading; an ABI mismatch means the plug-in will not load, types will be unknown, or processes will abort. Authority IT pins viewer builds for certification—your schema plug-in is part of that same compatibility surface.
Matching 'any USD minor version as long as the file extension is .usd' confuses file format with runtime plugin ABI; .usd is not an ABI contract. Building only against the USDA ASCII parser and ignoring runtime plugin loading misses how schema plug-ins are consumed in viewers. Targeting a private game-engine USD subset without plugInfo metadata produces an island binary that authority viewers cannot discover or load through standard USD plugin mechanisms.
Exam caveat: file extension ≠ compatibility. ABI + version + plugInfo registration are the triad for custom schema plug-ins in municipal deployments.
Operational check: compile against the authority's pinned USD, register the schema plug-in, launch the deployed viewer build (not a laptop tip build), open a platform stage that applies the custom schema, and confirm attributes/types resolve without fallback-to-unknown prim type behavior.