Update¶
Purpose¶
Owns editor-update abstraction contracts used by centralized editor update processing.
This territory provides marker and participation contracts for systems that integrate with shared editor update workflows.
Owns¶
- Editor update contracts
- Update participation markers
- Editor update workflow seams
Does NOT Own¶
- Update execution
- Update scheduling
- Editor tick orchestration
- Preview updates
- Rendering updates
- Export workflows
Allowed Dependencies¶
Update abstractions may depend on:
- Shared editor concepts
- Marker interfaces
Update abstractions should avoid depending directly on:
- Preview systems
- Rendering systems
- Export systems
- Panel systems
- Window systems
Notes¶
Update abstractions exist to identify systems that participate in centralized editor update workflows without creating direct dependencies on the update infrastructure itself.
Implementations remain owned by higher-level editor orchestration systems.
The abstraction layer only defines participation.
Future Candidates¶
- Update ordering contracts
- Update priority contracts
- Editor lifecycle participation contracts