Project Atlas AetherDev project hub
Atlas project production

Integr8r-rebase

PowerShell integration runner repository with a broad BOUSD integration catalog, executable config loading, SQL/export orchestration, and report-mailer subsystems.

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

Purpose

Provide a centralized runner and configuration catalog for BOUSD integration workflows spanning SIS, identity, vendor exports, and operational reporting.

Current state

Code-level evidence strongly indicates production-grade runtime capability. Like Integr8r, this repo has end-of-run summary mail logic (`JB_SendReports` -> `JB_SendMail`) tied to global mail settings, while per-integration `AdditionalMailTo` entries appear in config but not in active send logic. Host normalization now points Windows runner execution to `saw-01.bousd.us`; current scheduler artifact evidence shows live tasks invoking `C:\Integr8r\Integr8r.ps1`, not an `Integr8r-rebase` path. Active production invocation from this repo is therefore not currently evidenced, and Atlas treats it as implementation catalog/variant until host-side task evidence says otherwise.

Next step

Classify this repo explicitly as active runtime, mirror, staged successor, or dormant variant relative to `Integr8r`, then document any `saw-01` scheduler entries that execute `Integr8r-rebase` paths if they exist.

Interfaces

Inputs
  • Config/*.ps1 definitions
  • SQL source systems
  • Vendor/API transport settings
Outputs
  • Integration files/exports
  • SQL update actions
  • Email report artifacts
  • Logs

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Artifacts

  • Config/Config.ps1 integration catalog
  • Integration folder SQL files
  • Reports subsystem templates/scripts

Operational notes

Constraints and scars

  • Executable config means small edits can produce high-impact runtime changes.
  • Large integration surface area increases maintenance and validation burden.

Reliability posture

Runner architecture is mature but high risk due to executable config and broad blast radius. Changes require careful validation.

Observability

  • PowerShell log output
  • Per-integration report data
  • Report mailer artifacts

Security and privacy

Contains sensitive operational integration definitions. Protect credentials and treat generated outputs as restricted student/staff operational data where applicable.

Dependencies

Upstream
  • District SQL data sources
  • Vendor endpoints
  • Runtime host modules and tools
Downstream
  • Rostering
  • identity workflows
  • vendor imports
  • district reporting operations

Ownership

Owners

Josh Barton

Users

Technology Services, Data and integration operators

Integr8r-rebase

Runtime Shape

  • Integr8r.ps1 starts the runner.
  • Modules/PSConfigModule.psm1 imports all Config/*.ps1 files.
  • Integration definitions drive SQL/export/command/report phases.
  • Modules/JB_Function_Library.psm1 sends summary email through global MailTo settings; per-job mail-recipient overrides still need validation.

Relationship To Other Runners

  • Integr8r remains the legacy-reference runner entry in Atlas.
  • This rebase repository carries comparable runner structure with substantial active configuration evidence.
  • Host/scheduler normalization currently favors Integr8r as the evidenced saw-01 runtime path; this repo remains runtime-adjacent until direct scheduler/manual invocation evidence is documented.

Validation Needed

  • Final relationship to Integr8r (active mirror, staged successor, partial overlap, or dormant variant) now that scheduler evidence is tied to C:\\Integr8r\\Integr8r.ps1 tasks on saw-01.bousd.us.
  • Any host task entries that execute Integr8r-rebase directly (none evidenced in current task-scheduler-inventory-*.csv artifact snapshot).
  • Per-job escalation routing if AdditionalMailTo remains metadata-only in current code paths (tracked in the Lifecycle Decision Queue).