Project Atlas AetherDev project hub
Atlas project production

Aeries Staff Extract SQL Generator

Provide the canonical staff extract logic feeding BOUSD refresh, reporting, and operational planning workflows.

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

Purpose

Give downstream BOUSD reporting and refresh workflows a shared staff extract contract instead of multiple slightly different local queries.

Current state

The registry now makes this page more important than a query-design note. It is a live upstream dependency for staff/device reporting and refresh workflows, but the formal published contract is still missing.

Next step

Publish a versioned contract with column definitions, cadence, live consumers, and validation queries so downstream Atlas pages can reference one canonical output.

Interfaces

Inputs
  • Aeries staff, section, and room-association tables
  • term and date-window parameters
Outputs
  • canonical staff datasets
  • room and site associations
  • downstream CSV or staging outputs

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Contributes in this stage.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

Core workflow

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

Data integrity and contracts

Source of truth rules

  • Aeries remains canonical for staff identity and assignment data.
  • This SQL layer defines the operational extract view consumed by downstream reporting and device workflows.

Safe handling

  • Use read-only SQL access for extract generation.
  • Restrict downstream copies of staff extracts.
  • Document consumer dependencies before changing columns or join logic.

Operational notes

Reliability posture

The SQL itself is deterministic, but the missing versioned contract leaves downstream consumers vulnerable to silent schema drift.

Observability

  • row-count checks
  • consumer-side mismatch detection
  • validation queries run by maintainers

Security and privacy

Staff identity and assignment data are confidential and should be handled with read-only DB access and restricted downstream distribution.

Dependencies

Upstream
  • Aeries schema stability
  • query governance
  • read-only SQL access
Downstream
  • BOUSD-Staff-Technology-Dashboard
  • Staff Device Refresh Operations Portal
  • Perpetual Data Reports Portal

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, downstream reporting and automation maintainers

Aeries Staff Extract SQL Generator

Operational Notes

  • The extract is the shared upstream dependency behind the staff technology dashboard, refresh portal, and broader reporting workflows. The registry now treats it as a live contract dependency, not just a useful query note.
  • The strongest Atlas improvement here is boundary clarity: downstream dashboards should not each infer the schema independently. A versioned output contract is now the missing governance layer.
  • This page is also relevant to the Perpetual Data Reports Portal because staff-device readiness reporting depends on the same upstream field definitions and cadence expectations.

Registry Alignment

  • Mapped registry entry: INT-032.
  • Registry clarified: this is a live upstream dependency, not a SQL sandbox page.
  • Validation gaps: scheduler location, versioned contract, consumer inventory, and change-control rules for downstream consumers still need publication.