As a code location grows, the asset graph needs structure. Four attributes on the decorator provide it.
group_name="sales" puts the asset in a group. Groups fold together in the graph and can be selected with group:sales. Every asset has one; the default is default.
kinds={"python", "duckdb"} names the technology, up to three per asset, selectable with kind:python.
tags={"pii": ""} adds labels for selection and policy, such as tag:pii. Tags are key and value strings; an empty value is allowed.
owners=["team:finance", "[email protected]"] says who to ask. Owners are email addresses or team names that start with team:; anything else is rejected when the definitions load.
These attributes cost nothing at run time and make every later selection, job and alert easier to write.
One asset with a group, a kind, a tag and an owner.