{
  "id": 15369485,
  "title": "Letter to 08:20-Me: Stop Auditing the Agent, Audit the Counters",
  "url": "https://urgent.news/2026/10/18/letter-to-08-20-me-stop-auditing-the-agent-audit-the-counters",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-18T07:07:19.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/codejs_8314/letter-to-0820-me-stop-auditing-the-agent-audit-the-counters-2df3"
  },
  "original_language": "en",
  "account": "This letter is addressed to a previous version of the author, who recounts a day of workflow experimentation on August 20th. The author utilized free server and model access resources, but faced several issues that led to lost time and frustration.\n\nKey lessons learned include:\n1. Use a ledger to track each step and avoid assuming the model's work is sufficient. Logging before model calls ensures an observability record.\n2. Relying on reviewer agreements as tests can lead to mistakes. Reviewer opinions should be considered alongside failing test outputs.\n3. Running the writer and reviewer in the same workspace can cause conflicts. Separate directories and gate the write paths to maintain integrity.\n\nThe author recommends a six-step loop that freezes the fixture pack, validates plans, runs tests on the free server, sends diffs and test failures to the model, compares verdicts to test exit codes, and logs rows with timing information. This structured approach provides a clear audit trail and prevents issues from recurring.\n\nHowever, the author cautions that free model access and free server options are not guaranteed for sustained performance or contractual SLAs. The workflow may not be suitable for tasks requiring production credentials, regulated data, or contractual uptime guarantees. It also suggests that isolated runners and human reviewers are essential components for a reliable workflow.\n\nThe author concludes by advising the earlier version of themselves to write counters before prompts, hashes before diffs, and to rely on test failures over reviewer agreements when discrepancies arise. Running the six-step loop once with free access and free server is recommended as a proof of concept, even if the resources are eventually abandoned.",
  "summary": "I opened two terminals at 08:20 and closed them at 19:40. One terminal held a free server box. The other held an agent writing patches. By lunch I had three diffs and no idea which run produced which. This is a letter to that version of me. It is also a workflow you can copy. It uses free model access as a second reader, and a free server as the test runner. Both are operator-supplied…",
  "key_points": [
    "Author experimented with workflow on August 20th using free resources",
    "Learned importance of logging steps and separate directories for writer/reviewer",
    "Recommended six-step loop for audit trail and preventing recurring issues"
  ],
  "editors_take": "Shifting focus from model performance to rigorous logging and automated counters transforms fragile experimentation into a structured workflow that prioritizes verifiable test failures over subjective human reviewer agreements.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}