Project Atlas AetherDev project hub
Atlas project production

Aeries Language Fluency Sync

Runs an internal Aeries write-back workflow to keep language-fluency and related program fields aligned to CALPADS-shaped source values.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-24
Visibility
Internal

Purpose

Maintain Aeries language-fluency and related program fields using CALPADS-aligned values already present in the SIS.

Current state

Active Integr8r and PowerShell write-back path exists, but business approval and scheduler ownership remain under-documented.

Next step

Document cadence, owner approval, and rollback expectations for bulk write-back runs.

Interfaces

Inputs
  • Aeries language-acquisition data
  • CALPADS-aligned source values
  • delta report SQL
Outputs
  • updated Aeries language-fluency and program fields

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes 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 source fields and CALPADS-aligned values drive the intended state.
  • Aeries is both source and destination for this maintenance workflow.

Safe handling

  • Use restricted SQL permissions and controlled write-back access.
  • Treat student program fields and logs as sensitive.

Operational notes

Reliability posture

Write-back flow is well evidenced, but approval, rollback, and cadence still need explicit runbook coverage.

Observability

  • Integr8r logs
  • post-script logs
  • delta report outputs

Security and privacy

Restricted student program data; internal only.

Dependencies

Upstream
  • Aeries source-field accuracy
  • Integr8r scheduler or operator path
  • PowerShell write-back script
Downstream
  • CALPADS and downstream reporting quality

Ownership

Owners

Technology Services

Users

Technology Services, data and compliance stakeholders

Aeries Language Fluency Sync

Operational Notes

  • The registry clarifies that this is an Aeries-to-Aeries maintenance job, not an external vendor sync.
  • Integr8r exports a delta report and then runs Modify-BOUSD-Students-Aeries-EL-Status.ps1.
  • Failure can leave EL-related fields stale or inconsistent for downstream compliance work.

Registry Alignment

  • Mapped registry entry: INT-038
  • Registry clarified: this is a live internal SIS write-back workflow with concrete scripts and CALPADS-shaped field logic.
  • Validation gaps: Confirm operating cadence, business approval, and rollback expectations for bulk changes.