Purpose
Synchronize Aeries-derived roster and class data into Google Classroom.
Current state
Recurring scripted sync exists in Aether with multiple daily runs and explicit archive or delete safeguards for end-of-year cleanup. Registry alignment now also treats school-specific incoming-student readiness channels, such as the BJHS implementation and related BOHS incoming or grad-year groups, as part of this Classroom sync scope rather than as standalone integrations.
Next step
Document production scope, scheduler ownership, school-specific readiness-channel implementations, and cross-boundary handling with guardian invite automation.
Interfaces
Inputs- Aeries class data
- teacher and student roster data
- sync mode controls
Outputs- Google Classroom course and roster updates
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesContributes in this stage.
Human InterfacesNot in scope.
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 is canonical for course, section, teacher, and student roster state.
- Google Classroom is the downstream target for classroom roster state.
Safe handling
- Protect API credentials and class roster exports.
- Use guardrails for removal or archive modes during end-of-year changes.
Operational notes
Reliability posture
Concrete script and cron evidence exist, but scope overlap with other roster workflows and owner routing still need clearer runbook coverage.
Observability
- script logs
- cron output
- Google API response handling
Security and privacy
Restricted student instructional roster data; internal only.
Dependencies
Upstream- Aeries data quality
- Google Classroom API access
- scheduled runtime
Downstream- instructional roster readiness
- adjacent guardian and readiness workflows
Ownership
OwnersTechnology Services
UsersTechnology Services, site stakeholders
Aeries to Google Classroom Sync
Operational Notes
- The registry ties this workflow to
Push-AeriesToGoogleClassroom.sh and a concrete cron schedule. - It is related to the broader student rostering ecosystem but still merits its own connector record.
- This page tracks class and roster synchronization; school-specific incoming-student readiness channels belong here when they are implemented as Classroom sync variants rather than as standalone systems.
- Guardian invitation and parent-contact behavior is handled in the adjacent Aeries to Guardian Invite Sync workflow.
- Failure leaves Classroom rosters stale and increases manual cleanup for sites.
Registry Alignment
- Mapped registry entry:
INT-042 - Registry clarified: there is a concrete Aether script and multi-run schedule behind the inventory name, and former school-specific readiness channels such as
INT-019 are now treated as component implementations within this broader sync. - Validation gaps: confirm the current production scope, scheduler ownership, school-specific implementation inventory, and relationship to adjacent Classroom workflows.
