Data Architecture & Governance (DAG) — Template (Phase 0→1)

Document Classification: Internal — CHLOM Confidential

Phase: 0 → 1 Version: 0.1

Owner: CrownThrive, LLC

Last Updated: 2025-08-08

Section 1 — Data Sources & Schemas

1.1 Source Inventory (to be populated)

Source IDDomainSystem/ProviderData TypeUpdate CadencePHI/PIIResidencySteward
SRC-PEP-01RiskSanctions/PEP Provider AEntities, watchlistsDailyPII-liteUS/EURisk Ops
SRC-KYC-01IdentityKYC Vendor (Phase 1)Document hashes, decisionsOn demandPIIRegionalCompliance
SRC-INT-01InternalCE Derived FeaturesFeature vectorsRealtimePII-minUSData Eng

1.2 Canonical Schemas (contract-first)

  • Entity:
  • FeatureVector:
  • AegisScore:

Schema Rules

  • All schemas versioned in
  • Backward-compatible changes only on minor versions; breaking changes require new topic/table.

Section 2 — Data Lineage Map

2.1 Lineage Requirements

  • End-to-end lineage captured via OpenLineage events emitted by CE/ZKV and ingestion jobs.
  • Every derived dataset attaches

2.2 Lineage Storage

  • Marquez (or equivalent) for lineage graph; retained 7 years for regulated domains.
  • Immutable snapshots for Feature Groups written to Delta Lake with commit metadata.

Section 3 — Retention & Archival Policies

DatasetHot (days)Warm (months)Cold (years)Deletion PolicyLegal Hold
Feature Store (OLTP)30127TTL by entity_idYes
Audit Events (WORM)7127Never mutateYes
AegisScore Decisions90247Pseudonymize after 24 moYes
  • RPO/RTO Alignment: Retention policies must not violate DR objectives.
  • Right-to-Erasure: Maintain deletion manifests for PII keyed by

Section 4 — Privacy Classifications

4.1 Data Classes

  • Public — Non-sensitive docs, public keys.
  • Internal — Operational metadata.
  • Sensitive — PII-lite, hashed identifiers.
  • Restricted — Full PII, cryptographic material, proof parameters.

4.2 Handling Rules (by Class)

ClassAt RestIn TransitIn UseAccess
PublicStandardTLSN/AAll
InternalAES-256TLSN/ARBAC
SensitiveAES-256 + FPETLS 1.3Trusted enclaves onlyRBAC + JIT
RestrictedHSM/KMS-backedmTLS + TLS 1.3Enclave/TEEBreak-glass + dual control
  • Pseudonymization: Use salted hash (Argon2id) for persistent identifiers; never store raw national IDs.

Section 5 — ZKP Boundaries

  • Public Inputs: Commitments, Merkle roots, policy IDs, non-PII aggregates.
  • Private Inputs: Raw attributes (DOB, document signatures), license secrets.
  • Boundary Rule: Raw PII never leaves ZK prover/verifier enclave; CE only consumes verification boolean + proof metadata.

Artifacts

  • /zk/obsidian/circuits/*
  • /zk/policies/*

Section 6 — Dataset Entitlement & Access Matrix

DatasetRole: CERole: ZKVRole: SRERole: DataEngRole: ComplianceExternal Tenant
Feature Store (OLTP)R/W (scoped)R (subset)R (metrics only)AdminRNone
Delta Lake FeaturesRRR (ops)AdminRNone
Audit WORMAppendAppendRRAdminRead (regulator only)
Model RegistryRRRAdminRNone
  • Enforcement: IAM + row-level policies; all access is logged and correlated with

Section 7 — Data Quality & SLAs

CheckTargetMethodAction on Breach
Freshness (Feature Group)< 5 min lagTimestamp diffAlert SRE; degrade gracefully
Completeness≥ 99.5% non-nulldbt testsBlock promotion
Validity100% schema-conformantSchema registryQuarantine batch
Drift (Key Features)PSI < 0.2 vs baselineDrift jobTrigger retrain RFC

Section 8 — Compliance Controls (Privacy, Residency, DPIA)

  • Residency: Tag records with
  • Consent & Purpose: Persist
  • DPIA: Required for any new PII source; template
  • DLP: Egress scanning on logs and exports; block patterns for sensitive tokens.

Section 9 — Cryptography & Key Rotation

  • At Rest: AES-256-GCM; per-table keys rotated every 180 days.
  • In Transit: TLS 1.3 only; mTLS inside mesh.
  • Identifiers: Tokenize with format-preserving encryption where necessary.
  • Rotation: Keys in KMS with automatic rotation; key IDs versioned in dataset metadata.

Section 10 — Operational Playbooks (Links)

  • /runbooks/feature-freshness-lag.md
  • /runbooks/delta-lake-compaction.md
  • /runbooks/pseudonymization-key-rotation.md

Was this article helpful?

CHLOM License Exchange (LEX) — API & Integration Specification (Phase 3→4)