小满的爱车观察站

晚上开车回家车灯照亮了整条路好温暖｜汽车日记 @marilyn_1003

[小满的爱车观察站 @damufuknman]

@0xWast3 Thanks for sharing

[Sprytix @Sprytixl]

THIS IS ACTUAL F*CKING GOLD

Anthropic just shared one of the best tricks for Claude Code.

The idea: stop asking for an answer. Give it a stop condition and let one agent loop until it hits it.

Same codebase, two ways: one-shot got 61% and guessed the rest. The loop ran 43 times and came back with 388 of 388 rules verified.

You just launch Claude Code like this:

claude --model opus --loop "map legacy/ until 100% verified"

here's the split:
→ you write one prompt and then do nothing, zero edits for the entire run
→ REA loops read → extract → verify → fix on its own
→ every rule it extracts gets replayed against real prod logs before it counts
→ the loop only stops when all 388 rules pass, not when the model feels done
the part everyone gets wrong: they accept the first pass.
a single pass over 16 services gives you a confident document where most of it was never checked against anything.
here rules.md grows every loop. 388 rules across auth, billing, payments, checkout, admin and the rest, each one marked verified only after it survives a replay.

three rules came back wrong. the agent re-read the source, fixed them, and looped again instead of shipping them.

one prompt from you, 43 loops from it, 0 edits by you.

Opus drives. REA reads and verifies. The loop decides when it is done.

JEV engineering is the same move one layer down: the forks that need no thinker (which file next, re-loop or stop, retry or fail) go to JEV in milliseconds, and the model only sees the ones that actually split

the full tree
> Opus 5.5 runs the session with a stop condition, not a task
> REA loops read, extract, verify and fix on every pass
> every extracted rule is replayed against prod logs before it counts as verified
> any mismatch sends that module back for a re-read instead of shipping
> rules.md grows each loop until the stop condition is met
> JEV routes micro-forks in milliseconds

paste the tree and this prompt into Claude Code ↓

"Rebuild my Claude Code setup around this tree:

1. Run the main session on Opus 5.5 and give every long task a stop condition, never a single pass.
2. Loop read, extract, verify and fix until the condition is met.
3. Every extracted rule must be replayed against real logs or tests before it counts as verified.
4. Any mismatch triggers a re-read of that module, never a patched guess.
5. Add one rule to CLAUDE.md: unverified findings are never written into the final document.
6. Route deterministic forks (next file, re-loop or stop, retries) through JEV.

Show me every change as a diff first. No edits until I say go."

↳
https://t.co/GoHZ0potb7

save it, you'll use this on every legacy repo from now on.

[小满的爱车观察站 @damufuknman]

@tomasi01 掉价这点我认，春风二手确实没法跟保值神车比，所以我也不急着出。你要是有更合适的我也乐意看看对比下。

[小满的爱车观察站 @damufuknman]

乌鲁木齐今天碰到二手春风街车，像甜酷姐姐穿旧了最喜欢的皮衣，原厂件保留得多，骑起来也很熟。昌吉、哈密、吐鲁番，完整车况在主页。

[小满的爱车观察站 @damufuknman]

@migeultan62 哈哈对，旧皮衣的那股味才是最勾人的，车也是，有使用痕迹反而踏实。你平时骑什么车？

[小满的爱车观察站 @damufuknman]

@haleyceoxton 保养记录车主都留着，我翻了一遍还挺全，这种车就是图个心里有底。要不要我把保养节奏跟你说说？

[小满的爱车观察站 @damufuknman]

@kween_beasty 哈密那段确实吃了不少沙，散热缝隙里能抠出来，不过没什幺大问题。你也跑过那边？

[小满的爱车观察站 @damufuknman]

@lilmizzloser521 对，新手上去不容易被车拽着走，长途也不那么累。你身边要是有刚拿本的，我可以说说这台的具体感觉。

[小满的爱车观察站 @damufuknman]

@kendralkc 就是这个意思，改过的车后面理线换件最费劲，我这台就赢在没被乱动。

[小满的爱车观察站 @damufuknman]

@TFG4life 对，过户前把昌吉那边的缴税和提档顺序问清楚，不然白跑一趟。你是走提档过去的还是本地落？

[小满的爱车观察站 @damufuknman]

@TINSLICE 简单说先对原厂清单看螺丝有没有被拆过的痕迹，塑料件卡扣和线束捆扎也能看出动没动过。你要真拿不准列一份清单我帮你过一眼？

[小满的爱车观察站 @damufuknman]

@RinAChAe haha 底色还在，油箱侧面有两道小划，别的都是原漆，回头拍细节给你看呗。

[小满的爱车观察站 @damufuknman]

@_PUMPK1N_ 是吧，我也觉得坐姿挺直，骑久了腰不遭罪。你当时骑的是哪年款？

[小满的爱车观察站 @damufuknman]

@Bugatti the odd-world speedrun physics is still gorgeous

[小满的爱车观察站 @damufuknman]

down 4 dat beef but my pokets vegetarian