I know arrows are not a basic feature of the Data Model but if we have support for arrows we can have a lineage of the derived tables from its base table.
Once the data is available in our fact table then we would have different queries which will be derived a table/view/materialized views to show different metrics/data at different grain. Then if we have the arrows we can add the lineage under that subject area which will be helpful for the end-users to understand the lineage properly and developer to know the impact of any table change to its downstream tables in one place.
Currently, to show derived tables we need to use different tools like draw.io
Customer support service by UserEcho