ai-enabled-hr-talent-automation

Data Architecture

Title: Data Architecture Version: 1.1 Owner: [TENANT_CONFIGURATION_REQUIRED — Data Architecture] Status: Draft (domain-separation model still valid; engine choice now fixed — see notice) Last reviewed: 2026-09-08 Next review: [TENANT_CONFIGURATION_REQUIRED] Reviewers: Architecture, Security, DBA

Implementation reality notice (2026-09-08): the transactional/document/vector data-domain separation below is still the real direction and matches what’s implemented. The engine choice originally left open (see “Assumptions and dependencies”) is now fixed: the real database is SQL Server, HrAutomationDb, implemented database-first at src/HrAutomation.Infrastructure/Database/scripts/, not the flat Postgres-style sample in sample-relational-schema.sql/data-dictionary.md. Object storage and vector-store integration described below have not been implemented yet (Planned).

Purpose and scope

Defines the separation of data domains, storage technologies, and data-flow boundaries. This is a technical baseline requiring DBA/security review before implementation — see sample-relational-schema.sql header.

Data domain separation

flowchart TB
    subgraph Transactional [Transactional HR Data - RDBMS, system of record]
        T1[Tenants/Users/Roles reference]
        T2[Candidates/CV metadata]
        T3[TAN/JD versions]
        T4[Applications/Match scores]
        T5[Interviews/Feedback]
        T6[Offers/Green Form]
        T7[Documents metadata/Verification/Discrepancies]
        T8[Approvals/Workflow transitions]
        T9[Employee master/Employee ID registry]
        T10[Integration outbox]
    end
    subgraph Documents [Document Store - Object Storage]
        D1[Raw CVs]
        D2[Offer letters]
        D3[Green Form uploads]
    end
    subgraph Embeddings [Vector Store - approved retrieval content only]
        V1[Policy/process document chunks]
        V2[JD reference material]
    end
    subgraph Logs [Audit & Telemetry]
        L1[Audit log - RDBMS, append-only]
        L2[Traces/metrics/logs - observability backend]
    end
    subgraph Analytics [De-identified Evaluation / Analytics]
        AN1[AI evaluation datasets]
        AN2[Reporting read-models]
    end

    T2 -. blob ref .-> D1
    T6 -. blob ref .-> D2
    T7 -. blob ref .-> D3
    T3 -. source doc .-> V2
    T8 --> L1

Separation principles

Domain Storage Authoritative for Never used as authoritative for
Transactional HR data Relational DB Workflow status, approvals, offers, employee records —
Documents Object storage Raw file bytes Any structured field (structured data lives in RDBMS, referencing the blob)
Embeddings Vector store Retrieval ranking for RAG Workflow status, approvals, offers, employee records (ADR-003)
Audit/telemetry RDBMS (audit log) + observability backend (traces/metrics) Historical record of actions and system behavior Live query path for application logic
Analytics/evaluation Read-model / analytics store, de-identified Reporting, AI evaluation Any live workflow decision

Data flow: CV to CV Bank

  1. Recruiter uploads CV → Document Service stores raw file in object storage, emits candidate.cv_uploaded.
  2. Agent Plane parses file (async), extracts structured fields, returns JSON-Schema-validated result.
  3. HR Core API writes structured candidate/CV metadata to RDBMS (with blob reference), runs dedup rules, emits candidate.cv_parsed.
  4. Low-confidence extractions route to a manual-review queue (never silently auto-accepted).

Retention and deletion

See data-classification-and-retention.md for retention periods and the deletion/legal-hold workflow.

Assumptions and dependencies

Originally scoped as a per-tenant choice between Postgres or SQL Server; the real implementation fixed this to SQL Server (HrAutomationDb), not a runtime/tenant-configurable choice — see the implementation notice above. Assumes one object-storage provider per tenant; multi-provider-per-tenant is out of scope for v1.

Risks and open questions

Change control

Version Date Author Change
1.0 2026-09-07 Documentation package generation Initial creation
This site is open source. Improve this page.