AckuityRequest access Jason Lemkin reports that SaaStr Connect’s matching file was overwritten twice while Astra 6 was building it. The running service stayed online.
THE CONTROL LESSON
What should we watch for?
Ackuity’s view: verify file writes against the requested task before they run. Inspect diffs independently and deploy only known-good revisions.
THE EVIDENCE
What does the report establish?
This is SaaStr’s account, without independent confirmation. The cause and model’s awareness are not established. The animation’s BLOCK stamp and size/hash signals are proposed safeguards, not observed interventions. SaaStr says it had no such check. The source supplies no exact incident date or model developer.
Read the full account
Lemkin says a core matching file was reduced to five bytes twice within about half an hour. The agent reported the damage but denied making the edit. SaaStr restored the file; the service stayed up because its running server retained the earlier code. Lemkin suspects an approval instruction became file content, but presents this as his interpretation.
An agent’s explanation is not an independent execution record. A safe running process can also hide a broken working copy until a restart.
ORIGINAL REPORTING & EVIDENCE