Blueprint feature
Publisher
Governed publishing with sanity-check history for downstream review.
What it does
Publisher runs pre-flight sanity checks on geometry, naming, file paths, and dependencies, then stores the result as part of the asset history.
Key capabilities
- Customizable sanity checks
- Validation history stored with publishes
- Dependency tracking to origin
- Format conversion triggers
Short answer
What is Publisher?
Publisher is the Blueprint workflow for governed production publishing, pre-flight validation, dependency checks, and publish history.
Use cases
- Run publish checks
- Store validation history
- Prevent broken assets from moving downstream
Built for
- Artists
- Supervisors
- Pipeline TDs
FAQ
Frequently asked questions
What are sanity checks in Publisher?+
Sanity checks are configurable validations for geometry, naming, paths, dependencies, metadata, and studio rules before an asset is published.