Add corrupt success case study - #41
Open
marsloting wants to merge 2 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new case study documenting the “corrupt success” verification/termination failure mode, where an agent’s producer-side “done” evidence passes checks but the downstream consumer never receives the work. This expands the repository’s catalog of concrete agent workflow failure patterns and mitigation guidance.
Changes:
- Added a new case study on consumer-end verification for “done/written/shipped” claims.
- Linked the new case study from the main README under “Autonomous Agent Failures”.
- Added the case study as a real-world example under Verification & Termination Failures.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| README.md | Adds a new “Autonomous Agent Failures” entry pointing to the corrupt success case study. |
| docs/failure-modes/verification-termination.md | Adds a new real-world example describing the corrupt success verification failure pattern. |
| docs/case-studies/agent-corrupt-success-consumer-verification.md | Introduces a new case study write-up with scenario, impact, and mitigation guidance focused on consumer-end proof. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+5
to
+7
| **Agent**: AI coding and operations agent<br> | ||
| **Operator**: Marsloting agent workflow<br> | ||
| **Date**: June 2026<br> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a case study for a failure mode that is easy to miss in agent workflows: corrupt success.
The agent reports done and the producer-side check passes, but the downstream consumer never receives the work because proof was collected upstream of the point where the failure surfaces.
Why this fits this list:
Changes:
docs/case-studies/agent-corrupt-success-consumer-verification.mddocs/failure-modes/verification-termination.mdValidation:
git diff HEAD~1..HEAD --check