Parks wants human-diffable fountain setups in git and fast loads in public viewers. Which approach fits USDA/USDC trade-offs?
Select an answer to reveal the explanation.
Short Explanation
Git loves readable USDA the way editors love plain text. Publish USDC to viewers when you want snappy loads—best of both trade-offs.
Full Explanation
Parks fountain setups that must be human-diffable in git and fast in public viewers should split authoring from delivery. Author and version fountain setups as USDA in git for clear peer review and history, then publish USDC packages to viewers for efficient loads—using each encoding where it wins instead of forcing one file to serve opposite goals.
Committing only USDC crates to git makes reviews noisy or opaque binary diffs and weakens change auditability for civic assets. Forbidding USDC entirely ignores viewer performance needs; modern USD viewers open crates routinely and expect them for large packages. Storing fountain meshes as JPEG screenshots replaces a 3D twin with pictures and fails both git-as-source-of-truth for 3D content and interactive public viewing.
Exam caveat: Publish pipelines must keep USDA and USDC content hashes or build IDs aligned so a viewer package can be traced to the exact reviewed USDA revision during audits or rollback.
Operational check: Merge a fountain USDA change via git review, run the publish step to USDC, open the viewer package, and verify visual parity plus provenance metadata pointing at the reviewed commit before releasing to the public site.