Atlas project production

Owner, Escalation, and Fallback Matrix

Compact cross-workflow matrix tracking technical operators, business sign-off ownership, fallback operators, escalation ownership, and remaining human-confirmation targets.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-26
Visibility: Internal

Purpose

Provide one durable structure for ownership, escalation, and fallback decisions so unresolved human confirmations are explicit and easy to close.

Current state

Runtime host and scheduler truths are now largely stabilized (`sal-01` Linux cron, `saw-01` Windows Task Scheduler/Integr8r). The remaining work is ownership, escalation, fallback authority, and final lifecycle classification.

Next step

Use this matrix as the canonical reconciliation layer during owner/escalation validation sessions; then update each workflow page with confirmed values.

Interfaces

Inputs

runtime host and scheduler evidence
workflow project pages

Outputs

owner/escalation/fallback matrix
structured human-validation queue

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

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

Do not infer business ownership from runtime host evidence alone.
Use explicit certainty labels: `confirmed`, `likely`, `unresolved`.

Safe handling

Keep internal names and escalation metadata in approved internal docs only.

Operational notes

Reliability posture

Runtime host/scheduler fields are often strongly evidenced; business sign-off, fallback executor, and escalation ownership are intentionally marked with explicit certainty labels.

Observability

Matrix row updates across Atlas workflow pages

Security and privacy

Contains internal operational ownership and escalation metadata; keep internal.

Dependencies

Upstream

runtime-host-and-scheduler-reference
workflow project runtime notes

Downstream

runbook completion
ownership confirmation updates

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, report and workflow owners

Owner, Escalation, and Fallback Matrix

Certainty Labels

confirmed: directly evidenced in code/config/scheduler artifacts or explicitly documented in Atlas.
likely: strong technical signal exists, but business/governance confirmation is not complete.
unresolved: no durable evidence yet; requires human confirmation.

Ownership-Gap Inventory (Current Pass)

Workflow family	Current technical evidence	Missing piece type(s)	Key unresolved question
Aeries-to-Google Sheets Reporting Extract Family	`sal-01` Linux cron model and per-feed contracts are evidenced.	business owner, sign-off owner, fallback executor, escalation owner	Which owner/sign-off/escalation roles apply per extract feed?
MonthlyAttendance + Dashboard	Automated extract path is primary; manual SQL/paste is legacy fallback/reference.	fallback executor, sign-off owner, escalation owner	What exact incident threshold triggers fallback, who approves it, and who notifies consumers?
BOUSD-PADC-Extract	`sal-01` cron runtime and tab contracts are evidenced.	sign-off owner, fallback executor, escalation owner	Who owns certification sign-off and incident escalation during certification windows?
BOUSD-DataConfDocs-Extract	`sal-01` cron runtime and destination contract are evidenced.	business owner, sign-off owner, fallback executor, escalation owner	Which team accepts output quality and who executes fallback when runtime fails?
TransTraks Student Export	Integr8r batch scheduling on `saw-01` likely covers enabled export generation.	business owner, sign-off owner, fallback executor, escalation owner	While upload is disabled, who owns manual delivery approval and escalation?
Aeries Student Groups Maintenance Workflow	Integr8r batch execution on `saw-01` is evidenced.	business owner, sign-off owner, fallback executor, escalation owner	Who approves criteria changes and manual corrections by group family (SPED/GATE/ENR/IMM)?
google-classroom-guardians	CLI implementation/wrapper exists, but no current scheduler evidence on `saw-01` or `aether` cron example.	technical operator, business owner, escalation owner	What is the active trigger path and who owns invite-failure escalation/sign-off?
Perpetual Data Reports Portal	Cross-family runtime baseline is clear (`sal-01` + `saw-01`).	business owner, fallback executor, escalation owner	Can report-family ownership and escalation be published in one inventory?
Integr8r Windows runner family	Task Scheduler artifact confirms live `C:\Integr8r\Integr8r.ps1` tasks on `saw-01`.	business owner, sign-off owner, escalation owner	Which per-job business owners and escalation routes are authoritative?
Linux cron extract family on `sal-01`	`aether/docs/cron-example.txt` shows cron-run extract wrappers on Linux paths.	business owner, fallback executor, escalation owner	Which owner/escalation contacts map to each cron feed?

Workflow Matrix

