Why this exists
AetherDev runs on integrations that must be reliable, auditable, and repeatable. This initiative keeps extraction, normalization, and diff-or-apply automation consistent so new connectors do not reinvent the same workflows or introduce fragile handoffs.
March 2026 Registry Reconciliation
Atlas is now aligned more closely to the enriched BOUSD registry in four areas:
- District Transfers, Google Workspace MFA, and staff Active Directory lifecycle now read as parent integrations with component pages linked underneath them instead of appearing as fragmented standalone records.
- Clever is documented as a first-class parent hub with child instructional workflows, while school-specific readiness-channel implementations stay as component context instead of standalone integrations.
- The Aeries-to-Google Sheets reporting jobs and Perpetual Data Reports Portal remain documented in Atlas as operating-model context, but they no longer present themselves as standalone BOUSD integrations.
- InformedK12, TitanHST, and Edlio pages now distinguish active production use, successor or component scope, and retired records more explicitly.
Ecosystem Parent/Child Clarification
- Student rostering ecosystem parent: district SIS-to-platform distribution remains the broader ecosystem layer.
- Clever hub child: Aeries to Clever Rostering and SSO Hub is the governance and distribution control point for app assignment and vendor enablement.
- Downstream instructional children: i-Ready, HMH, Savvas, APEX, and related platform pages represent child workflows under the Clever/distribution layer.
- Google Classroom and guardian connectors: Aeries to Google Classroom Sync and google-classroom-guardians remain adjacent child paths for classroom and family-facing workflows.
March 25, 2026 Workbench Follow-Up
The latest registry-backed workbench pass added and clarified high-impact runtime context:
- Integr8r inventory drift was corrected (39 configured jobs; 26 enabled; 13 disabled or dormant), and Atlas now reflects that as current runner context rather than older counts.
- Edlio is now tracked as a first-class validation-needed workflow with a dedicated Atlas project entry.
- TitanHST and Google Groups documentation now explicitly distinguishes active legacy runtime evidence from modernization/successor implementation paths.
- Transfer and extract-family pages now carry clearer cross-repo runtime layering and follow-up ownership gaps.
Measures of success
- New integrations reuse shared connector patterns and mapping layers.
- Diff-or-apply workflows produce consistent audit artifacts.
- Connector runs are repeatable with clear retry and rollback behavior.
- Integration ownership, run cadence, and validation gaps are documented and visible.
Active projects
- District Transfer Tracking
- Google Workspace MFA Enforcement and Reporting
- Staff AD Account Management
- Student Active Directory Sync
- Frontline Substitute and Employee Account Lifecycle Automation
- Aeries to Google Classroom Sync
- ParentSquare Custom Contact Groups Sync
- Aeries to Clever Rostering and SSO Hub
- ASCIP Sync Engine
- InformedK12 Sync
- HMH MyHRW / ThinkCentral Instructional Rostering Workflow
- OCDE S1S Summer School Roster Export Automation
- Savvas Realize Instructional Rostering Workflow
- OCDE HR to Aeries Staff Sync
- TitanHST Sync
- Google Workspace Group Membership Maintenance Automation
- Aether Integrator Platform
Key risks
- Vendor API or file-contract drift breaks established mappings.
- Production scheduler ownership stays implicit and creates support gaps.
- Component pages are mistaken for live district workflows when runtime evidence actually sits in wrapper scripts or separately scheduled jobs.
- Integration ownership is unclear during staff transitions.