Diagnostics¶
Purpose¶
Owns debugging, logging, profiling, environment reporting, and diagnostic tooling used throughout Snap Studio Pro.
This territory provides developer-facing support systems for issue diagnosis, profiling, debugging visibility, environment reporting, and support workflows.
Diagnostics is intentionally support-tooling territory.
Owns¶
- Logging systems
- Debug object tracking
- Profiling utilities
- Environment diagnostics
- Version reporting
- Diagnostic support tooling
- Debug export helpers
- Developer-facing troubleshooting workflows
Does NOT Own¶
- Production workflow orchestration
- Preview scene lifecycle ownership
- Rendering implementation
- Export orchestration
- Panel UI layout ownership
- Feature-domain business workflows
Allowed Dependencies¶
Diagnostics may depend on:
- Unity editor/debug APIs
- Lightweight shared systems/utilities
- Environment/platform APIs
- EditorPrefs where required
Diagnostics should avoid depending on:
- feature orchestration systems
- preview orchestration systems
- rendering implementation systems
- export workflow systems
Notes¶
Diagnostics exists to support: - debugging - troubleshooting - profiling - issue reporting - developer support workflows
This territory is intentionally allowed to touch broad areas of the editor architecture where needed for visibility and reporting purposes.
Diagnostics should remain: - support-focused - observable - developer-oriented
The goal is improving maintainability, troubleshooting, and support visibility — not owning production workflows.
Future Candidates¶
- Continue isolating diagnostics from production workflow ownership.
- Avoid allowing support tooling to become hidden production dependencies.
- Maintain lightweight and developer-focused diagnostic surfaces.
- Continue centralizing environment/support reporting systems here.