Project Atlas AetherDev project hub
Atlas project production

Integr8r

Legacy Windows production runner for BOUSD integration jobs, including SQL exports, file transfers, write-back workflows, and report mailers.

Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Public

Purpose

Provide the current legacy production orchestration layer for many BOUSD integrations while modernization paths are validated.

Current state

Repo-native docs now provide stronger inventory evidence: `docs/integr8r-job-reference.md` records 38 configured runner jobs as of March 23, 2026 (25 enabled, 13 disabled/dormant) plus a separate `Reports/` subsystem. Integr8r remains the strongest production runtime evidence layer for many legacy workflows, including Clever, SEIS, TitanHST, and multiple SIS/vendor exchanges. Host scheduler evidence is now available: `docs/artifacts/task-scheduler-inventory-20260325-225026.csv` (ComputerName `SAW-01`) shows active Task Scheduler entries invoking `C:\Integr8r\Integr8r.ps1`, including `Integr8r - Batch`, `Integr8r - Diff`, and job-specific tasks (`CCGI`, `DecisionInsite`, `SchoolMessenger Absences`, `SEIS`). Notification behavior is partly evidenced in code: end-of-run reporting is sent through `JB_SendReports`/`JB_SendMail` using global mail settings; per-job `AdditionalMailTo` fields are present in config but are not referenced by current module code.

Next step

Continue scheduled host evidence exports and reconcile unresolved technical operator/business sign-off/fallback/escalation fields through the [Owner, Escalation, and Fallback Matrix](../owner-escalation-and-fallback-matrix/), including per-job successor-runtime boundaries.

Interfaces

Inputs
  • Config/Config.ps1 job definitions
  • SQL queries
  • source DB connections
  • vendor transfer credentials
  • module scripts
Outputs
  • CSV or tab-delimited exports
  • vendor uploads
  • Aeries or directory write-backs
  • report emails and artifacts

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

  • Config/Config.ps1 is the authoritative runner inventory for Integr8r-hosted workflows.
  • Enabled job definitions indicate supported runtime paths but do not alone prove scheduler cadence or business ownership.

Safe handling

  • Do not publish credentials or key material from config files.
  • Treat generated exports and report artifacts as restricted operational data.
  • Document ownership and recovery procedures for each high-impact job family.

Operational notes

Reliability posture

Production-capable with mature guardrails (batch flags, diff mode, minimum-line checks, report artifacts) and strong in-repo job inventory documentation. Host association is now explicit (`saw-01.bousd.us` for Integr8r/Windows workloads), and alerting is partially evidenced (`JB_SendReports` -> `JB_SendMail` to global `MailTo`), while per-job escalation routing remains external to git.

Observability

  • `logs/main.log` and module-specific logs
  • ReportDetails-driven email/report output
  • artifact files under integration directories
  • separate `Reports/` subsystem artifacts

Security and privacy

Contains restricted student and staff data paths and host-managed credentials; configs, generated files, and report artifacts must remain internal.

Dependencies

Upstream
  • Aeries and HR source systems
  • vendor transfer/API endpoints
  • Windows host scheduling and credentials

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services operators, integration maintainers

Integr8r

Operational Notes

  • Core execution model: Config/Config.ps1 defines per-job options (enabled state, batch mode, diff flags, SQL/file contracts, transfer settings, and optional pre/post commands), and Integr8r.ps1 executes those jobs on the Windows host.
  • Repo-native operations docs (docs/integr8r-job-reference.md, docs/integr8r-active-vs-legacy-map.md, docs/integr8r-high-risk-runbooks.md) now provide stronger classification of active vs dormant jobs and high-risk runbook context.
  • Alert-routing evidence is now clearer: JB_SendReports sends end-of-run summary mail through JB_SendMail, which uses global MailTo and SMTP settings from Config/Config.ps1.
  • Per-job ReportDetails.AdditionalMailTo is widely populated in config, but current module search only finds those keys in config (not in active send logic), so per-job recipient routing still requires host/operator validation.
  • Runtime role in the workbench: this is the legacy production runner layer; adjacent repositories provide documentation (aether-atlas), Linux wrappers (aether), and modernization candidates (titanhst_sync, google-groups-guard, aether-integr8r).
  • Current inventory highlights from repo docs include enabled jobs for Clever, TitanHST, HMH, Hero, SEIS, and TransTraks, alongside disabled historical jobs preserved for continuity.
  • Runtime host normalization: saw-01.bousd.us is the primary Windows host for Integr8r and related Windows-based automations.
  • Task Scheduler evidence now exists in-repo (docs/artifacts/task-scheduler-inventory-20260325-225026.csv) and confirms multiple live Integr8r task entries on SAW-01.
  • Evidence scope caveat: current CSV snapshot is not a full lifecycle/governance map for every job key; task presence is now proven, while ownership/escalation and complete coverage still need maintained exports and reconciliation.
  • Governance note: unresolved role assignments are now tracked in the Owner, Escalation, and Fallback Matrix.

Registry Alignment

  • Mapped registry scope: primary runtime evidence layer across INT-009 through INT-069, plus INT-079 through INT-084 where applicable.
  • Registry clarified that Integr8r remains operationally important even as newer component repos evolve.
  • Validation gaps: per-job escalation recipient map (including whether AdditionalMailTo is actually enforced), full scheduler coverage across all Integr8r job keys (including disabled/hidden/manual-helper paths), and successor-runtime cutover boundaries remain open; unresolved owner/sign-off/fallback/escalation fields are tracked in the Owner, Escalation, and Fallback Matrix.