Purpose
Deliver current Aeries roster data into Savvas Realize through the district's scheduled instructional access workflow.
Current state
The registry now promotes Savvas Realize into its own child record based on the active Integr8r `SavvasRealize` job, explicit job definition in `Config/Config.ps1`, and corroborating weekly-report evidence about nightly Aeries-based access updates.
Next step
Document exact schedule, site scope, and whether all active Savvas use still depends on the same OneRoster-style upload path.
Interfaces
Inputs- Aeries roster and identity data
- Clever or vendor configuration
- site or program scope rules
Outputs- Savvas roster payloads
- student and teacher access readiness
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesContributes in this stage.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Data integrity and contracts
Source of truth rules
- Aeries remains canonical for roster and identity source data.
- Clever or the vendor platform reflects downstream access state and should not silently become the source of truth for SIS records.
Safe handling
- Limit vendor admin access and exported roster artifacts.
- Treat student and teacher roster data as restricted instructional data.
- Document scope and approval expectations before expanding to new sites or programs.
Operational notes
Reliability posture
The child workflow matters because access drift quickly becomes classroom-visible, but owner, cadence, and launch-path details are still not centralized.
Observability
- vendor-admin checks
- site access incidents
- wrapper or upload runtime evidence where available
Security and privacy
Instructional roster and access data remain restricted student and staff records and should stay within approved vendor-sharing boundaries.
Dependencies
Upstream- Aeries data quality
- OneRoster-style packaging
- vendor endpoint availability
Downstream- teacher and student access to the platform
Ownership
OwnersTechnology Services
UsersEducational Services, school sites, Technology Services
Savvas Realize Instructional Rostering Workflow
Operational Notes
- The registry treats this as a first-class child workflow rather than leaving it inside generic Clever ecosystem context.
Registry Alignment
- Mapped registry entry:
INT-082. - Registry clarified: this child workflow now has enough production-backed evidence to justify a dedicated Atlas page instead of remaining only inventory context, and
Config/Config.ps1 provides direct Integr8r job evidence for the scheduled workflow. - Validation gaps: exact cadence, launch path, and active site scope still need confirmation.
