Get ThruLine

Blog

Research and field notes.

What we learn from reading AI coding sessions against what actually ran. Written by the person who built ThruLine.

[ Essay · October 2026 · 8 min read ]

You Are the Latency

What becomes of a person whose job is carrying text from one machine to another. Some of it is funny. Most of it isn’t.

Ashwinsuriya Ravi · Founder

Read the essay

Key takeaways

  1. A meat proxy isn’t lazy. It’s latency.
  2. Workslop costs its reader close to two hours.
  3. We built Searle’s room and moved in.
  4. “The AI said” is an alibi.
  5. Ask: what did I change, and why?

[ ThruLine engineering · October 2026 · 12 min read ]

We Ran ThruLine on Itself

AI coding agents wrote most of ThruLine’s code, and ThruLine recorded them doing it. What its own record caught, what it got wrong about itself, and one fix we recorded end to end.

Ashwinsuriya Ravi · Founder

Read the research

Key takeaways

  1. 1,537 of 1,941 commits name an AI co-author.
  2. Its first finding on us was a false alarm.
  3. The same rules caught our own mistakes.
  4. A decision has to become a check.
  5. We publish our failing rows.

[ ThruLine Research · October 2026 · 12 min read ]

Green Is Not Proof

CI checks the code an AI agent leaves behind. It doesn’t check what the agent did to get there, or whether what it told you is true. The evidence from 2025–2026.

Ashwinsuriya Ravi · Founder

Read the research

Key takeaways

  1. Green answers one question.
  2. Models change the tests.
  3. Passing isn’t correct.
  4. The report isn’t evidence.
  5. The worst failures never reach CI.