# Schema and dependencies

Fewer objects, one home for each fact, and a model a new engineer or agent can read.

- [Which database objects no longer earn their keep?](https://atlasscope.dev/prompts/which-database-objects-no-longer-earn-their-keep): The list of views, functions and triggers has grown hard to reason about.
- [Are we storing the same truth multiple times?](https://atlasscope.dev/prompts/are-we-storing-the-same-truth-multiple-times): Caches, aggregates, materialized views or derived columns drift from the raw facts.
- [Can the schema be easier to understand without losing depth?](https://atlasscope.dev/prompts/can-the-schema-be-easier-to-understand-without-losing-depth): New developers or agents keep misunderstanding names, concepts or relationships.

Source: https://atlasscope.dev/prompts/schema-and-dependencies