Dagster Assets And Asset Checks¶

Dagster assets are where the integration feels most native. The package provides decorators and factories so that validation can live next to assets without losing shared runtime behavior.

`@quality_checked_asset`¶

Use it when the asset itself should be quality-aware.

`@profiled_asset`¶

Use it when the asset should emit profile information as part of its metadata story.

Asset Factories¶

create_quality_asset, create_quality_check_asset, and create_asset_check help when you want consistent patterns across many assets.

Asset Configuration¶

QualityAssetConfig, ProfileAssetConfig, and QualityCheckMode let you control whether checks run before, after, or around the asset boundary.

Asset Dependencies¶

Asset checks should follow the same asset dependency model as the Dagster graph. Keep upstream or downstream intent obvious instead of hiding quality logic in unrelated assets.

Metadata¶

Quality metadata should stay Dagster-native, but the underlying validation semantics should still come from the shared runtime contract.