# Writes and ingestion

Who writes what, how often it changes nothing, and whether imports survive retries and corrections.

- [Map every place that writes to the database](https://atlasscope.dev/prompts/map-every-place-that-writes-to-the-database): Several jobs, functions, APIs or agents change the same data, or nobody is sure who owns it.
- [Stop rewriting data that hasn't changed](https://atlasscope.dev/prompts/stop-rewriting-data-that-hasnt-changed): Upserts and updates run at high volume, imports are costly, or vacuum and write-ahead log churn look high.
- [Is our ingestion process more complicated than necessary?](https://atlasscope.dev/prompts/is-our-ingestion-process-more-complicated-than-necessary): The import pipeline is long, slow to correct, or does the same work at several stages.
- [Can we rerun everything without damaging the data?](https://atlasscope.dev/prompts/can-we-rerun-everything-without-damaging-the-data): Imports get retried, schedulers overlap, files are replayed, or runs fail halfway.
- [Find where write logic should live](https://atlasscope.dev/prompts/find-where-write-logic-should-live): Business rules are split across SQL, triggers, edge functions, server routes and workers.

Source: https://atlasscope.dev/prompts/writes-and-ingestion