Project Atlas AetherDev project hub
Atlas project production

Runtime Host and Scheduler Reference

Compact reference for current production host roles, scheduler split, and evidence boundaries across Linux cron and Windows Task Scheduler integration workloads.

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

Purpose

Provide one durable host/scheduler baseline so Atlas pages can reference consistent runtime truth and reserve validation notes for unresolved ownership/process questions.

Current state

Host normalization baseline is now explicit: `sal-01.bousd.us` is primary for Linux cron-based integrations/automations, and `saw-01.bousd.us` is primary for Windows Task Scheduler-based integrations/automations including Integr8r. Current Task Scheduler artifact evidence confirms Integr8r task presence on `saw-01`. Ownership/escalation/fallback role tracking now lives in the dedicated matrix page.

Next step

Maintain periodic scheduler exports and annotate exceptions where a workflow does not follow the default `sal-01` (Linux) or `saw-01` (Windows/Integr8r) host role.

Interfaces

Inputs
  • host normalization decisions
  • scheduler inventory artifacts
  • repo runtime docs (`aether/docs/cron-example.txt`, Integr8r docs)
Outputs
  • host-role reference
  • scheduler evidence baseline
  • validation boundary guidance

Reality to Action trace

Reality Ingestion

Not in scope.

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

  • Host-role normalization (`sal-01` Linux, `saw-01` Windows/Integr8r) is the baseline runtime model unless stronger per-workflow evidence contradicts it.
  • Scheduler artifacts prove task presence and command path at capture time, not full business ownership or complete operational coverage.

Safe handling

  • Do not publish credentials, secret paths, or full sensitive command payloads.
  • Keep host and scheduler metadata internal to approved operational documentation.

Operational notes

Reliability posture

Strong enough for runtime normalization baseline, but still a documentation layer: scheduler snapshots and host-role statements do not by themselves prove business ownership or complete task coverage.

Observability

  • Task Scheduler CSV artifacts under Integr8r docs/artifacts
  • Linux cron path evidence in `aether/docs/cron-example.txt`

Security and privacy

Host names and task metadata are operationally sensitive internal details; keep this reference internal.

Dependencies

Upstream
  • production host inventory updates
  • scheduler export refreshes
Downstream
  • Atlas project runtime notes
  • ownership/escalation runbook reconciliation

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, integration maintainers

Runtime Host and Scheduler Reference

Baseline Host Roles

HostPlatformPrimary roleStrongest evidence
sal-01.bousd.usLinuxPrimary runtime host for most Linux-based integration wrappers and extract automations (cron model).Host normalization decision + cron-path evidence in aether/docs/cron-example.txt (/home/bousdtech/repos/...).
saw-01.bousd.usWindowsPrimary runtime host for most Windows-based integrations and automations, including Integr8r runner workloads.Host normalization decision + Task Scheduler artifact evidence in Integr8r/docs/artifacts/task-scheduler-inventory-*.csv.

Scheduler Split (Current Baseline)

  • Linux-oriented wrappers/extracts: cron-driven pattern, primarily on sal-01.
  • Windows runner workloads: Task Scheduler-driven pattern, primarily on saw-01.
  • Integr8r association: Task Scheduler artifact confirms tasks invoking C:\Integr8r\Integr8r.ps1 on SAW-01.
  • Fallback boundary rule: manual methods documented in workflow pages should be treated as outage/exception fallback paths unless scheduler evidence proves they are primary.

Current Task Scheduler Artifact Snapshot

  • Artifact path: Integr8r/docs/artifacts/task-scheduler-inventory-20260325-225026.csv
  • Capture host evidence: ComputerName = SAW-01 for all rows.
  • Evidenced Integr8r tasks include:
    • Integr8r - Batch
    • Integr8r - Diff
    • Integr8r - CCGI
    • Integr8r - DecisionInsite
    • Integr8r - SchoolMessenger Absences
    • Integr8r - SEIS
  • Snapshot limitation: this capture is a point-in-time artifact and not a complete governance map for all job keys, disabled tasks, or manual-helper invocation policy.
  • Governance note: use this page for runtime truth and the Owner, Escalation, and Fallback Matrix for owner/sign-off/fallback/escalation role closure.

Example Workflow Families by Host Role

  • Primarily sal-01 (Linux cron): Aeries-to-Google Sheets extract family, Mosyle/Snipe-IT wrapper syncs, other aether cron-documented wrappers.
  • Primarily saw-01 (Windows Task Scheduler): Integr8r runner batch/diff and scheduled Integr8r job invocations.

What Is Still Validation-Needed

  • Per-workflow business owner, backup owner, and escalation ladder.
  • Alert-routing destinations and incident response ownership by workflow family.
  • Full scheduler coverage reconciliation (disabled/hidden/manual paths and exception hosts).
  • Explicit exception mapping for workflows that do not follow the baseline host-role split.
  • Per-workflow fallback trigger conditions, named fallback operator, and outage-only vs exception-only policy.