{"id":5197,"date":"2026-09-14T01:41:49","date_gmt":"2026-09-14T04:41:49","guid":{"rendered":"https:\/\/tucumandevelopers.com\/index.php\/2026\/09\/14\/when-someone-elses-system-rejects-you-without-a-reason-fixing-a-diagnostic-order-in-advance\/"},"modified":"2026-09-14T01:41:49","modified_gmt":"2026-09-14T04:41:49","slug":"when-someone-elses-system-rejects-you-without-a-reason-fixing-a-diagnostic-order-in-advance","status":"publish","type":"post","link":"https:\/\/tucumandevelopers.com\/index.php\/2026\/09\/14\/when-someone-elses-system-rejects-you-without-a-reason-fixing-a-diagnostic-order-in-advance\/","title":{"rendered":"When Someone Else’s System Rejects You Without a Reason \u2014 Fixing a Diagnostic Order in Advance"},"content":{"rendered":"
\n
\n

And the way of speaking becomes a rule too.<\/p>\n

\n

Before verification, don’t say “cause.” Say “candidate.”<\/strong><\/p>\n<\/blockquote>\n

This one word keeps the record uncontaminated. A candidate can be erased, but a cause gets read as fact by the next person.<\/p>\n

<\/a> 4. Design the Discriminating Test First <\/h3>\n

If there are multiple candidates, first build a test that separates the candidates<\/strong>. Picking one without a test is exactly what guessing is.<\/p>\n

\n\n\n\n\n\n\n\n\n
Candidate<\/th>\nDiscriminating test<\/th>\nInterpreting the result<\/th>\n<\/tr>\n<\/thead>\n
Rules not agreed to<\/td>\nCan the data list be queried?<\/td>\nIf yes, agreement is done<\/td>\n<\/tr>\n
Service configuration problem<\/td>\nDoes the metadata show a “submissions paused” flag?<\/td>\nIf not, the configuration is fine<\/td>\n<\/tr>\n
My file format<\/td>\nSend it once in a different format<\/strong><\/td>\nIf it passes, the format is the cause<\/td>\n<\/tr>\n
Account permissions<\/td>\nSame call with a different account or different key<\/td>\nOnly at this point do you ask a person<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The reason we lost two days is that we never carried the third test through to the end<\/strong>. We postponed the cheapest test until last.<\/p>\n

<\/a> 5. The Sentences to Put in CLAUDE.md <\/h3>\n

To make the agent follow this order every time, nail it into the rules file. <\/p>\n

\n
 <\/code><\/pre>\n
\n<\/p><\/div>\n<\/p><\/div>\n
If you have the memory structure built in Chapter 3, incidents like this also get recorded in mistakes.md<\/code>.
 The sole purpose of the record is to keep the same mistake from happening twice.<\/strong><\/p>\n
  <\/a> 6. Locking It In with a Regression Test <\/h3>\n
Once you’ve found the cause, don’t stop there. Leave a test so that that format can never be produced again<\/strong>. <\/p>\n
\n
def<\/span> test_submission_is_targz_not_zip<\/span>():<\/span> path<\/span> =<\/span> build_submission<\/span>()<\/span> assert<\/span> path<\/span>.<\/span>suffix<\/span> ==<\/span> \"<\/span>.gz<\/span>\"<\/span> and<\/span> path<\/span>.<\/span>name<\/span>.<\/span>endswith<\/span>(<\/span>\"<\/span>.tar.gz<\/span>\"<\/span>),<\/span> \\ def<\/span> test_required_files_are_at_archive_root<\/span>():<\/span> with<\/span> tarfile<\/span>.<\/span>open<\/span>(<\/span>build_submission<\/span>())<\/span> as<\/span> tar<\/span>:<\/span> names<\/span> =<\/span> tar<\/span>.<\/span>getnames<\/span>()<\/span> <\/code><\/pre>\n
\n<\/p><\/div>\n<\/p><\/div>\n
The key is writing why the test exists<\/strong> in the test’s message. Without the reason, six months later someone (or an AI) deletes it as “a constraint that looks unnecessary.”<\/p>\n
  <\/a> 7. How to Phrase a Request to a Human <\/h3>\n
If you’ve come all the way to the end and truly need a human hand, say it like this.<\/p>\n