Verify Canonical Build

This section explains the exact steps L2 teams use to verify whether Canonical (UDS) is structurally and functionally ready after installation. The goal is not data validation — only platform readiness validation

Structural Verification (LDZ → ANP → RDV → BDV → 360)

Canonical is installed by deploying an image that lays down all DDLs. Verification is done by describing entities created in the installation process.

Verification Method

For each layer, L2 performs DESC checks (schema-level only), for example: 
SQL> DESC LDZ_<entity>;
SQL> DESC ANP_<entity>;
SQL> DESC RDV_<entity>;
SQL> DESC BDV_<entity>;
SQL> DESC C360_<entity>;

Expected validation outcomes:

  • Entity exists
  • Columns match the Redbook structure
  • Data types are correct
  • Mandatory fields exist
  • Surrogate keys/audit fields exist where expected

If all entities across layers respond correctly to DESC, Canonical structure is considered deployed successfully.

Functional Verification (Pipeline Flow Validation)

Once structure exists, we verify whether Canonical can move data through the layers correctly. This can be done using a small synthetic dataset in LDZ.

Checks L2 performs

  1. Load a tiny, known dataset into LDZ.
  2. Run ETL DAG pipelines end-to-end.
  3. Confirm record presence in ANP, RDV, BDV, and 360.
  4. Validate pass-through integrity using counts:
    • If 10 Parties in LDZ, 10 Parties appear in C360.
    • If 50 Transactions in LDZ, 50 appear in C360.
    Attention: Do a referential spot-check:
    • For a record in ldz_account_party, check whether the partyid exists in ldz_party_demographic and acct_id exists in corresponding type of account detail table (i.e. CASA in ldz_account_dtl, LOAN in ldz_loan_dtl, CREDITCARD in ldz_creditcard_dtl and DEPOSIT in ldz_deposit_dtl).
    • For a record in ldz_acct_party_trans, check whether the partyid exists in ldz_party_demographic and acct_id exists in corresponding type of account detail table (i.e. CASA in ldz_account_dtl, LOAN in ldz_loan_dtl, CREDITCARD in ldz_creditcard_dtl and DEPOSIT in ldz_deposit_dtl).
    • Campaign ↔ Flowchart ↔ Cells

    If LDZ → 360 flow works, the Canonical installation is verified.

What Successful Build Means

Canonical installation is considered successful when:

  • All schema entities exist and match design
  • No missing or misnamed entities
  • DAG pipelines execute without exceptions
  • LDZ → ANP → RDV → BDV → 360 propagation works
  • Counts reconcile end-to-end
  • Basic referential integrity holds