Skip to content

Latest commit

 

History

History
62 lines (53 loc) · 3.66 KB

File metadata and controls

62 lines (53 loc) · 3.66 KB

USD 3DGS Plugins documentation

Documentation is organized by responsibility. This follows the same taxonomy as usd-vrm-plugins, so current contracts, procedures, plans, and historical evidence do not drift into one another.

When a summary disagrees with the implementation, the implementation wins and the summary is a documentation bug. When a summary disagrees with architecture/WORKSPACE.md about structure, the workspace contract wins; structural changes must update that contract first.

Category Answers Start here
architecture/ How the workspace is structured and which dependency directions are legal. WORKSPACE.md
guides/ How to build, test, package, and install the plugin. BUILDING.md, INSTALL.md
reference/ What is supported and how source data maps to USD. CAPABILITY_MATRIX.md
roadmap/ What remains incomplete and what comes next. README.md
releases/ Immutable records for tagged releases. README.md
design/ Why the project is built this way. DESIGN_POLICY.md
adr/ Numbered, immutable architecture decision records. 0001-model-frame-is-rub.md
reports/ Evidence from real runs, including OST dogfooding. README.md
contributing/ Contributor and release procedures. RELEASE_NOTES_TEMPLATE.md

Canonical documents

Component documentation

Component-specific usage stays with the component:

Component Documentation
gaussian-ply plugin README
gaussian-spz plugin README
gaussian-sog plugin README
gaussianCore library README
gaussianUsd library README