Project Atlas AetherDev project hub
Atlas project concept

TitanHST Integration Connector

Prove the Aether Integrator architecture with a connector that matters operationally. It ingests Aeries + HR 2.0 source truth; TitanHST API (details pending) and produces synced TitanHST records; audit logs; job statuses.

Playbook available

Operational guidance is available for this system.

Open playbook
Type
System
Lifecycle
Idea
Last touched
2026-03-26
Visibility
Public
Why it's showcased

Highlights the first connector intended to prove the Aether Integrator architecture in a high-impact operational workflow.

Purpose

Prove the Aether Integrator architecture with a connector that matters operationally.

Current state

Concept and intent remain valid for the Aether Integrator roadmap, but this connector is not the currently deployed TitanHST production runtime. Registry-backed evidence still points to Integr8r as the active production path and `titanhst_sync` as the nearer modernization implementation.

Next step

Write the record-mapping contract, migration criteria, and runtime declaration that explicitly defines when this connector would supersede or coexist with current Integr8r and `titanhst_sync` paths.

Interfaces

Inputs
  • Aeries + HR 2.0 source truth
  • TitanHST API (details pending)
Outputs
  • synced TitanHST records
  • audit logs
  • job statuses

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

  1. Define TitanHST API contract and mapping tables.
  2. Pull staff and HR truth data from Aeries/HR exports.
  3. Normalize identities, positions, and site assignments.
  4. Map to TitanHST fields and required codes.
  5. Diff against TitanHST records to compute changes.
  6. Apply creates, updates, and deactivations.
  7. Emit audit logs, exception lists, and summary counts.

Data integrity and contracts

Canonical schema definitions

  • Staff roster schema from Aeries/HR (IDs, roles, sites).
  • TitanHST user/job payload schema.
  • Mapping tables for departments, locations, and job codes.
  • Audit report schema for adds, updates, and removals.

Source of truth rules

  • Aeries/HR is canonical for staff identity and assignments.
  • Mapping tables define authoritative translations to TitanHST codes.
  • TitanHST is treated as target state and updated to match source.

Data quality checks

  • Validate required IDs/emails and active status fields.
  • Ensure mapping coverage for all departments and sites.
  • Verify TitanHST API responses and error codes.
  • Generate exception lists for missing or mismatched data.

Safe handling

  • Protect PII in exports and logs.
  • Restrict TitanHST API tokens and rotate on schedule.
  • Limit access to audit artifacts.

Downstream integration map

  • TitanHST platform records.
  • Integration audit reporting.
  • Aether Integrator job history.

Operational notes

Reliability posture

Must be idempotent with diff/apply and audit.

Observability

  • job logs
  • connector-level metrics (recommended)

Security and privacy

PII and potentially financial/benefit-adjacent data.

Dependencies

Upstream
  • Aeries/HR exports
  • Aether Integrator kernel
Downstream
  • TitanHST platform state

Ownership

Owners

Josh Barton

Users

IT, business ops (indirect), Josh Barton (owner)

TitanHST Integration Connector

Registry Alignment

  • Related registry entry: INT-016.
  • The registry reinforces that this page represents the future Aether Integrator connector direction, not the currently confirmed production runtime.
  • Current production runtime: Integr8r TitanHST job with SQL export and secure upload path.
  • Parallel modernization runtime: titanhst_sync, with cutover still unresolved.
  • Validation gaps still open: production scheduler ownership, destination contract naming, and explicit migration criteria before this connector can become active.

Related playbooks