# Evidence package: The Agent That Could Fix the Code but Couldn't Finish the Job

Ayobami John Haastrup (ayobamih) · 1 November 2026

Article: https://aiworkaccountability.com/writing/the-agent-that-could-fix-the-code-but-couldnt-finish-the-job/

This is an **owner-generated, redacted record** of an engineering release which initially stalled and later passed guarded deployment. It is not an independent third-party audit or peer-reviewed experiment.

## Files

- [case.json](https://aiworkaccountability.com/evidence/tailwagging-autonomous-delivery/case.json) — final SHA, successful and superseded CI job states, Cloudflare release identity, browser DOM hashes and explicit limitations.
- [sources.json](https://aiworkaccountability.com/evidence/tailwagging-autonomous-delivery/sources.json) — source URL and visibility map. Tail Wagging's repository is **private**, so some external links require authorised access.
- [citation.bib](https://aiworkaccountability.com/evidence/tailwagging-autonomous-delivery/citation.bib) — article citation.
- [SHA256SUMS.txt](https://aiworkaccountability.com/evidence/tailwagging-autonomous-delivery/SHA256SUMS.txt) — checksums for the three files above and this README.

## Distinct historical checkpoints

On 31 October 2026, PR #126 was merged and quality checks passed, but production was still on hold and the portfolio route was not deployed. The first draft was correctly described as an **unfinished release**.

On 1 November 2026, CircleCI pipeline #16 checked merged SHA `c19703717e3d6c3ed45b0d11a3c3c5bffa25ca8b`. All four workflow jobs succeeded. Owner-run live HTTP, commercial capability, release-SHA and browser checks then passed. The active Cloudflare Worker version was `7615022e-83e6-4ef9-9e3e-873831e99b00`.

## Limits of proof

The canonical release was guarded, not bypassed. A rollback was available but was not exercised because the release succeeded. No live card charge, full customer purchase or exhaustive device acceptance was performed. A user manually saved a one-time CircleCI token, and multiple follow-up prompts were needed: **this is not fully unattended agent autonomy**.

The private close-out receipt contains eight hashed internal snapshots; its SHA-256 is `65fbe0abd2b58f3b17385f24b429ceec4525640204fa82f2109f54eb9343c2b4`. We **do not** offer it as a public download or claim that its hash independently proves the truth of the contained observations. The redacted package includes no private raw logs, token contents, environment files, account identifiers, customer data or full private filesystem paths.

Use the public live endpoints for contemporary context and the fixed extract to understand what was observed at publication. A future deployment can legitimately serve another SHA.