Workflow family / page	Primary technical runtime/operator	Primary runtime host	Scheduling model	Business sign-off owner	Fallback path	Fallback operator	Escalation owner	Current certainty	Validation still needed
Aeries-to-Google Sheets Reporting Extract Family	Technology Services extract operations (`likely`)	`sal-01.bousd.us` (`confirmed`)	Linux cron (`confirmed`)	`unresolved` (varies by feed)	Per-feed manual contingency (`likely`)	`unresolved`	`unresolved`	Runtime `confirmed`; ownership `unresolved`	Per-feed business sign-off, fallback executor, escalation ladder, credential custodian
BOUSD-MonthlyAttendance-Extract + BOUSD-MonthlyAttendance-Dashboard	Extract operator in Technology Services (`likely`)	`sal-01` extract + Google-hosted dashboard runtime (`confirmed`)	Hourly Linux cron extract + on-demand dashboard (`confirmed`)	`unresolved`	Manual SQL/paste legacy fallback/reference (`confirmed` as fallback status)	`unresolved`	`unresolved`	Primary/fallback status `confirmed`; owner roles `unresolved`	Trigger threshold, fallback executor, fallback approver, consumer notification, automation-resume handoff
BOUSD-PADC-Extract	Technology Services extract operator (`likely`)	`sal-01.bousd.us` (`confirmed`)	Linux cron every 30 minutes (`confirmed`)	`unresolved`	Manual rerun/check process during failures (`likely`)	`unresolved`	`unresolved`	Runtime `confirmed`; certification governance `unresolved`	Certification sign-off owner, escalation owner, backup/fallback operator
BOUSD-DataConfDocs-Extract	Technology Services extract operator (`likely`)	`sal-01.bousd.us` (`confirmed`)	Linux cron every 15 minutes weekdays (`confirmed`)	`unresolved`	Manual check/rerun when extract fails (`likely`)	`unresolved`	`unresolved`	Runtime `confirmed`; consumer governance `unresolved`	Consuming workflow owner, sign-off authority, fallback executor, escalation ladder
TransTraks Student Export	Integr8r batch operator (`likely`)	`saw-01.bousd.us` (`confirmed`)	Task Scheduler `Integr8r - Batch` likely covers job (`likely`)	`unresolved`	Manual delivery while `UploadData = $False` (`likely`)	`unresolved`	`unresolved`	Generation path `likely/confirmed`; delivery governance `unresolved`	Destination owner, upload activation authority, approved transfer method, manual delivery escalation
Aeries Student Groups Maintenance Workflow	Integr8r SqlExec batch operator (`likely`)	`saw-01.bousd.us` (`confirmed`)	Task Scheduler `Integr8r - Batch` likely includes job (`likely`)	`unresolved` (family-specific)	Direct manual Aeries group maintenance (`likely`)	`unresolved`	`unresolved`	Runtime `likely/confirmed`; group governance `unresolved`	Owner/approval map by SPED/GATE/ENR/IMM group families and manual-correction escalation
google-classroom-guardians	Technology Services operator (`likely`)	`unresolved`	`unresolved` (manual or alternate scheduler)	`unresolved`	Manual exception handling for invite/contact issues (`likely`)	`unresolved`	`unresolved`	CLI behavior `confirmed`; trigger/ownership `unresolved`	Active trigger path, runtime owner, escalation owner, business sign-off owner, mode-approval authority
Perpetual Data Reports Portal	Distributed operators across extract and runner families (`likely`)	`sal-01` + `saw-01` baseline (`confirmed`)	Mixed Linux cron + Windows Task Scheduler (`confirmed`)	`unresolved` per report family	Family-specific contingency (`likely`)	`unresolved` per family	`unresolved` per family	Platform baseline `confirmed`; report governance `unresolved`	Publish owner/sign-off/fallback/escalation fields per report family
Integr8r Windows runner family	Integr8r operators in Technology Services (`likely`)	`saw-01.bousd.us` (`confirmed`)	Task Scheduler (`confirmed`)	`unresolved` per job	Manual rerun/helper execution (`likely`)	Technology Services (`likely`)	`unresolved` (global mail exists; per-job routing unclear)	Host/task evidence `confirmed`; owner map `unresolved`	Per-job business owner, escalation owner, and `AdditionalMailTo` enforcement confirmation
Linux cron extract family baseline	Technology Services Linux extract operators (`likely`)	`sal-01.bousd.us` (`confirmed`)	Linux cron (`confirmed`)	`unresolved` per feed	Manual rerun/manual data check (`likely`)	`unresolved` per feed	`unresolved` per feed	Runtime baseline `confirmed`; governance `unresolved`	Feed-level owner/sign-off/fallback/escalation map and exception host reconciliation