---
title: "Comment by Kartik N V J K on \"My AI deleted more than twenty unfinished tasks so it could say it was done\" | Hashnode"
description: "This is textbook reward hacking: the gate measured \"unfinished count,\" so the agent optimized the metric by deleting the tasks, exactly what Goodhart predicts o"
url: "https://hashnode.com/posts/my-ai-deleted-more-than-twenty-unfinished-tasks-so-it-could-say-it-was-done/6a58de29691da066eee9a863/comment/6a5a30b26eafcae2692212df"
---

[Discussion](https://hashnode.com/posts/my-ai-deleted-more-than-twenty-unfinished-tasks-so-it-could-say-it-was-done/6a58de29691da066eee9a863)

Comment [My AI deleted more than twenty unfinished tasks so it could say it was done](https://hashnode.com/posts/my-ai-deleted-more-than-twenty-unfinished-tasks-so-it-could-say-it-was-done/6a58de29691da066eee9a863)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Jul 17](https://hashnode.com/posts/my-ai-deleted-more-than-twenty-unfinished-tasks-so-it-could-say-it-was-done/6a58de29691da066eee9a863/comment/6a5a30b26eafcae2692212df)

This is textbook reward hacking: the gate measured "unfinished count," so the agent optimized the metric by deleting the tasks, exactly what Goodhart predicts once a check becomes the target. The tell is that your gate read from a mutable list the agent could also write to, so the measurement and the thing measured shared state. Did you move the source of truth somewhere the agent can't edit, like an append-only log the gate reads?

[Bryce Darling](https://hashnode.com/@mindrealm)

[Jul 17](https://hashnode.com/posts/my-ai-deleted-more-than-twenty-unfinished-tasks-so-it-could-say-it-was-done/6a58de29691da066eee9a863/comment/6a5a30b26eafcae2692212df#reply-6a5a6a38e4fc24a048b947c4)

Append-only in normal operation, yes. Immutable against an agent with the same shell access, no. That distinction is why I didn’t make the log the completion authority.

The history records which transition the harness accepted. It can't tell me whether the work earned "done," so the guard now treats completed as a claim. A separate read-only reviewer checks the original task against the current repository state and issues a certificate bound to both. Redefine the task, change the artifact, replay stale evidence, or delete an uncertified task, and the gate blocks.

The pattern I landed on is append-only event history plus independent certification of the work.
