Purpose
Keeps Aeries staff records aligned with OCDE HR data for identity, assignment, and compliance reporting.
Current state
Aether includes legacy `Push-OCDEHRToAeries.sh` logic and the Rust rewrite at `rust/ocdehr_aeries_sync/` with lock files, reporting outputs, and managed tunnel behavior. Registry-backed cron evidence indicates the Rust binary is the active scheduled runtime (:58 hourly from 06:00-18:00), and the Bash script is now explicitly marked retired in-script as replaced by `ocdehr_aeries_sync`.
Next step
Confirm declared production host ownership, write-mode governance, and publish the Rust runtime runbook and escalation ownership.
Interfaces
Inputs- OCDE HR 2.0 staff identity and assignment data.
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesNot in scope.
Operational AdoptionNot in scope.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Data integrity and contracts
Source of truth rules
- OCDE HR 2.0 staff identity and assignment data remain the authoritative upstream inputs for this workflow.
- Aeries staff records are downstream targets and should not be treated as the authoring source.
Safe handling
- Protect credentials, generated files, logs, and any transient export artifacts.
- Limit staff identity, employment, or account data to approved administrators and business owners.
Operational notes
Reliability posture
Rust tracing logs with optional HTML/JSON reports and lock-file support prevent overlapping runs. Failure impact: out-of-date staff records and downstream identity or compliance reporting errors. Manual fallback: manual Aeries updates or manual HR export.
Observability
- Rust tracing logs with optional HTML/JSON reports.
- Runtime lock files prevent overlapping runs.
- Optional HTML/JSON summaries support operator review and exception triage.
Security and privacy
DB credentials and SSH tunnel access; config files should remain protected. Classification: confidential staff identity and employment data. HR data requires restricted handling.
Dependencies
Upstream- OCDE HR DB access, Aeries DB access, SSH tunnel reliability, and SQL template accuracy.
DownstreamOwnership
OwnersTechnology Services with HR, Technology Services
UsersTechnology Services with HR, HR / personnel stakeholders
OCDE HR to Aeries Staff Sync (Rust Active; Legacy Bash Retired)
Operational Notes
- Method: SQL extraction from OCDE HR, match/diff logic, and Aeries updates with optional write mode.
- Implementation: active runtime is Rust binary
rust/ocdehr_aeries_sync/ocdehr_aeries_sync with TOML configs under rust/ocdehr_aeries_sync/config/; legacy retired artifacts include Push-OCDEHRToAeries.sh and related legacy SQL scripts. - Current runtime / active path: Rust binary
rust/ocdehr_aeries_sync/ocdehr_aeries_sync appears to be the active scheduled implementation. - Legacy path status:
Push-OCDEHRToAeries.sh is explicitly marked retired in-script and should be treated as historical reference only. - Trigger / frequency: minute 58, hourly from 06:00-18:00 daily per
docs/cron-example.txt. - Scheduler / operator model: scheduled Rust execution with lock-file guardrails plus operator rerun controls.
- Failure impact / fallback: out-of-date staff records and downstream identity or compliance reporting errors. Manual fallback: manual Aeries updates or manual HR export.
- Related references:
Push-OCDEHRToAeries.sh, rust/ocdehr_aeries_sync/README.md. - Related Atlas pages: aeries staff extract sql
Registry Alignment
- Mapped registry entry:
INT-070 - Registry clarified:
ocdehr_aeries_sync is the active runtime and Push-OCDEHRToAeries.sh is a retired legacy reference. - Validation gaps: write-mode governance, production host ownership, and runbook/escalation documentation are still not fully documented.
