I just did. I did not find anything on compound values where the components can have references to other components with in the compound value. Maybe I did not look good enough. I also would like to have integrity requirements on references such as FOREING KEY constraints with cascaded delete in Relational databases. I also would like to have transactions like those in databases.

I am surprised that there are still no software development platforms where you use one language for all levels and do not have to translate between different ways of representing data and interacting with services.

The interesting applications are where multiple agents (people and/or other systems) are working on the same data. The methods to define such forms of cooperation are rather primitive. On one hand you have the databases with their transactions and pessimistic locking approaches. On the other hand you have git repositories with optimistic locking and manual merging. Sometimes you would like to have something in the middle, where you can define which operations conflict (do not commute) and how to deal with them.