https://getrefinery.nl/blog/ Practical data improvement and verified development lessons. https://getrefinery.nl/blog/narrow-scope-safer-data-automation/ https://getrefinery.nl/blog/narrow-scope-safer-data-automation/ A practical framework for choosing one operational workflow, limiting the data involved, and deciding what evidence is strong enough to automate a source correction. Wed, 23 Sep 2026 01:47:21 GMT https://getrefinery.nl/blog/what-a-durable-data-repair-receipt-should-make-possible-months-later/ https://getrefinery.nl/blog/what-a-durable-data-repair-receipt-should-make-possible-months-later/ A repair receipt should let an operator reconstruct what changed, why it was authorized, whether the source now matches expectations, and what happened when the same problem returned. Tue, 22 Sep 2026 01:46:06 GMT https://getrefinery.nl/blog/when-data-should-stay-unresolved/ https://getrefinery.nl/blog/when-data-should-stay-unresolved/ A practical framework for deciding when a data problem needs evidence or human review instead of an automatic correction that could make the source less trustworthy. Sat, 19 Sep 2026 05:14:53 GMT https://getrefinery.nl/blog/five-questions-before-automating-a-data-correction/ https://getrefinery.nl/blog/five-questions-before-automating-a-data-correction/ A practical framework for deciding whether a data correction has enough scope, evidence, authority and verification to be automated without hiding uncertainty. Fri, 18 Sep 2026 03:35:36 GMT https://getrefinery.nl/blog/keep-direct-reads-while-improving-operational-data/ https://getrefinery.nl/blog/keep-direct-reads-while-improving-operational-data/ A practical framework for improving data at its source without forcing every application read through a new gateway or replacing the operational database. Mon, 14 Sep 2026 00:16:01 GMT https://getrefinery.nl/blog/monitor-recurring-data-problems-without-promising-permanent-prevention/ https://getrefinery.nl/blog/monitor-recurring-data-problems-without-promising-permanent-prevention/ A practical framework for distinguishing a verified source correction from lasting prevention, using recurrence checks, explicit evidence and visible uncertainty in operational data workflows. Sun, 13 Sep 2026 00:02:30 GMT https://getrefinery.nl/blog/what-a-data-repair-proposal-should-show-its-owner/ https://getrefinery.nl/blog/what-a-data-repair-proposal-should-show-its-owner/ A practical framework for reviewing a proposed source correction before approval, including scope, evidence, expected values, authority, uncertainty and the proof required afterwards. Fri, 11 Sep 2026 00:13:12 GMT https://getrefinery.nl/blog/when-a-read-only-reference-can-establish-a-correct-value/ https://getrefinery.nl/blog/when-a-read-only-reference-can-establish-a-correct-value/ A practical framework for using an approved read-only reference to evaluate conflicting operational data without turning the reference into a second system of record. Thu, 10 Sep 2026 00:07:38 GMT https://getrefinery.nl/blog/finding-a-data-problem-is-not-proving-the-source-correction/ https://getrefinery.nl/blog/finding-a-data-problem-is-not-proving-the-source-correction/ A practical framework for separating detection, authorization, source cleanup and proof when operational data is wrong or uncertain. Tue, 08 Sep 2026 07:16:35 GMT https://getrefinery.nl/blog/building-refinery-why-the-database-stays-in-charge/ https://getrefinery.nl/blog/building-refinery-why-the-database-stays-in-charge/ A lesson from designing Refinery is simple: improving operational data should strengthen the source of truth, not create another competing copy. Mon, 07 Sep 2026 09:04:20 GMT https://getrefinery.nl/blog/before-an-ai-uses-a-record-ask-whether-it-is-eligible/ https://getrefinery.nl/blog/before-an-ai-uses-a-record-ask-whether-it-is-eligible/ An AI assistant does not need every available record. It needs data that satisfies the requirements of the task it is about to perform. Mon, 07 Sep 2026 09:04:14 GMT https://getrefinery.nl/blog/the-hidden-cost-of-fixing-data-away-from-the-source/ https://getrefinery.nl/blog/the-hidden-cost-of-fixing-data-away-from-the-source/ Teams often patch bad data in reports, exports and prompts. The visible error disappears while the source record keeps creating the same operational cost. Mon, 07 Sep 2026 09:04:08 GMT https://getrefinery.nl/blog/a-data-quality-alert-is-not-a-proven-correction/ https://getrefinery.nl/blog/a-data-quality-alert-is-not-a-proven-correction/ An alert can identify a possible data problem. A proven correction requires authorized action at the source, a fresh readback, and durable evidence of what changed. Mon, 07 Sep 2026 09:02:43 GMT