Script-first operational toolbox spanning SIS, Google Workspace, identity, asset, and reporting workflows through shared shell libraries, config packs, SQL sources, and per-workflow entry scripts.
Provide a practical integration toolbox for recurring district automation workflows where script-first execution remains the fastest operational fit.
Active with broad implementation evidence and refreshed repo-level documentation from the current workbench pass. Host/scheduler normalization now treats this repository as the primary Linux automation layer on `sal-01.bousd.us` for many cron-driven workflows, while Windows Task Scheduler-centric runner jobs remain primarily in Integr8r on `saw-01.bousd.us`.
Map active production entrypoints to explicit run schedules, owners, and host assignment (`sal-01` default versus exceptions), then split stable workflow families into tighter runbooks/playbooks.
Contributes in this stage.
Not in scope.
Contributes in this stage.
Contributes in this stage.
Contributes in this stage.
TBD. Document the 5-10 steps that define the core workflow.
High utility and broad coverage, but behavior varies by script. Host normalization now places most Linux script-scheduled workloads on `sal-01.bousd.us`, while Windows runner workloads remain centered on `saw-01.bousd.us` via Integr8r. Safe operation still depends on workflow-specific validation and ownership discipline.
Repository handles sensitive operational integrations. Keep credentials outside source control and treat generated data/log artifacts as restricted where they contain PII or privileged context.
Josh Barton
UsersTechnology Services, Operations maintainers
aether acts as a script toolbox rather than a single service. Each workflow has its own entrypoint and dependency chain.
sal-01 cron, saw-01 Task Scheduler, or manual).