Atlas registry sync - March 26, 2026

This note records a focused Atlas update pass against the refined BOUSD integrations registry.

What changed

• Clarified runtime and cutover posture for TitanHST and OCDE HR to Aeries pages.
• Strengthened Clever hub governance context and parent/child ecosystem positioning.
• Tightened attendance dashboard versus extract-family dependency language so freshness assumptions are explicit.
• Expanded Munki and device-refresh pages with concrete operational behavior (mapping, readiness segmentation, operator model).
• Added first-class Atlas coverage for:
  • Classroom Display Refresh Coordination
  • WAN Connectivity Incident Tracking and Communications
  • Board Meeting Livestream AV Workflow
• Updated guardian and family-access pages to reflect mostly automated workflows with explicit manual-assist boundaries.
• Strengthened lighter connector pages (Brightly, OSTicket, Raptor, ShoreTel) with clearer behavior classification and validation targets.
• Added retirement alignment for legacy script references: Push-OCDEHRToAeries.sh and informedk12-sync-transfers.sh are now documented as retired historical paths in favor of active runtime replacements.

Remaining validation targets

• Formal scheduler/host ownership and cutover declarations for TitanHST.
• Publish the Rust runtime runbook and write-mode governance for OCDE HR to Aeries.
• Clever export contract and app-assignment governance change-control details.
• Extract-family destination sheet ownership and escalation inventory.
• Incident response template and escalation ladder for WAN continuity workflows.
• Runbook location and credential custodianship for board-meeting livestream operations.

Gap-closure follow-up (same date pass)

• Tightened the Aeries-to-Google Sheets extract family pages with concrete run.sh tab contracts and cron-path evidence from aether/docs/cron-example.txt.
• Upgraded child extract pages (MonthlyAttendance, ClassSize, DataConfDocs, PADC) from broad validation language to specific unresolved targets (owner/escalation mapping, host authority, certification handoff).
• Added stronger Integr8r-backed detail for Aeries Student Groups (exact maintained group scripts/IDs and SQL pattern) and TransTraks (export contract clearly present, upload path still unresolved).
• Updated Integr8r project inventory posture to repo-native documented counts and clarified that scheduler metadata remains host-side.
• Replaced Data Warehouse front-matter TBD placeholders with concrete repository implementation evidence (aeries-data-warehouse) while keeping rollout validation explicit.

Second extraction wave (targeted)

• Tightened operational-control truth across Integr8r and Integr8r-rebase by documenting global report-mail routing behavior (JB_SendReports -> JB_SendMail) and narrowing unresolved escalation questions to per-job recipient enforcement and host scheduler ownership.
• Strengthened Aeries-to-Google Sheets Reporting Extract Family with explicit Linux runtime-path evidence (/home/bousdtech/repos/...) and clearer statement that alert routing is not implemented inside extract run.sh scripts.
• Reconciled monthly attendance automation tension by updating both BOUSD-MonthlyAttendance-Extract and BOUSD-MonthlyAttendance-Dashboard to frame manual SQL/paste steps as a specific fallback-vs-primary validation target.
• Narrowed ownership follow-ups for BOUSD-PADC-Extract and BOUSD-DataConfDocs-Extract into explicit technical-operator versus business-signoff questions.
• Reduced vague validation language in remaining core runner pages:
  • Mosyle to/from Snipe-IT Asset and Tag Sync
  • APEXLearningAPI
  • GSuiteAPI
  • google-classroom-guardians
  • mssql_query_to_google_sheet
• Tightened governance gaps for:
  • TransTraks Student Export (upload activation decision, destination owner, manual-delivery escalation owner)
  • Aeries Student Groups Maintenance Workflow (per-group-family business owner and approval model).

Host and scheduler normalization wave

• Normalized Atlas runtime host posture with explicit baseline roles:
  • sal-01.bousd.us for most Linux cron-based integrations/automations.
  • saw-01.bousd.us for most Windows Task Scheduler-based integrations/automations, including Integr8r.
• Incorporated Windows scheduler artifact evidence from Integr8r/docs/artifacts/task-scheduler-inventory-20260325-225026.csv into key pages, including explicit Integr8r - Batch, Integr8r - Diff, CCGI, DecisionInsite, SchoolMessenger Absences, and SEIS task presence on SAW-01.
• Updated priority pages to distinguish:
  • technical runtime host/scheduler truth,
  • implementation-repo location,
  • unresolved business ownership/escalation responsibilities.
• Added compact reusable reference page:
  • Runtime Host and Scheduler Reference
• Narrowed major unresolved business-context items by tying them to now-evidenced runtime facts (for example TransTraks and Student Groups batch scheduling context on saw-01, monthly attendance fallback ownership on sal-01 cron path).