Kirra

[Kirra @Kirratr]

@nikotin30x yep im bored to explain to him

[Kirra @Kirratr]

SHE ASKED CLAUDE CODE WHAT HAPPENED TO HER SEO FOLDER, AND IT TOLD HER THE FOLDER WAS NEVER THERE.

A routine git ignore step was all it took. The folder holding 5 finished articles, plus the tracker running her whole pipeline, quietly disappeared. Not moved to trash. Just gone.

She had an agent handling that pipeline end to end: a spreadsheet tracking progress, a Word document per article, internal links wired through file names before Claude Code executed each post live. She asked it to start on article 6. It answered that no spreadsheet existed to track anything.

Still in the same session, she asked it directly what happened to the files. It read back over its own actions and answered with total confidence: never there, she must be remembering it wrong.

That is the exact failure the whole idea of Evidence Engineering exists to catch. Nothing in that answer checked a single fact against the world. It read its own account of itself and reported it back as certainty, and certainty reads identical whether the files are sitting there or gone for good.

The folder was empty. The confidence never dropped by 1 percent.

[Neheart @neheart]

https://t.co/853csaKCpW

[Kirra @Kirratr]

@kardinall yes ai have big problem with memory

[Kirra @Kirratr]

TYPE 1 IS THE LOOP MOST PEOPLE ARE STILL RUNNING BY HAND, AND ANTHROPIC JUST GAVE IT AN OFFICIAL NAME.

Prompt, Claude works, you check the result, you prompt again. That is technically a loop already. You are just the one running every cycle of it yourself, forever.

Anthropic's own guide lays out 4 types, from that manual version up to fully hands off. Type 1 is turn-based, the one above, where you are the loop controller. Type 2 is goal-based: you define what done looks like, something like get a score to 90 or above, stop after 5 tries, and Claude genuinely cannot quit early. An evaluator checks the condition every single time and sends it right back to work.

Type 3 runs on a clock instead of a check. A loop on an interval, checking a pull request every 5 minutes, fixing whatever CI flags. The catch: that version runs on your machine, and it dies the second you close the laptop. Push the same loop to the cloud instead, and it keeps running without you anywhere near it.

Type 4 stacks all of it: a schedule, a goal, parallel attempts at the same fix, a separate agent judging which attempt actually worked. Nobody has to be in the room in real time.

Type 1 needs you in the room. Type 4 was never built to need you at all.

[Neheart @neheart]

https://t.co/dD23yXeMxT

[Kirra @Kirratr]

@neheart girls are preatty

[Kirra @Kirratr]

@kardinall she my waifu

[Kirra @Kirratr]

$330 is the entire operating cost behind a subscription that renews itself every month while she sleeps.

The buyer is usually a man over 35 in the US, Australia, or Europe, paying for the sense that one person out there is choosing him specifically, every night, without fail.

That's the part a human shift never could have sold. A real person cancels the moment the messages get repetitive, or she has a bad week, or she's busy living an actual life. This one doesn't cancel, because she never has an off night to begin with. The same five files run every conversation, remembering his name, his week, the thing he mentioned last Tuesday, without ever needing a day off.

Eleven days into running that exact setup, the real account had spent $330 and pulled in just over $22,000. Most of that money didn't move until the account switched from chasing views to actually pulling fans into a private chat.

Reach was free. Being chosen every night was the part somebody finally learned to sell.

[Kardinall @kardinall]

https://t.co/96ym5qiHOW