Try dbt on CoreModels

import_vendor_project
  vendor:   dbt
  manifest: manifest.json   (jaffle_shop, dbt 1.4.1)
  catalog:  catalog.json

• customers · customer_id, first_name, last_name, first_order, most_recent_order, number_of_orders, total_order_amount
• orders · order_id, customer_id, order_date, status, amount, credit_card_amount, coupon_amount, bank_transfer_amount, gift_card_amount
• stg_customers · customer_id
• stg_orders · order_id, status
• stg_payments · payment_id, payment_method

One note from the import: model.jaffle_shop.customers.total_order_amount has no declared type in the sample. CoreModels stored it as String and kept the original in the vendor metadata.

Result: real output of import_vendor_project. The list of models and columns is read from the sample manifest.

audit_vendor_project
  vendor:   dbt
  manifest: manifest.json   (pull request version)
  catalog:  catalog.json    (pull request version)

• Coverage · Info

  field-unmapped on model.jaffle_shop.stg_payments.method

  Field is not represented on the governed dataset (added since the last import).

• Drift · Error

  field-removed on model.jaffle_shop.stg_payments.payment_method

  Field is governed in CoreModels but no longer exists on the estate dataset.

The same audit on the unchanged manifest reports 0 errors and no drift. An error count above 0 is the signal a CI check can fail on.

Result: real output of audit_vendor_project. Findings of the Drift and Coverage kinds are shown.

# Generated by CoreModels — governed model contracts.
# Meaning changes belong in CoreModels; regenerate this file rather than editing it.
version: 2

models:
  - name: stg_payments
    config:
      contract:
        enforced: true
      materialized: view
    meta:
      coremodels:
        maps_to:
          - standard: "dbt"
            uri: "model.jaffle_shop.stg_payments"
    columns:
      - name: order_id
        description: "[dbt: model.jaffle_shop.stg_payments.order_id]"
        data_type: INT64
        meta:
          coremodels:
            maps_to:
              - standard: "dbt"
                uri: "model.jaffle_shop.stg_payments.order_id"
      - name: payment_method
        description: "[dbt: model.jaffle_shop.stg_payments.payment_method]"
        data_type: STRING
        data_tests:
          - accepted_values:
              values: ["credit_card", "coupon", "bank_transfer", "gift_card"]
        meta:
          coremodels:
            maps_to:
              - standard: "dbt"
                uri: "model.jaffle_shop.stg_payments.payment_method"
            vocabulary: "stg_payments payment_method values"
            vocabulary_maps_to:
              - standard: "dbt"
                uri: "model.jaffle_shop.stg_payments.payment_method#values"
      - name: amount
        description: "[dbt: model.jaffle_shop.stg_payments.amount]"
        data_type: FLOAT64
        meta:
          coremodels:
            maps_to:
              - standard: "dbt"
                uri: "model.jaffle_shop.stg_payments.amount"
      - name: payment_id
        description: "[dbt: model.jaffle_shop.stg_payments.payment_id]"
        data_type: INT64
        constraints:
          - type: not_null
        data_tests:
          - unique
          - not_null
        meta:
          coremodels:
            maps_to:
              - standard: "dbt"
                uri: "model.jaffle_shop.stg_payments.payment_id"

The contract keeps the governed name payment_method and sets enforced: true. dbt checks the columns of the model against it when the model builds.

Note from CoreModels: This model already has properties in 'models/staging/schema.yml'. Remove its block there, or dbt will report a duplicate patch for the generated 'models/coremodels_contracts.yml'.

Result: real output of generate_vendor_artifacts for stg_payments. CoreModels never writes to your repo.