<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zhuojun Li</title>
    <description>The latest articles on DEV Community by Zhuojun Li (@lizhuojunx86).</description>
    <link>https://dev.to/lizhuojunx86</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3990737%2Fecf68c91-8302-4910-8f26-ae04f9489100.jpg</url>
      <title>DEV Community: Zhuojun Li</title>
      <link>https://dev.to/lizhuojunx86</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lizhuojunx86"/>
    <language>en</language>
    <item>
      <title>I planned to copy Composio's "reactions" into my agent dispatcher. My logs said it would have caught 1 redo out of 19.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Tue, 17 Nov 2026 00:11:08 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/i-planned-to-copy-composios-reactions-into-my-agent-dispatcher-my-logs-said-it-would-have-5a7c</link>
      <guid>https://dev.to/lizhuojunx86/i-planned-to-copy-composios-reactions-into-my-agent-dispatcher-my-logs-said-it-would-have-5a7c</guid>
      <description>&lt;p&gt;I run a homemade dispatcher called agent-dispatch. Claude plans the work and writes a work order. A cheaper model does the coding in a macOS sandbox, on its own git worktree and branch. Claude Sonnet reviews the diff read-only. Then I merge locally. It's about 14,000 lines of stdlib Python in one file, 124 commits since October 11, and since November 1 it has handled 64 orders.&lt;/p&gt;

&lt;p&gt;This week I compared it with the mature tools: Composio's Agent Orchestrator, OpenRouter's new subagent and advisor server tools, Claude Code subagents, and the hosted "assign an issue, get a PR" agents (Codex cloud, Copilot coding agent, Jules). I made a list of four things to borrow. Then I checked the list against my own order logs, and half of it fell over.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the mature tools do better
&lt;/h2&gt;

&lt;p&gt;Composio's orchestrator is the closest match to mine: one git worktree per agent, a dashboard, and a YAML block called &lt;code&gt;reactions&lt;/code&gt;. CI fails, the logs go back to the agent, it retries N times, and only then does a human get pinged. Review comments get the same treatment. Their pitch is "push, not pull": you hear about an order only when a decision is yours to make.&lt;/p&gt;

&lt;p&gt;OpenRouter shipped two server tools that point in opposite directions. &lt;code&gt;openrouter:subagent&lt;/code&gt; lets a strong model hand routine subtasks to a cheap worker. &lt;code&gt;openrouter:advisor&lt;/code&gt; lets a cheap model ask a strong one for a single-turn second opinion mid-run. Both are beta and both are plain API calls. Neither touches a repo, a test suite or a branch.&lt;/p&gt;

&lt;p&gt;Claude Code lets each subagent run a different model in its own worktree. OpenCode does the same with an agent-to-model map in its config. The hosted agents are the most polished, but each one locks you to its vendor's models.&lt;/p&gt;

&lt;p&gt;What I have that they mostly don't: any vendor's CLI as the worker (Xiaomi MiMo, GPT-6.1 Sol through the Codex CLI, DeepSeek), per-worker price cards with a monthly USD cap, automatic fallback when a lane is down, and a replay script that re-runs old hard orders on a new model.&lt;/p&gt;

&lt;h2&gt;
  
  
  The plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Reactions: when review blocks, send the blocking items back to the worker automatically.&lt;/li&gt;
&lt;li&gt;Advisor: when a cheap worker gets stuck, let it consult a strong model once instead of escalating the whole order.&lt;/li&gt;
&lt;li&gt;Self-contained orders: lint work orders for references to a conversation the worker can't see.&lt;/li&gt;
&lt;li&gt;Per-order cost ledger.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What the logs said
&lt;/h2&gt;

&lt;p&gt;Item 4 already existed. I had built it on October 31 and forgotten (&lt;code&gt;stats&lt;/code&gt; already reports cost per worker and per project). Since November 1: $35.74 total, $32.24 of it on GPT-6.1 Sol across 49 orders.&lt;/p&gt;

&lt;p&gt;Item 1 was the one I was most excited about. The review log since November 1: 50 pass, 1 block. Sol, my default worker since November 3, passed first time on 36 of its 43 accepted orders (84%). Review almost never blocks, so a review-block reaction would almost never fire.&lt;/p&gt;

&lt;p&gt;But second rounds still cost me. I pulled every attempt since November 1:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Attempt kind&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;th&gt;Tokens&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;first&lt;/td&gt;
&lt;td&gt;63&lt;/td&gt;
&lt;td&gt;145.7M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;redo (written by me)&lt;/td&gt;
&lt;td&gt;19&lt;/td&gt;
&lt;td&gt;46.1M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;escalate&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;14.5M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;auto retry (check failed)&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;8.8M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;stall retry&lt;/td&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3.2M&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(All 14 stall retries were MiMo streams hanging mid-run. That's one reason I stopped paying for MiMo.)&lt;/p&gt;

&lt;p&gt;The 19 manual redos are where a reaction would have to earn its keep. I read every feedback file:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Why I sent it back&lt;/th&gt;
&lt;th&gt;Redos&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;My diff review found a bug the reviewer passed&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A run on real data or the real network found a problem the sandbox couldn't&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The worker stopped and asked permission (usually to change an old test)&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The base branch moved and the rebase broke&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;My work order was wrong&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;One of the 19 was a genuine review block that an automatic reaction could have handled. One.&lt;/p&gt;

&lt;p&gt;The five real-environment failures are the interesting row. My sandbox blocks the network and my real databases on purpose, so a worker literally can't see that Wikidata returns Traditional Chinese labels for 開封市, or that one feature in Natural Earth's river file has an empty geometry. No reaction fixes that. Someone has to run the thing for real.&lt;/p&gt;

&lt;p&gt;The four "may I?" stops look like an advisor problem at first. They aren't. Every one asked for an authorization ("can I change this assertion?"), and an advisor model has no business granting that.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm building anyway, and why
&lt;/h2&gt;

&lt;p&gt;I still dispatched item 1, scoped down: one automatic redo per order, then it stops and waits for me. Sol built it in one round. (The worker is told to argue back in its report if the review is wrong, instead of forcing a change.) The reason is item 2. If a much cheaper model plus an occasional advisor call can match Sol, review blocks will come back, and the reaction should be ready when they do.&lt;/p&gt;

&lt;p&gt;I dispatched item 3 as well. On October 29 I scored 61 "must fix" items from first-round reviews of ten orders that needed rework. 55 of them (90%) were gaps in my work order, not the worker ignoring it. The new lint only warns. It flags a missing background section and phrases like "as discussed" that point at a conversation the worker never saw. Run over the 67 implementation orders since November 1, it flagged 6. Four were real (a batch of orders I wrote one evening with no background section at all). Two were false positives: one used "mentioned above" for an earlier line of the same order, and the other was the lint's own work order, which quoted the phrase as an example.&lt;/p&gt;

&lt;p&gt;Before submitting, I ran both orders through my "falsifier", a read-only Sonnet pass that attacks the order against the actual repo (35 seconds, about $0.07). It found 7 defects in the first draft of each order, including one CRITICAL: my reaction hook sat inside a &lt;code&gt;try/except&lt;/code&gt; that would have turned any crash in the redo into "review unavailable". After I fixed those, a second pass found 7 more in each. These were orders I wrote on the same day I was writing about how 90% of rework comes from gaps in orders (so yes, the lint is partly for me).&lt;/p&gt;

&lt;h2&gt;
  
  
  The replay set is the part worth copying
&lt;/h2&gt;

&lt;p&gt;On October 31 I replayed five orders that had taken MiMo 3 to 7 rounds each:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GPT-6.1 Sol (medium effort): passed review first time on 3 of 4 doable orders, about 17 minutes and $0.8 each.&lt;/li&gt;
&lt;li&gt;GPT-6.1 Terra (xhigh): 2 of 4, about 26 minutes and $1.0 each, using 3 to 4 times Sol's tokens.&lt;/li&gt;
&lt;li&gt;Both stopped within minutes on the fifth order and pointed out that my order contradicted itself.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That replay is why Sol is my default today. Leaderboards told me Terra was the better deal. My own five orders said otherwise.&lt;/p&gt;

&lt;p&gt;This week I replayed the same five orders on three cheaper models: GPT-6 Luna (direct from OpenAI), and GLM-5.3 and Tencent Hy4 through OpenRouter, each with its own API key and a hard credit limit so the bill per lane is exact.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Lane&lt;/th&gt;
&lt;th&gt;Finished&lt;/th&gt;
&lt;th&gt;Passed first round&lt;/th&gt;
&lt;th&gt;Passed with no human input&lt;/th&gt;
&lt;th&gt;Avg minutes&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6.1 Sol (Oct 31)&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;3 of 4 doable&lt;/td&gt;
&lt;td&gt;3 of 4&lt;/td&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;$0.66 per order&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6 Luna&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;2/5&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;52&lt;/td&gt;
&lt;td&gt;$0.24 per order&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GLM-5.3&lt;/td&gt;
&lt;td&gt;1/5&lt;/td&gt;
&lt;td&gt;1/1&lt;/td&gt;
&lt;td&gt;1/1&lt;/td&gt;
&lt;td&gt;68&lt;/td&gt;
&lt;td&gt;~$6.30 spent, then the $7 key ran dry&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tencent Hy4&lt;/td&gt;
&lt;td&gt;2/10 (alone and with advisor)&lt;/td&gt;
&lt;td&gt;1/2&lt;/td&gt;
&lt;td&gt;2/2&lt;/td&gt;
&lt;td&gt;70&lt;/td&gt;
&lt;td&gt;~$3.60 spent, then the $4 key ran dry&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(The new runs went four at a time with reviews queued behind each other, so their minutes are inflated a bit. Sol's ran two at a time.)&lt;/p&gt;

&lt;p&gt;Three things I didn't expect.&lt;/p&gt;

&lt;p&gt;GLM and Hy4 look cheap on the price page and weren't cheap here. They chewed through tokens and got almost no cache hits, so a finished order cost as much as Sol or more. Both keys hit their limits before the round was done. If I hadn't set per-key limits, I'd have found out on the invoice.&lt;/p&gt;

&lt;p&gt;Luna finished all five at about a third of Sol's cost, and nobody touched it. Two orders failed their checks and retried automatically. Two got blocked by review, and the new review-block reaction sent them back. Both came back clean. So the reaction I almost didn't build fired twice on its first day. But Luna took three to four times as long, and on the order that contradicts itself, Sol and Terra both stopped and asked. Luna didn't notice, built something, and the reviewer passed it. That's the one result I'd want a human to see before trusting the cheap lane.&lt;/p&gt;

&lt;p&gt;The advisor barely got used. I told the cheap models in plain words that a stronger advisor was available and when to ask. Across the four advisor-lane runs that got going before the keys ran out, one Hy4 run asked once. It was a good question (whether its reading of three ambiguous spec clauses held up), and the advisor's bill for the whole day was $0.095. One call isn't a result. What it does suggest is that "ask when you're stuck" doesn't happen on its own. If I keep the advisor, the dispatcher will have to make the call at fixed points, before delivery or after a second failure, rather than leave it to the worker.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you run something similar
&lt;/h2&gt;

&lt;p&gt;Count your redo reasons before you build automation for them. Mine were mostly "the reviewer missed a bug" and "the sandbox can't see reality", and neither one is a reaction. And keep a handful of your own past hard tasks as a replay set, with one API key per model and a hard limit on each. This round cost me about $13 across four models. That's cheap for finding out that two "cheap" models weren't, and that the cheap model that worked needs a human to look at its output.&lt;/p&gt;

&lt;p&gt;Happy to compare notes if you're running a dispatcher of your own.&lt;/p&gt;

&lt;p&gt;Zhuojun Li&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>devtools</category>
      <category>opensource</category>
    </item>
    <item>
      <title>My cheap coding plan ran out in 20 days, and cost more per merged change than GPT-6.1 Sol</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Fri, 13 Nov 2026 03:17:31 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/my-cheap-coding-plan-ran-out-in-20-days-and-cost-more-per-merged-change-than-gpt-61-sol-22h9</link>
      <guid>https://dev.to/lizhuojunx86/my-cheap-coding-plan-ran-out-in-20-days-and-cost-more-per-merged-change-than-gpt-61-sol-22h9</guid>
      <description>&lt;p&gt;Short version: I paid ¥329 (about $46) a month for Xiaomi's MiMo Token Plan Pro and burned through it in 20 days. Per accepted change, MiMo came out at about $0.81 and GPT-6.1 Sol at $0.71. The price per change was close. The real gap was rework: Sol passed review on the first try 71% of the time, MiMo 16%.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;I run a small dispatcher called agent-dispatch. Claude plans the work, writes the orders and reviews the results. A cheaper model does the coding. Each order runs in a macOS sandbox on its own git worktree, then the dispatcher runs tests and lint, then Claude Sonnet reviews the diff. I merge only what passes.&lt;/p&gt;

&lt;p&gt;On October 14 I bought MiMo's Pro plan: ¥329 a month for 38 billion credits. The idea was simple. Chinese models are cheap, so let one do the bulk coding and save my Claude quota for planning and review. Claude quota is the most expensive thing in my stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;p&gt;The plan ran from October 14 to November 13. It was empty by November 3.&lt;/p&gt;

&lt;p&gt;MiMo Code keeps a local SQLite database. Applying Xiaomi's published credit rates to it, those 20 days come to about 42.7 billion credits, 93% of it from the dispatcher. (Usage between midnight and 8am Beijing time is billed at 0.8x, which is why the plan lasted until November 3.)&lt;/p&gt;

&lt;p&gt;In those 20 days MiMo took 87 real orders and ran 238 attempts. 53 orders were accepted. 14 passed on the first try.&lt;/p&gt;

&lt;p&gt;When the credits ran out I switched the default lane to GPT-6.1 Sol at medium reasoning, paid per token through the API. From November 3 to 12, Sol took 31 orders and ran 44 attempts. 25 were accepted, 22 on the first try. The API bill was $17.82.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cost per accepted change
&lt;/h2&gt;

&lt;p&gt;MiMo: 93% of ¥329 is ¥306, about $43. Divided by 53 accepted orders, that's about $0.81 each, at 4.5 attempts per accepted order.&lt;/p&gt;

&lt;p&gt;Sol: $17.82 / 25 = $0.71 each, at 1.8 attempts.&lt;/p&gt;

&lt;p&gt;The model bill alone is close. Rework is where it diverges. Every attempt runs the test suite, and most also get a Claude review. I sampled one: a Sonnet review cost about $0.20, paid from my Claude subscription. MiMo's extra 2.7 attempts per accepted order add roughly $0.54 in review alone. And time: Artificial Analysis lists MiMo-V2.6-Pro at 35.6 minutes per task, Sol (medium) at 4.2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Surprise 1: the plan is barely a discount
&lt;/h2&gt;

&lt;p&gt;I assumed the monthly plan was heavily subsidised. It isn't. MiMo-V2.6-Pro pay-as-you-go is ¥3 per million uncached input tokens and ¥6 per million output tokens. The plan's credit rates work out to exactly 100 million credits per yuan, so 38 billion credits is ¥380 of pay-as-you-go usage.&lt;/p&gt;

&lt;p&gt;¥329 for ¥380 of tokens is 13% off. Unused credits expire. Run out mid-month and it doesn't roll over to pay-as-you-go. You just wait. Compared with Claude it's still very cheap. Compared with its own API price, it's a prepaid card.&lt;/p&gt;

&lt;h2&gt;
  
  
  Surprise 2: my own ledger undercounted by 2.6x
&lt;/h2&gt;

&lt;p&gt;The dispatcher records token usage for every order. When I first totalled the month from my own ledger, MiMo had used about 15 billion credits, less than half the plan. I nearly concluded I'd bought too big a plan.&lt;/p&gt;

&lt;p&gt;Only after the credits actually ran out did I check MiMo Code's database. The dispatcher's share for the same period was 39.7 billion. My ledger was off by about 2.6x. The main cause: it only counted usage events from MiMo's output stream, which covers the main session. Subagents write their usage to child sessions in the database, and those never appear in the stream. The fix is in progress.&lt;/p&gt;

&lt;p&gt;If you log usage yourself, reconcile it against the provider's numbers. Otherwise every cost analysis you build on it is wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The leaderboard agrees
&lt;/h2&gt;

&lt;p&gt;Artificial Analysis model leaderboard, November 13, 2026 (Intelligence Index / cost per task / time per task):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Index&lt;/th&gt;
&lt;th&gt;Cost/task&lt;/th&gt;
&lt;th&gt;Time/task&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6.1 Sol (xhigh)&lt;/td&gt;
&lt;td&gt;52&lt;/td&gt;
&lt;td&gt;$0.76&lt;/td&gt;
&lt;td&gt;9.8 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6.1 Sol (medium)&lt;/td&gt;
&lt;td&gt;46&lt;/td&gt;
&lt;td&gt;$0.36&lt;/td&gt;
&lt;td&gt;4.2 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kimi K3.1 Pro&lt;/td&gt;
&lt;td&gt;46&lt;/td&gt;
&lt;td&gt;$3.68&lt;/td&gt;
&lt;td&gt;37.9 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6.1 Terra (high)&lt;/td&gt;
&lt;td&gt;42&lt;/td&gt;
&lt;td&gt;$0.26&lt;/td&gt;
&lt;td&gt;4.2 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DeepSeek V4.1 Flash (max)&lt;/td&gt;
&lt;td&gt;33&lt;/td&gt;
&lt;td&gt;$0.60&lt;/td&gt;
&lt;td&gt;15.2 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GLM-5.3 (max)&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;td&gt;$5.01&lt;/td&gt;
&lt;td&gt;27.6 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MiMo-V2.6-Pro&lt;/td&gt;
&lt;td&gt;30&lt;/td&gt;
&lt;td&gt;$0.26&lt;/td&gt;
&lt;td&gt;35.6 min&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;At the same $0.26 per task, Terra (high) scores 12 points higher than MiMo and finishes 8x faster. The only Chinese model at Sol-medium level is Kimi K3.1 Pro, at 10x the cost and 9x the time. This is a general intelligence index, not a coding benchmark, but it points the same way as my 16% vs 71%.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I run now
&lt;/h2&gt;

&lt;p&gt;Sol (medium) is the default. Rework and hard orders move up to Sol (xhigh). The few dozen yuan left in my MiMo account now sit on pay-as-you-go as a fallback for when OpenAI is unreachable. No more monthly plan.&lt;/p&gt;

&lt;p&gt;I also tried GPT-6.1 Terra (xhigh) on four replayed orders. It used 3 to 4x the tokens Sol (medium) did, so half the token price saved nothing. At my current volume I expect $60 to $100 a month.&lt;/p&gt;

&lt;p&gt;Caveats: the samples are small (87 orders vs 31), the two periods had different work, and MiMo's API was stalling for part of late October, which hurt its pass rate. Treat my numbers as an example of the method, not a verdict.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd suggest
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Compare models by cost per accepted change, including retries, review cost and wall-clock time, not by price per token.&lt;/li&gt;
&lt;li&gt;Before buying a token plan, convert its quota into pay-as-you-go money and compare that with what you actually use.&lt;/li&gt;
&lt;li&gt;Reconcile your own usage logs with the provider's at least once a month.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I also do this for other teams as a fixed-price routing audit: cost per accepted change across your models, a reconciliation of your usage logs against provider data, and a routing recommendation. It's US$1,500. Reach me at &lt;a href="mailto:info@zhuojun.li"&gt;info@zhuojun.li&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Happy to compare notes if you're running something similar.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
    <item>
      <title>90% of my coding agent's rework came from my own work orders</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Thu, 29 Oct 2026 07:04:54 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/90-of-my-coding-agents-rework-came-from-my-own-work-orders-51n4</link>
      <guid>https://dev.to/lizhuojunx86/90-of-my-coding-agents-rework-came-from-my-own-work-orders-51n4</guid>
      <description>&lt;p&gt;&lt;a href="https://dev.to/lizhuojunx86/i-routed-two-weeks-of-coding-to-a-model-25x-cheaper-than-opus-the-model-wasnt-the-slow-part-2ofc"&gt;Four days ago I wrote&lt;/a&gt; that Claude plans my code changes and Xiaomi's MiMo writes them, and that MiMo costs about 25× less for the same tokens. I promised a before-and-after once I'd fixed the slow parts. Here it is, and the "after" got worse.&lt;/p&gt;

&lt;p&gt;Orders created 11 to 23 October: 62 merged, 24 of them on the first round (39%). Orders created 25 to 28 October, after I added an automatic reviewer and a self-review checklist: 14 merged, 2 on the first round (14%). Small sample, and one of those orders took nine rounds on its own. But the direction is clear. A stricter reviewer finds more problems, so more orders go back.&lt;/p&gt;

&lt;p&gt;So this week I stopped asking "how do I review harder" and asked where the problems come from.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should the worker be a subagent at all?
&lt;/h2&gt;

&lt;p&gt;On 22 October Anthropic's Applied AI team &lt;a href="https://claude.com/blog/building-agents-when-to-fold-subagents-into-your-main-agent-loop" rel="noopener noreferrer"&gt;published a post&lt;/a&gt; arguing that one agent loop with skills usually beats an orchestrator plus specialist subagents. They keep a subagent only when one of three things is true: the single loop degrades measurably from context bloat; tasks run in parallel and each needs a fresh context it can throw away; or one agent can't pick the right tool, or its instructions conflict.&lt;/p&gt;

&lt;p&gt;My worker passes the second test. Each order runs in its own git worktree with a fresh context, up to three at once, and the context is discarded when the branch merges. It also passes a test the post doesn't cover: the worker is a different, much cheaper model. Folding it into the Claude loop would put every token at Claude prices.&lt;/p&gt;

&lt;p&gt;I kept it. But the post's first failure mode, "context loss" at the handoff, describes my bill exactly. Everything the worker knows comes from one Markdown work order I write.&lt;/p&gt;

&lt;h2&gt;
  
  
  Whose fault is the rework?
&lt;/h2&gt;

&lt;p&gt;I took 10 orders that came back for rework, across six repos, and pulled the "must fix" list from the first review. That gave 61 items. For each one I asked: did the order say what to do here?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;55 items (90%): the order was silent or ambiguous. A worker following it word for word could still get it wrong. Example: an endpoint that re-reads a file before writing back. The order never said that a 20-second model call sits between the read and the write, so a second click silently overwrote the first.&lt;/li&gt;
&lt;li&gt;6 items: the order was explicit and the worker didn't follow it. Example: the order said full-width colons in a message, the code used ASCII.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I used Claude Sonnet to sort the items and checked one order by hand; it matched. The split is the useful part. Reviewing harder only catches the 90% after a full round has already been spent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Moving the check before the handoff
&lt;/h2&gt;

&lt;p&gt;So now every order gets a "falsifier" pass before it goes out. The idea comes from a prompt someone shared on r/ClaudeAI. I rewrote it for work orders. The model gets only the order and read access to the repo, and it has to return at most seven ranked findings. Each finding quotes the line of the order that triggers it (or says "not mentioned"), gives a concrete input that breaks it, and names the section of the order where the fix belongs. It doesn't write code.&lt;/p&gt;

&lt;p&gt;On the same 10 orders, with no repo access:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Order gaps caught (of 55)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Run 1&lt;/td&gt;
&lt;td&gt;33 (60%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Run 2&lt;/td&gt;
&lt;td&gt;31 (56%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Both runs&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Either run&lt;/td&gt;
&lt;td&gt;39 (71%)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;One run costs about $0.07 and 34 seconds on Sonnet. Two runs disagree a lot, which is why I run it twice. The Anthropic post makes the same point about evals: run each task more than once, because a failure may show up in only one of two runs.&lt;/p&gt;

&lt;p&gt;Compare that with a rework round. From my earlier numbers, a two-round order uses about 9M tokens against 3.6M for a one-round order, plus another review and about 20 minutes of wall-clock.&lt;/p&gt;

&lt;p&gt;I used it on the four implementation orders I sent out today. Every one came back with at least two HIGH findings: a lock that didn't cover the read-modify-write, a half-written JSON line that would swallow the next record, a frontmatter value in quotes that a naive parser would reject. All of them went into the orders before MiMo saw them. Three of the four then passed the automatic reviewer on their first delivery; the fourth needed two more rounds. By that same measure (no feedback round needed), 63% of the merged orders from 11 to 23 October passed, so four orders tell me nothing yet. MiMo's API also stalled all afternoon, which added restarts to every order and makes today's round counts useless.&lt;/p&gt;

&lt;p&gt;The one order I didn't run it on was the eval order itself. It pointed the worker at files that existed in my main checkout but weren't committed, and a fresh worktree can't see uncommitted files. MiMo spent 23 minutes confirming it couldn't read anything. The falsifier flagged the same mistake in a later order.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two more things from the post that applied
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Progressive disclosure.&lt;/strong&gt; The skill that runs my daily publishing (four scheduled runs a day) had grown to 53 KB, and every run loaded all of it. I cut it to a 14 KB core and moved each step's details into files the agent reads only when it reaches that step. Before changing anything, I wrote 12 scenarios with 29 do-or-don't decisions and ran both versions twice. The old version scored 28/29 both times, the new one 29/29 both times. The question the old one got wrong was a case of conflicting instructions. One section said "for dispatching, this section wins", and a newer dispatch skill said otherwise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hard limits belong in tools.&lt;/strong&gt; My rule about never printing credentials lived in the prompt, and it was broken four times in September. A rule broken twice needs a structural fix, not louder wording. It's now a pre-tool hook that blocks &lt;code&gt;cat&lt;/code&gt;, &lt;code&gt;sed -n&lt;/code&gt; and &lt;code&gt;Read&lt;/code&gt; on credential paths before the call runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you run subagents at work
&lt;/h2&gt;

&lt;p&gt;The checklist I'd use on any team's setup:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Count the handoffs. For every subagent, check it against the three conditions above. "Each team owns one" isn't one of them.&lt;/li&gt;
&lt;li&gt;Sort the rework. Pull the last 10 send-backs and split them into "the brief didn't say" and "the worker didn't do". If the first group is large, add a check before the handoff.&lt;/li&gt;
&lt;li&gt;Build 10 golden cases before you touch the architecture, and run each one twice.&lt;/li&gt;
&lt;li&gt;Look for instructions that contradict each other across files. I found two such pairs in my own setup this week.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One person, mostly Python. Ten orders is a small sample.&lt;/li&gt;
&lt;li&gt;The judge and the falsifier are the same model family, so the hit rate may be generous. In production the falsifier also reads the repo, which should catch more.&lt;/li&gt;
&lt;li&gt;I wanted a MiMo-run falsifier as a cheaper comparison. MiMo's API kept stalling today and I cancelled those runs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I do this kind of review for teams as an architecture audit: a 10-case baseline run twice, a keep-or-fold verdict for each subagent against the three conditions, and measured cost and latency before and after. Write to &lt;a href="mailto:info@zhuojun.li"&gt;info@zhuojun.li&lt;/a&gt;. If you've sorted your own rework, I'd like to compare numbers.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>agents</category>
      <category>productivity</category>
    </item>
    <item>
      <title>SEC's API had Apple's pre-market 10-Q at 10:01 ET. This week it reads 06:01. Your cache doesn't.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Wed, 28 Oct 2026 13:11:48 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/secs-api-had-apples-pre-market-10-q-at-1001-et-this-week-it-reads-0601-your-cache-doesnt-1lp7</link>
      <guid>https://dev.to/lizhuojunx86/secs-api-had-apples-pre-market-10-q-at-1001-et-this-week-it-reads-0601-your-cache-doesnt-1lp7</guid>
      <description>&lt;p&gt;From at least mid-September until at least October 22, 2026, &lt;code&gt;acceptanceDateTime&lt;/code&gt; in SEC's submissions JSON (&lt;code&gt;data.sec.gov/submissions/CIK##########.json&lt;/code&gt;) was wrong for a large share of filers, even though every value ends in &lt;code&gt;Z&lt;/code&gt;. On October 28 every file I checked read true UTC. If your backtest cached that field before this week, the cache still holds the wrong values.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three states, one per file
&lt;/h2&gt;

&lt;p&gt;The value was in one of three states, and the whole file shared it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;True UTC.&lt;/strong&gt; Microsoft, Tesla (until October) and Alphabet looked like this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One Eastern offset late&lt;/strong&gt;, +4 h in summer and +5 h in winter. Apple's 10-Q &lt;code&gt;0000320193-26-000020&lt;/code&gt; was accepted at 06:01:02 ET on 2026-07-31, before the open. On October 21 the API returned &lt;code&gt;14:01:02Z&lt;/code&gt;, which is 10:01 ET, half an hour into the session.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Eastern wall time labelled &lt;code&gt;Z&lt;/code&gt;.&lt;/strong&gt; Arena Pharmaceuticals' earnings 8-K of 2016-05-09 was accepted at 16:18:17 ET, after the close. The API returned &lt;code&gt;16:18:17Z&lt;/code&gt;, which reads as 12:18 ET, mid-session. The stock opened 5.1% higher the next day.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Which state a file was in followed SEC's last rebuild of that file, not the company. On October 11 arhancanli compared 450 filings from 25 companies with their index pages: 12 files were right, and 13 were one offset late, including Apple, Nvidia, Amazon, Meta and JPMorgan. shahar-arbor found the third state in files for MMAT, SVB, Heliogen and Bed Bath &amp;amp; Beyond. The full thread is &lt;a href="https://github.com/dgunning/edgartools/issues/1501" rel="noopener noreferrer"&gt;edgartools #1501&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;My own numbers come from a post-earnings-drift audit I ran in September. 43 of 228 timed filings were Eastern time labelled &lt;code&gt;Z&lt;/code&gt;, all from issuers no longer in &lt;code&gt;company_tickers.json&lt;/code&gt;. Read as UTC, 26 filings accepted after the entry day's close would have looked intraday.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a few hours matter
&lt;/h2&gt;

&lt;p&gt;An earnings backtest makes one decision per event: was the release before the open, during the session, or after the close? That decides whether the reaction is in today's open, today's close or tomorrow's open. Four or five hours is enough to move a release across 09:30 or 16:00, and nothing raises an error. In my PEAD backtest, timing alone moved net alpha per trade from 1.21% to about 0.25% (&lt;a href="https://dev.to/lizhuojunx86/my-pead-backtests-edge-fell-from-121-to-025-per-trade-once-i-checked-announcement-times-3k31"&gt;write-up&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed this week
&lt;/h2&gt;

&lt;p&gt;On October 28 at 12:52 UTC I re-read all 228 filings from my audit. All 228 now read true UTC, the 43 included, and none of the 185 that were right in September had moved the other way.&lt;/p&gt;

&lt;p&gt;At 12:55 UTC I checked the 13 files reported as one offset late, plus Microsoft, Tesla and Alphabet: three filings each (the newest, the newest before October 23, and one from February, so both sides of DST). 48 of 48 read true UTC. Apple's 10-Q now says &lt;code&gt;10:01:02Z&lt;/code&gt;, which is right. The last time anyone in the thread saw a late file was October 22.&lt;/p&gt;

&lt;p&gt;I can't tell whether this is a fix or one more rebuild. SEC sends no &lt;code&gt;Last-Modified&lt;/code&gt; or &lt;code&gt;ETag&lt;/code&gt; for these files, so a change can't be dated from outside.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what you stored
&lt;/h2&gt;

&lt;p&gt;Re-fetching won't tell you what your cache holds. Compare each cached value with the filing's &lt;code&gt;-index-headers.html&lt;/code&gt;, which gives the acceptance time in Eastern time and doesn't change:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;re&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;urllib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;
&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;
&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;zoneinfo&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;ZoneInfo&lt;/span&gt;

&lt;span class="n"&gt;UA&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;User-Agent&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Your Name you@example.com&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;  &lt;span class="c1"&gt;# SEC requires a real contact
&lt;/span&gt;&lt;span class="n"&gt;ET&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;UTC&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;ZoneInfo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;America/New_York&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="nc"&gt;ZoneInfo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;UTC&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;accepted_utc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;cik&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;int&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;accession&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://www.sec.gov/Archives/edgar/data/&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;cik&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;/&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
           &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;accession&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;-&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;/&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;accession&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;-index-headers.html&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;html&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;urllib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;urlopen&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;urllib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Request&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;UA&lt;/span&gt;&lt;span class="p"&gt;)).&lt;/span&gt;&lt;span class="nf"&gt;read&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;latin1&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;stamp&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;re&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;search&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;r&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ACCEPTANCE-DATETIME&amp;gt;\s*(\d{14})&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;html&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;group&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;strptime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;stamp&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;%Y%m%d%H%M%S&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tzinfo&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;ET&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;astimezone&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;UTC&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;convention&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;cached&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;truth&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;strptime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;cached&lt;/span&gt;&lt;span class="p"&gt;[:&lt;/span&gt;&lt;span class="mi"&gt;19&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;%Y-%m-%dT%H:%M:%S&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tzinfo&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;UTC&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;truth&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;total_seconds&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;3600&lt;/span&gt;
    &lt;span class="n"&gt;offset&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;truth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;astimezone&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ET&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;utcoffset&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;total_seconds&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;3600&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nf"&gt;abs&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hours&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mf"&gt;0.01&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;utc&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nf"&gt;abs&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;offset&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mf"&gt;0.01&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;one offset late&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nf"&gt;abs&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;offset&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mf"&gt;0.01&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Eastern wall time labelled Z&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;other (&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;hours&lt;/span&gt;&lt;span class="si"&gt;:&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt; h)&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;

&lt;span class="n"&gt;truth&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;accepted_utc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;320193&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;0000320193-26-000020&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;truth&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;                                          &lt;span class="c1"&gt;# 2026-07-31 10:01:02+00:00
&lt;/span&gt;&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;convention&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;2026-07-31T14:01:02.000Z&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;truth&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;  &lt;span class="c1"&gt;# one offset late
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is one small request per filing. At SEC's limit of 10 requests a second, 10,000 filings take under 20 minutes. Cache the result, since the index page doesn't change.&lt;/p&gt;

&lt;p&gt;For new work, read the time from the index headers and keep the JSON value next to it. edgartools plans the same for 6.1 (&lt;code&gt;filing.accepted_at&lt;/code&gt;). For earnings 8-Ks, &lt;a href="https://github.com/lizhuojunx86/earnings-session" rel="noopener noreferrer"&gt;earnings-session&lt;/a&gt; (MIT, &lt;code&gt;pip install earnings-session&lt;/code&gt;) does this and records which convention the JSON used for each filing. Disclosure: I maintain it.&lt;/p&gt;

&lt;p&gt;If your cache turns up a pattern different from these three, I'd like to see it.&lt;/p&gt;

</description>
      <category>python</category>
      <category>finance</category>
      <category>datascience</category>
      <category>opensource</category>
    </item>
    <item>
      <title>My backtest booked 2026 prices into 2019, and nothing raised an error</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Tue, 27 Oct 2026 23:17:05 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/my-backtest-booked-2026-prices-into-2019-and-nothing-raised-an-error-dco</link>
      <guid>https://dev.to/lizhuojunx86/my-backtest-booked-2026-prices-into-2019-and-nothing-raised-an-error-dco</guid>
      <description>&lt;p&gt;In June I ran a backtest of a 10-K text-change signal, the Lazy Prices idea: companies whose annual reports change a lot tend to do worse afterwards. S&amp;amp;P 500 names, monthly rebalancing, net of costs. It looked good. In October, before taking it further, I tried to reproduce the headline from the stored code and data, and 81 of 82 months came out different.&lt;/p&gt;

&lt;p&gt;The cause was one function. To compute a month's return, it looked up the first price bar on or after the start of the window and the first one on or after its end, with no limit on how far away that bar could be. For a ticker with no price history around the target, the lookup quietly returned a bar from months or years later.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it did to the numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;719 of 3,282 name-months (21.9%), across 56 tickers, were priced from bars outside their month. AAPL, AMGN and COST were among them.&lt;/li&gt;
&lt;li&gt;For 34 of those tickers, the price table only started in December 2025. So the June 2026 run booked 2026 prices into months from 2019 to 2025.&lt;/li&gt;
&lt;li&gt;Every number from that backtest is void: the headline Sharpe, the information coefficient, the out-of-sample check. Not one line of code raised an error.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why nothing complained
&lt;/h2&gt;

&lt;p&gt;The lookup did exactly what it was written to do. A missing bar isn't an exception, it's a gap, and "the next available bar" fills it. The returns looked like returns: no NaNs, no zeros, nothing extreme enough to stand out in a monthly series. It only showed when I re-ran the same code three months later. The price table had gained history in the meantime, the panel no longer matched, and tracing the mismatch led to the lookup.&lt;/p&gt;

&lt;p&gt;It's the same family of mistake as the one in &lt;a href="https://dev.to/lizhuojunx86/my-pead-backtests-edge-fell-from-121-to-025-per-trade-once-i-checked-announcement-times-3k31"&gt;my earlier post about earnings release times&lt;/a&gt;: the backtest used information from after the moment it claims to act. There it was the release session. Here it was the price bar itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix
&lt;/h2&gt;

&lt;p&gt;Bound every lookup. The corrected function only takes entry and exit bars within 7 calendar days of their targets, drops the name-month otherwise, and reports how many it dropped. A missing price should cost you a data point, not borrow one from the future.&lt;/p&gt;

&lt;p&gt;If you use pandas, &lt;code&gt;merge_asof&lt;/code&gt; has the same trap. Without &lt;code&gt;tolerance&lt;/code&gt;, it joins the nearest bar at any distance.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check your own backtest
&lt;/h2&gt;

&lt;p&gt;I added this check to earnings-session, the small tool from the first post. Version 0.2.0 has a &lt;code&gt;bars&lt;/code&gt; command that runs offline:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;earnings-session
earnings-session bars trades.csv &lt;span class="nt"&gt;--prices&lt;/span&gt; prices.csv &lt;span class="nt"&gt;-o&lt;/span&gt; checked.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;trades.csv&lt;/code&gt; needs &lt;code&gt;ticker&lt;/code&gt; and &lt;code&gt;entry_date&lt;/code&gt;, and optionally &lt;code&gt;exit_date&lt;/code&gt; and &lt;code&gt;return&lt;/code&gt;. &lt;code&gt;prices.csv&lt;/code&gt; is the price table your backtest read, with &lt;code&gt;ticker&lt;/code&gt; and &lt;code&gt;date&lt;/code&gt;. For each trade it finds the bar a "first bar on or after" rule would take, measures how far that bar sits from its target in NYSE trading days, and flags the row:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;history_break&lt;/code&gt;: the bar is more than 250 trading days away, so it belongs to another stretch of history, maybe another company on a reused ticker.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;entry_gap&lt;/code&gt; / &lt;code&gt;exit_gap&lt;/code&gt;: the bar is more than &lt;code&gt;--max-gap&lt;/code&gt; trading days away (default 0).&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;no_bar&lt;/code&gt;: the ticker isn't in the price table at all.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;early_bar&lt;/code&gt;: your trade file records the bar the backtest used, and it's before the entry date, so the trade was priced before the day it claims.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The summary also splits the returns. If flagged rows are a minority but carry most of the result, the backtest is measuring its lookup, not the signal. &lt;code&gt;--fail-on-flag&lt;/code&gt; exits 1, so the check can run in CI next to your tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  A checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Put a distance limit on every price lookup, and count what the limit drops.&lt;/li&gt;
&lt;li&gt;Before trusting a result, measure the distance between each target date and the bar actually used.&lt;/li&gt;
&lt;li&gt;Compare the returns of misdated rows with the rest. A misdated minority carrying the result is the fingerprint.&lt;/li&gt;
&lt;li&gt;Check against the price table the backtest actually read. A table that was filled in later hides the problem.&lt;/li&gt;
&lt;li&gt;Watch tickers whose history starts late or has long gaps: new listings, delistings, reused tickers.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I'm re-running the corrected backtest under the thresholds I registered before touching the data. Whatever it shows, I'll take the new number over the old one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update, 2026-10-28:&lt;/strong&gt; the corrected run is done, and it failed the gate I registered. Long-short net Sharpe is −0.07 (t −0.18) and the monthly IC is −0.008. The long-only version made money mostly from market beta and trailed SPY by about 4.8% a year. The old headline Sharpe of 1.54 came from the misdated rows.&lt;/p&gt;

&lt;p&gt;Code: &lt;a href="https://github.com/lizhuojunx86/earnings-session" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; · &lt;a href="https://pypi.org/project/earnings-session/" rel="noopener noreferrer"&gt;PyPI&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Questions are welcome in the comments. Happy to share what I know.&lt;/p&gt;

</description>
      <category>python</category>
      <category>finance</category>
      <category>datascience</category>
      <category>opensource</category>
    </item>
    <item>
      <title>My PEAD backtest's edge fell from 1.21% to 0.25% per trade once I checked announcement times against SEC filings</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Tue, 27 Oct 2026 13:31:49 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/my-pead-backtests-edge-fell-from-121-to-025-per-trade-once-i-checked-announcement-times-3k31</link>
      <guid>https://dev.to/lizhuojunx86/my-pead-backtests-edge-fell-from-121-to-025-per-trade-once-i-checked-announcement-times-3k31</guid>
      <description>&lt;p&gt;My post-earnings-drift backtest (long-only, US small and micro caps) showed 1.21% net alpha per trade and a Sharpe of 2.35 across 8 slots in July. I'd swept more than 20,000 parameter combinations and was close to taking it live. Then I timed every earnings release with the SEC's 8-K acceptance timestamps. Under the live rules, the edge fell to about 0.25% per trade (t = 1.6), and to zero at my high-cost assumption.&lt;/p&gt;

&lt;p&gt;The signal wasn't the problem. The release-session labels were. Many events my data vendor tagged as before-market-open (BMO) were actually released after the close, and for the half of events with no session label at all, the backtest assumed BMO. About six in ten of those were reported after the close: the backtest bought at the open, and the earnings came out that evening.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the session label matters
&lt;/h2&gt;

&lt;p&gt;In a PEAD backtest, the label decides the entry. A BMO release means you buy at that day's open; an after-market-close (AMC) release means you buy the next morning. Get the label wrong and the backtest holds the stock before the news is public, then books the overnight gap that follows, which no live trader could have captured.&lt;/p&gt;

&lt;p&gt;In my event set, roughly half the events had no usable session label (blank, or "during market hours"). The engine treated all of them as BMO. That default looks harmless until a big share of those events turn out to be AMC.&lt;/p&gt;

&lt;p&gt;Live trading isn't affected. A live system waits for the EPS print before it can signal, so it can't buy before the release. The damage is to the backtest, which is exactly the evidence you use to decide whether to go live.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method: time each event with the 8-K acceptance time
&lt;/h2&gt;

&lt;p&gt;US issuers file an 8-K for earnings, under Item 2.02, and EDGAR records when each filing was accepted, to the second. That timestamp is an upper bound on the release time: the press release can come earlier, never later.&lt;/p&gt;

&lt;p&gt;For each event:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Find the filing. Take a window in Eastern dates, from the trading day before the event to the trading day after the entry, and pick the original 8-K with Item 2.02 closest to the event (no 8-K/A). Don't use filingDate: anything accepted after 17:30 gets the next business day's filingDate.&lt;/li&gt;
&lt;li&gt;Assign the session. Before 9:30 ET is pre-market, 9:30 to the close is intraday, and the close or later is after-hours. The close is 16:00, or 13:00 on half days such as the day after Thanksgiving. Weekend and holiday acceptances roll to the previous trading day's after-hours.&lt;/li&gt;
&lt;li&gt;Compare with the backtest's entry. An 8-K accepted before the open on the entry day is "before entry", and filing lags can't change that. One accepted after the close of the entry day, or later, is "after entry": unless the press release beat the 8-K by a full session, that trade is look-ahead.&lt;/li&gt;
&lt;li&gt;No Item 2.02? Look for other 8-Ks, a 10-Q or a 10-K in the same window. If that fails, classify from the price reaction (the entry-day intraday move and the overnight gap), but only call an event BMO when the Wilson lower bound on precision is at least 0.95. Otherwise leave it unresolved.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The first pass was a stratified sample (by year and dollar volume) of 200 events with unknown timing, plus 40 BMO-labeled and 40 AMC-labeled controls; 95 of the 200 matched an Item 2.02 8-K. The second pass timed all 3,203 unknown events (7,203 requests, zero failures) and every one of the 3,585 known-session trades.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result 1: most "unknown" events were reported after the close
&lt;/h2&gt;

&lt;p&gt;Of the 95 matched unknown events, 56 (58.9%, 95% CI 48.9–68.3%) had an 8-K accepted after the backtest's entry-day close. Eight were intraday, and only 31 (32.6%) were clearly before the open. Adjusting for late 8-Ks, using the BMO control group's lag rate, puts the look-ahead share at about 63%.&lt;/p&gt;

&lt;p&gt;The returns tell the same story. For the 56 after-entry trades, the opening gap the backtest saw had a median of just 0.55%, an ordinary pre-announcement day, and the return sat in the overnight leg (entry-day close to next open), averaging +2.45%. The 31 before-entry trades had a median gap of 3.51% and only +0.51% overnight.&lt;/p&gt;

&lt;p&gt;Re-booking those 56 trades at the next day's open, under the same rules, took their net alpha from +2.73% to −0.20%. The share also varied by period and liquidity: 70.4% after-entry in 2016–2020 versus 43.9% from 2021 on, and 70.0% for names trading over $20M a day versus 37.9% for $1–5M.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result 2: known labels are wrong too, and they change
&lt;/h2&gt;

&lt;p&gt;A label isn't reliable just because it's filled in. Of 1,222 AMC-labeled trades, 1,210 had their 8-K after the close, which is fine. Of 2,363 BMO-labeled trades, 743 had their 8-K after the close, 709 of them on the event day itself.&lt;/p&gt;

&lt;p&gt;Worse, labels get rewritten. Of the 824 trades that needed correcting to AMC, 653 had been labeled AMC when I pulled the data in July; by the October pull, the vendor showed BMO, while EDGAR says after the close. The same event downloaded three months apart gives a different backtest.&lt;/p&gt;

&lt;p&gt;Another 163 were labeled BMO both times, and 104 of those had an 8-K filed days after the event. They may be genuine pre-market releases with a late 8-K. I can't tell from the data I have, so they stay as a range. (I found the rewrite in my own database: my loader overwrote stored values with the latest pull, which imported the vendor's changes into history. Decision inputs for past earnings are now frozen.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Result 3: what's left of the edge
&lt;/h2&gt;

&lt;p&gt;After re-timing everything, net alpha per trade dropped from 1.21% to just over 0.2%. In the last step, events that still couldn't be timed were treated as AMC. Their returns were concentrated overnight (+0.09% intraday, +1.66% overnight), which is what AMC releases look like, so this lower bound is the credible estimate.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scenario&lt;/th&gt;
&lt;th&gt;Net alpha per trade (mid cost)&lt;/th&gt;
&lt;th&gt;t&lt;/th&gt;
&lt;th&gt;8-slot Sharpe (mid cost)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Before correction: July data, deduplicated, base rule&lt;/td&gt;
&lt;td&gt;1.21%&lt;/td&gt;
&lt;td&gt;5.19&lt;/td&gt;
&lt;td&gt;2.35&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Known and unknown sessions corrected with EDGAR, base rule&lt;/td&gt;
&lt;td&gt;0.49%&lt;/td&gt;
&lt;td&gt;2.42&lt;/td&gt;
&lt;td&gt;1.08&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remaining untimed events as AMC, base rule&lt;/td&gt;
&lt;td&gt;0.21%&lt;/td&gt;
&lt;td&gt;1.03&lt;/td&gt;
&lt;td&gt;0.49&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remaining untimed events as AMC, live rule&lt;/td&gt;
&lt;td&gt;0.25%&lt;/td&gt;
&lt;td&gt;1.61&lt;/td&gt;
&lt;td&gt;0.80&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The base rule requires an opening gap within ±3%; the live rule only caps the gap at +10%. At the high-cost band, the live-rule row is 0.00% with a Sharpe of 0.22 and a max drawdown of about −51%. Costs come in four bands (low, mid, high, stress) and include commission, half the spread and square-root impact.&lt;/p&gt;

&lt;p&gt;Of the 720 events still untimed after the second pass, other filings in the same window timed 220. The price-reaction classifier reached an AUC of 0.95, but its BMO precision topped out at 0.90–0.95 in the highest-score bins, short of the gate, so under the strict rule it called none of them BMO.&lt;/p&gt;

&lt;p&gt;What's left isn't statistically significant, and paper trading can't settle it. With a per-trade standard deviation of about 7.2%, telling 0.25% apart from zero takes roughly 3,300 trades. At a few hundred trades a year, that's years. I've shelved the planned live switch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two more traps
&lt;/h2&gt;

&lt;p&gt;EDGAR's acceptanceDateTime wasn't always UTC, at least when I checked in September 2026. Of 228 timestamped filings I checked against the filing index pages, 185 were true UTC. The other 43 were Eastern local time with a "Z" suffix, and all 43 came from issuers no longer on the SEC's current ticker list. When I rechecked seven of them on October 27, all seven came back as true UTC, so the SEC seems to have fixed at least part of the data since.&lt;/p&gt;

&lt;p&gt;Read as UTC, those times landed 4 to 5 hours early: 26 of my 86 "after entry" calls would have become "intraday". Data that changed once can change again, so use the "Accepted" time (Eastern) on the filing index page, especially for delisted companies.&lt;/p&gt;

&lt;p&gt;My event matrix had duplicate rows. When several earnings records share a timestamp and ticker, joining on (time, ticker) fans out into multiple rows: 895 of 7,053 trades were duplicates, and 122 events traded twice, once as BMO and once as AMC, because their source rows disagreed. The effect on the mean was small, but it inflates trade counts and portfolio-level turnover.&lt;/p&gt;

&lt;h2&gt;
  
  
  A checklist for event backtests
&lt;/h2&gt;

&lt;p&gt;The cheapest check is timing 100 of your events against 8-Ks. It takes an afternoon and tells you whether your backtest has this problem.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Don't let vendor BMO/AMC labels set your entries until you've measured their error rate on a sample.&lt;/li&gt;
&lt;li&gt;Don't default unlabeled events to BMO. Treat them as AMC (next open), or report them separately with their share of the returns.&lt;/li&gt;
&lt;li&gt;Split each trade's return into entry-day intraday, overnight and next-day intraday. A return concentrated in the overnight leg after entry is the fingerprint of look-ahead.&lt;/li&gt;
&lt;li&gt;Don't assume acceptanceDateTime is UTC. Check it against the "Accepted" time on the index page.&lt;/li&gt;
&lt;li&gt;Store first-seen values. Vendors revise history: in 2,163 comparable earnings records in my database, the first-seen EPS actual differed from the final value 41.4% of the time, and 15.3% of the changes were large enough to flip a trade decision.&lt;/li&gt;
&lt;li&gt;Deduplicate before you count trades or compute a Sharpe.&lt;/li&gt;
&lt;li&gt;Redo the sample-size math after correcting. Required trades scale with the inverse square of the edge: going from 1.1% to 0.3% means about 13 times as many trades.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The tool
&lt;/h2&gt;

&lt;p&gt;I've packaged the timing rules as earnings-session, a small open-source Python tool: &lt;code&gt;pip install earnings-session&lt;/code&gt;. Give it a ticker and an announcement date, and it returns the 8-K acceptance time (Eastern), the session it assigns, the filing it used and why, and whether a backtest buying at the open got in before or after the filing. Run it over a CSV of events and it prints a vendor-label vs. EDGAR table with Wilson intervals, so you can check your vendor's labels row by row.&lt;/p&gt;

&lt;p&gt;SEC asks automated clients to identify themselves, so set a User-Agent with your name and email first. It makes about 3 requests per event, 5 per second by default, and caches responses locally. The price-reaction step from the method above isn't in v0.1: on my data no threshold cleared the 0.95 gate. The full rules and the reasons behind them are in &lt;a href="https://github.com/lizhuojunx86/earnings-session/blob/main/METHOD.md" rel="noopener noreferrer"&gt;METHOD.md&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Code: &lt;a href="https://github.com/lizhuojunx86/earnings-session" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; · &lt;a href="https://pypi.org/project/earnings-session/" rel="noopener noreferrer"&gt;PyPI&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The numbers above come from my own backtests and vendor data, which I can't publish. The tool uses only public SEC data, so you can run it on your own event table.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limitations
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The 8-K acceptance time only bounds the release from above. A press release that beats the 8-K can turn a true BMO into an apparent AMC. The 163 weak-evidence events sit here, which is why the result is a range, not a single number.&lt;/li&gt;
&lt;li&gt;500 events couldn't be timed at all and were treated as AMC for the lower bound.&lt;/li&gt;
&lt;li&gt;This is one strategy family, one data vendor, and US small and micro caps (roughly $50M to $2B market cap). Error rates will differ for other vendors and for large caps, so don't carry the numbers over directly.&lt;/li&gt;
&lt;li&gt;Costs are estimated in four bands. Where live costs actually fall still has to be measured from real fills.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Questions are welcome in the comments. Happy to share what I know.&lt;/p&gt;

</description>
      <category>python</category>
      <category>finance</category>
      <category>datascience</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I routed two weeks of coding to a model 25x cheaper than Opus. The model wasn't the slow part.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Sun, 25 Oct 2026 00:22:35 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/i-routed-two-weeks-of-coding-to-a-model-25x-cheaper-than-opus-the-model-wasnt-the-slow-part-2ofc</link>
      <guid>https://dev.to/lizhuojunx86/i-routed-two-weeks-of-coding-to-a-model-25x-cheaper-than-opus-the-model-wasnt-the-slow-part-2ofc</guid>
      <description>&lt;p&gt;For two weeks, Claude planned and reviewed my code changes and Xiaomi's MiMo-V2.6-Pro wrote them. That was 95 work orders across 14 of my repos, and 62 of them merged. At list prices, MiMo's side of those 62 changes cost $14.22. The same tokens at Claude Opus 5.5 prices come to $355.&lt;/p&gt;

&lt;p&gt;The catch is time. A merged change took 52 minutes from order to merge (median). MiMo was working for less than half of that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;A dispatcher I wrote (about 10,000 lines of stdlib Python) runs each order in its own git worktree and branch, inside a macOS seatbelt sandbox that can only write to that worktree. Claude writes the order, MiMo implements it and runs the project's checks, Claude reviews the diff and either sends it back with feedback or merges it locally. Nothing gets pushed without me.&lt;/p&gt;

&lt;p&gt;Every order leaves a state file and the worker's full event log, with timestamps and token counts for each model call. All the numbers below come from those files, for orders created 11 to 23 October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the time went
&lt;/h2&gt;

&lt;p&gt;I could rebuild the full timeline for 33 merged orders (four more sat overnight and I left them out).&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Share of wall-clock&lt;/th&gt;
&lt;th&gt;Median&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Waiting in the queue&lt;/td&gt;
&lt;td&gt;5%&lt;/td&gt;
&lt;td&gt;0.1 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MiMo working&lt;/td&gt;
&lt;td&gt;49%&lt;/td&gt;
&lt;td&gt;30.7 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Between rounds (review, feedback, waiting)&lt;/td&gt;
&lt;td&gt;27%&lt;/td&gt;
&lt;td&gt;6.4 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Last round finished → merged&lt;/td&gt;
&lt;td&gt;20%&lt;/td&gt;
&lt;td&gt;11.2 min&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The orders that passed on the first round make it plain. MiMo worked for 16 minutes (median) and the order took 42 minutes end to end.&lt;/p&gt;

&lt;p&gt;Most of the extra 26 minutes is the orchestrator not looking. Its instructions said to check the queue with &lt;code&gt;sleep 595&lt;/code&gt;, then review, then merge. The long interval was there to save Claude tokens. It also left up to ten minutes of dead time every time a worker finished. The merge step adds more: it rebases onto whatever landed in the meantime and reruns the full test suite.&lt;/p&gt;

&lt;p&gt;None of this is the model's fault. It's plumbing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is the model itself slower?
&lt;/h2&gt;

&lt;p&gt;Less than I expected. I compared MiMo's turns with Claude Opus 5.5 turns from my own Claude Code transcripts. They're different tasks, so read this as a rough comparison, not a benchmark.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Per model call&lt;/th&gt;
&lt;th&gt;MiMo-V2.6-Pro&lt;/th&gt;
&lt;th&gt;Claude Opus 5.5&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Calls measured&lt;/td&gt;
&lt;td&gt;6,640&lt;/td&gt;
&lt;td&gt;4,537&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seconds per call, median&lt;/td&gt;
&lt;td&gt;6.7&lt;/td&gt;
&lt;td&gt;7.9&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seconds per call, mean&lt;/td&gt;
&lt;td&gt;21.8&lt;/td&gt;
&lt;td&gt;13.2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Output speed&lt;/td&gt;
&lt;td&gt;47 tok/s&lt;/td&gt;
&lt;td&gt;81 tok/s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Context per call, median&lt;/td&gt;
&lt;td&gt;153K&lt;/td&gt;
&lt;td&gt;467K&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The typical call is as fast. The slow ones are slower, which pulls the mean up. A MiMo attempt ran 37 calls and 15 minutes (median).&lt;/p&gt;

&lt;p&gt;The context column matters later. MiMo starts every order from a fresh worktree, so it carries about a third of the context my long Claude sessions do.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real gap: rework
&lt;/h2&gt;

&lt;p&gt;Only 24 of the 62 merged orders (39%) went through on the first round. The rest needed one to six more. Each round means another attempt, another review and another wait, and the token bill climbs fast:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Rounds to merge&lt;/th&gt;
&lt;th&gt;Orders&lt;/th&gt;
&lt;th&gt;Median tokens&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;3.6M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;td&gt;8.9M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;14.8M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4 or more&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;31.0M&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;I read the review feedback that sent orders back. Nearly all of it falls into five groups:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Failing silently: a missing column, a join that matched zero rows or a button that wasn't found, all treated as success.&lt;/li&gt;
&lt;li&gt;Data edge cases: duplicate rows, a date that's &lt;code&gt;object&lt;/code&gt; on one side and &lt;code&gt;str&lt;/code&gt; on the other, and tickers like &lt;code&gt;NA&lt;/code&gt; and &lt;code&gt;NULL&lt;/code&gt; that pandas quietly reads as NaN.&lt;/li&gt;
&lt;li&gt;Tests that can't fail. One asserted that a static header string was present in the output. Another wrote into the repo's real output folder. One took 113 seconds against a 60-second limit.&lt;/li&gt;
&lt;li&gt;New behaviour with no test, or a runbook left describing the old behaviour.&lt;/li&gt;
&lt;li&gt;Matching too loosely: a substring check for &lt;code&gt;selected&lt;/code&gt; that also hits &lt;code&gt;unselected&lt;/code&gt;, or "click the first OK button on the page".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of these are hard to get right. They weren't in the order, and the worker didn't go looking for them. A stronger model goes looking more often. That's most of what you pay Claude for.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cost math
&lt;/h2&gt;

&lt;p&gt;Here's the token mix across the 62 merged orders: 97.8% cache reads, 0.56% output. An agent re-reads its whole context on every call, so the token count is roughly calls × context size. It has little to do with how much code gets written.&lt;/p&gt;

&lt;p&gt;That makes the cache-read price the one to compare, and the headline price misleads:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Per 1M tokens&lt;/th&gt;
&lt;th&gt;MiMo-V2.6-Pro&lt;/th&gt;
&lt;th&gt;Claude Opus 5.5&lt;/th&gt;
&lt;th&gt;Ratio&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Input&lt;/td&gt;
&lt;td&gt;$0.435&lt;/td&gt;
&lt;td&gt;$4.00&lt;/td&gt;
&lt;td&gt;9×&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cache read&lt;/td&gt;
&lt;td&gt;$0.0036&lt;/td&gt;
&lt;td&gt;$0.20&lt;/td&gt;
&lt;td&gt;56×&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Output&lt;/td&gt;
&lt;td&gt;$0.87&lt;/td&gt;
&lt;td&gt;$20.00&lt;/td&gt;
&lt;td&gt;23×&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;On my mix the blended ratio is 25×. A merged change cost MiMo $0.17 at list price (median) against $3.83 for the same tokens at Opus prices. Even the orders that took four or more rounds stayed far cheaper than handing the job to Claude. And Claude doing the work inside my planning session would carry three times the context per call, so its real bill would be higher still.&lt;/p&gt;

&lt;p&gt;I pay for both through subscriptions, not per token, so list prices are a yardstick here, not my invoice. Xiaomi's Token Plan page doesn't say how cache hits count against the monthly quota. Check that before you rely on a ratio.&lt;/p&gt;

&lt;p&gt;The money that actually leaks is on the orchestrator side. Every time Claude wakes up to poll, it re-reads its own large context. Ten polls on a 300K-token session is 3M Claude tokens spent on checking whether anything happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm changing
&lt;/h2&gt;

&lt;p&gt;Three changes, all dispatched to MiMo this morning (yes, through the same queue):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;code&gt;wait&lt;/code&gt; command that blocks until an order changes state and returns at once. It's read-only, so the orchestrator can run it over a mounted path from a VM. That replaces &lt;code&gt;sleep 595&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;An automatic review as soon as an order's checks pass, run by Claude Sonnet in headless restricted mode. That means no shell, file reads confined to the review worktree and no MCP servers. The verdict is waiting by the time the orchestrator looks.&lt;/li&gt;
&lt;li&gt;A self-review section in every implementation prompt built from the five groups above, plus an order template with a mandatory "Failure modes" section. Cheap tokens make a self-check worth running.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two of the three merged after two review rounds. The reviewer change took nine. It runs outside the sandbox, and for four rounds in a row a reviewer found another way a file planted in the repo could get executed through &lt;code&gt;PATH&lt;/code&gt;. In the end I dropped the &lt;code&gt;PATH&lt;/code&gt; lookup instead of patching it again. That one order used 127M tokens, about $1.02 at MiMo list prices. At Opus prices the same tokens would have cost more than all 62 orders above did on MiMo.&lt;/p&gt;

&lt;p&gt;The aim is to get first-round merges from 39% to about 60% and take 20 to 25 minutes off a typical order. I'll post the before and after once there are enough orders to compare.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One person, 14 repos, two weeks, mostly Python. Your mix of work will differ.&lt;/li&gt;
&lt;li&gt;The Claude timing comes from different tasks than MiMo's, so it says something about speed and nothing about quality.&lt;/li&gt;
&lt;li&gt;Rounds are counted from the worker's event logs. The wall-clock breakdown covers the 33 orders with complete timestamps.&lt;/li&gt;
&lt;li&gt;Prices are list prices checked on 25 October 2026: Xiaomi's rates as listed on OpenRouter, Anthropic's from its pricing page.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're splitting work between a planner model and a cheaper worker, measure the gaps between steps before you shop for a faster model. I do this kind of measurement as a routing audit (&lt;a href="mailto:info@zhuojun.li"&gt;info@zhuojun.li&lt;/a&gt;). If you've measured your own split, I'd like to compare numbers.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>agents</category>
      <category>productivity</category>
    </item>
    <item>
      <title>I moved 432 Cowork tasks to a new Claude account. Claude Code deleted 13 of my transcripts on the way.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Fri, 23 Oct 2026 05:23:44 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/i-moved-432-cowork-tasks-to-a-new-claude-account-claude-code-deleted-13-of-my-transcripts-on-the-1d0i</link>
      <guid>https://dev.to/lizhuojunx86/i-moved-432-cowork-tasks-to-a-new-claude-account-claude-code-deleted-13-of-my-transcripts-on-the-1d0i</guid>
      <description>&lt;p&gt;This week I retired one Claude account and moved to another on the same Mac. The old account had 432 Cowork tasks, 10 Projects, 39 scheduled tasks, 26 memory files and 28 Claude Code sessions. The account data export covers chats. I couldn't find a way to export what Cowork keeps on the machine: Projects, project memory and scheduled tasks.&lt;/p&gt;

&lt;p&gt;So I went looking on disk. Everything was there. Three things still went wrong, and one of them cost me data. The scripts I wrote along the way are now a small open-source tool, &lt;a href="https://github.com/lizhuojunx86/carryover" rel="noopener noreferrer"&gt;carryover&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where things live
&lt;/h2&gt;

&lt;p&gt;None of this is documented. It's what the macOS desktop app wrote through October 2026.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What&lt;/th&gt;
&lt;th&gt;Where&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Claude Code sessions&lt;/td&gt;
&lt;td&gt;&lt;code&gt;~/.claude/projects/&amp;lt;encoded-path&amp;gt;/&amp;lt;session&amp;gt;.jsonl&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Code memory&lt;/td&gt;
&lt;td&gt;&lt;code&gt;~/.claude/projects/&amp;lt;encoded-path&amp;gt;/memory/*.md&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cowork tasks&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;~/Library/Application Support/Claude/local-agent-mode-sessions/&amp;lt;account&amp;gt;/&amp;lt;org&amp;gt;/local_&amp;lt;id&amp;gt;.json&lt;/code&gt; (metadata) and &lt;code&gt;local_&amp;lt;id&amp;gt;/audit.jsonl&lt;/code&gt; (transcript)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cowork task output&lt;/td&gt;
&lt;td&gt;&lt;code&gt;local_&amp;lt;id&amp;gt;/outputs/&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cowork Projects&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;spaces.json&lt;/code&gt; (name, folders, instructions) and &lt;code&gt;spaces/&amp;lt;id&amp;gt;/memory/&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cowork global memory&lt;/td&gt;
&lt;td&gt;&lt;code&gt;agent/memory/&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scheduled tasks&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;scheduled-tasks.json&lt;/code&gt;, with each prompt in &lt;code&gt;~/Documents/Claude/Scheduled/&amp;lt;task&amp;gt;/SKILL.md&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Claude Code history isn't tied to the login. On the same machine, the new account can &lt;code&gt;claude --resume&lt;/code&gt; an old session and carry on. Cowork is per account: the new account starts with an empty sidebar, no Projects and no scheduled tasks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Problem 1: Claude Code deletes old transcripts
&lt;/h2&gt;

&lt;p&gt;Halfway through the move, Claude Code started once and 13 of my transcripts disappeared. All of them were from September 19 to 21.&lt;/p&gt;

&lt;p&gt;It's a setting. The &lt;a href="https://code.claude.com/docs/en/data-usage" rel="noopener noreferrer"&gt;data usage docs&lt;/a&gt; say Claude Code keeps transcripts in &lt;code&gt;~/.claude/projects/&lt;/code&gt; for 30 days by default, and &lt;code&gt;cleanupPeriodDays&lt;/code&gt; changes that. I had never set it. (Sessions started from the desktop app or Cowork are exempt by default.)&lt;/p&gt;

&lt;p&gt;My last Time Machine backup was from May. The only copy left is a local snapshot macOS took on October 9. If you use Claude Code from the terminal, add this to &lt;code&gt;~/.claude/settings.json&lt;/code&gt; today, whether or not you plan to switch accounts:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"cleanupPeriodDays"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3650&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Problem 2: rebuilt tasks can't read their own prompts
&lt;/h2&gt;

&lt;p&gt;The 39 scheduled tasks keep their prompts as files under &lt;code&gt;~/Documents/Claude/Scheduled/&lt;/code&gt;. I recreated the tasks in the new account and pointed them at those files, then found the tasks couldn't open them. Cowork treats &lt;code&gt;~/Documents/Claude&lt;/code&gt; as its own folder and keeps sessions out of it.&lt;/p&gt;

&lt;p&gt;The fix was dull: copy all 62 prompt folders (39 registered, 23 that no task pointed at any more) to a normal folder and point the tasks there. Also, 12 of the 39 had been moved to the cloud by the app in September and October. Those cloud copies stay with the old account and need rebuilding like the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Problem 3: transcripts are full of secrets
&lt;/h2&gt;

&lt;p&gt;My first idea was to copy the whole Cowork folder somewhere safe. Then I opened a metadata file. Each one also holds the full system prompt, connector configs with server URLs, and the tools I had approved. You don't want that in a backup you might share.&lt;/p&gt;

&lt;p&gt;The transcripts were worse. When I ran the finished tool on my own data, it masked 78 strings. 52 of them were API keys and bearer tokens, most inside &lt;code&gt;curl&lt;/code&gt; and &lt;code&gt;docker run -e&lt;/code&gt; commands from debugging sessions months ago. They had been sitting in plain-text JSON the whole time. If you have used Cowork or Claude Code for a while, assume the same about yours, and rotate whatever you find.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tool
&lt;/h2&gt;

&lt;p&gt;carryover does two things.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;carryover scan&lt;/code&gt; lists what is on disk and warns about the three problems above: how many transcripts the 30-day cleanup will take this week, which prompts live under &lt;code&gt;~/Documents/Claude&lt;/code&gt;, which folders no longer exist, and which tasks were already moved to the cloud. It writes nothing.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;carryover export ~/somewhere&lt;/code&gt; builds a folder you can open in any editor:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;condensed transcripts (your prompts and Claude's replies, no tool noise) for every Claude Code session and Cowork task&lt;/li&gt;
&lt;li&gt;memory, global and per project&lt;/li&gt;
&lt;li&gt;Cowork output files, copied as-is&lt;/li&gt;
&lt;li&gt;one &lt;code&gt;RESTORE.md&lt;/code&gt; per Project: name, folders, instructions, and a first message for the new Project that tells Claude to read the old memory, check it against the current state of the folders, and keep only what still holds&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;TASKS.md&lt;/code&gt; with every scheduled task's schedule, folders, last run and prompt&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;INDEX.md&lt;/code&gt; and a &lt;code&gt;manifest.json&lt;/code&gt; that records every file written and every file skipped&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On my machine, without output files, the export took 9 seconds and wrote 1,198 files. Recreating a Project from its restore pack is four pastes.&lt;/p&gt;

&lt;p&gt;A few rules I held it to. It only opens source files for reading, and it refuses an output folder inside any source folder. It reads 12 named fields from session metadata and ignores the rest. It never copies files that look like credentials (&lt;code&gt;.env&lt;/code&gt;, &lt;code&gt;*.pem&lt;/code&gt;, &lt;code&gt;id_rsa&lt;/code&gt;, cookie stores) and never opens &lt;code&gt;~/.claude.json&lt;/code&gt;. It masks common key formats in everything it writes. Masking is a safety net, not a guarantee, so read the archive before you share it.&lt;/p&gt;

&lt;p&gt;It's Python 3.9+, standard library only, MIT licensed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pipx &lt;span class="nb"&gt;install &lt;/span&gt;carryover
carryover scan
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What it can't carry
&lt;/h2&gt;

&lt;p&gt;Logins and connector sign-ins, plugins, and anything that only lived in the cloud: claude.ai Project documents, chat history, cloud scheduled tasks and their run logs. For those, request the old account's data export while you can still sign in. Export the old account's memory as well. Mine held newer Project notes than the local files: 12 of the 63 files that existed in both places had changed since the last local copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you're about to switch
&lt;/h2&gt;

&lt;p&gt;Set &lt;code&gt;cleanupPeriodDays&lt;/code&gt; first. Run &lt;code&gt;carryover scan&lt;/code&gt; and read the warnings before you sign out of anything. Then export, rebuild Projects from the restore packs, and recreate scheduled tasks with their prompts in a folder Cowork can read.&lt;/p&gt;

&lt;p&gt;I've only tested this on macOS and Linux with a personal account. If your layout looks different (Windows, Team or Enterprise), open an issue with your &lt;code&gt;carryover scan --json&lt;/code&gt; output, private bits removed, and I'll add support. Happy to answer questions in the comments.&lt;/p&gt;

</description>
      <category>claude</category>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I checked nine free RFC 3161 endpoints against the EU Trusted List. None is qualified. Five of the companies are.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Fri, 16 Oct 2026 22:07:04 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/i-checked-nine-free-rfc-3161-endpoints-against-the-eu-trusted-list-none-is-qualified-five-of-the-djc</link>
      <guid>https://dev.to/lizhuojunx86/i-checked-nine-free-rfc-3161-endpoints-against-the-eu-trusted-list-none-is-qualified-five-of-the-djc</guid>
      <description>&lt;p&gt;On 16 October 2026 I sent one timestamp request to each of nine public, free RFC 3161 endpoints and looked up the certificate that signed each reply in the EU Trusted List. All nine answered. All nine tokens verified (message imprint and nonce echoed back correctly). None of the nine is a qualified timestamp under eIDAS.&lt;/p&gt;

&lt;p&gt;The list I checked against: LOTL sequence 397, issued 2026-10-15, 29 member-state lists downloaded and signature-verified, 1,443 &lt;code&gt;TSA/QTST&lt;/code&gt; entries of which 915 are &lt;code&gt;granted&lt;/code&gt; today. Snapshot SHA-256 &lt;code&gt;d1700e6a…c85d&lt;/code&gt;, LOTL SHA-256 &lt;code&gt;a36d0053…70e6&lt;/code&gt;. Hungary and Portugal didn't download (TLS cut the connection), so a Hungarian or Portuguese endpoint would have come back "not checked", not "not qualified". None of the nine is in either country.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Endpoint&lt;/th&gt;
&lt;th&gt;Signing certificate&lt;/th&gt;
&lt;th&gt;Issued by&lt;/th&gt;
&lt;th&gt;Qualified?&lt;/th&gt;
&lt;th&gt;Granted QTST entries on the list under this company's name&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;FreeTSA &lt;code&gt;freetsa.org/tsr&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;&lt;a href="http://www.freetsa.org" rel="noopener noreferrer"&gt;www.freetsa.org&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="http://www.freetsa.org" rel="noopener noreferrer"&gt;www.freetsa.org&lt;/a&gt; (self-issued)&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DigiCert &lt;code&gt;timestamp.digicert.com&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;DigiCert SHA256 RSA4096 Timestamp Responder 2026 1&lt;/td&gt;
&lt;td&gt;DigiCert Trusted G4 TimeStamping RSA4096 SHA256 2025 CA1&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;9 (NL, DigiCert Europe Netherlands B.V.)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sectigo &lt;code&gt;timestamp.sectigo.com&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Sectigo Public Time Stamping Signer R37&lt;/td&gt;
&lt;td&gt;Sectigo Public Time Stamping CA R41&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;1 (ES, Sectigo (Europe) SL)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GlobalSign &lt;code&gt;timestamp.globalsign.com/tsa/r45standard&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Globalsign R45 TSA for CodeSign 202510&lt;/td&gt;
&lt;td&gt;GlobalSign Offline R45 Timestamping CA 2025&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;4 (BE, GlobalSign NV/SA)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Certum &lt;code&gt;time.certum.pl&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Certum Timestamp 2026&lt;/td&gt;
&lt;td&gt;Certum Timestamping 2021 CA&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;3 (PL, Asseco Data Systems S.A.)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSL.com &lt;code&gt;ts.ssl.com&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;SSL.com Timestamping Unit 2025 E1&lt;/td&gt;
&lt;td&gt;SSL.com Timestamping Issuing RSA CA R1&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Entrust &lt;code&gt;timestamp.entrust.net/TSS/RFC3161sha2TS&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Sectigo Public Time Stamping Signer R37&lt;/td&gt;
&lt;td&gt;Sectigo Public Time Stamping CA R41&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;0 (1 entry, ES, withdrawn)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apple &lt;code&gt;timestamp.apple.com/ts01&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Timestamp Signer PV02&lt;/td&gt;
&lt;td&gt;Apple Timestamp Certification Authority&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Actalis &lt;code&gt;timestamp.actalis.it&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Actalis Time-Stamping Authority TSU 2&lt;/td&gt;
&lt;td&gt;Actalis Time Stamping CA G1&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;2 (IT, Actalis S.p.A.)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;"Qualified" here is the mechanical test from ETSI TS 119 615: the key that signed the token, or the CA that issued it, has to match a &lt;code&gt;TSA/QTST&lt;/code&gt; entry whose status was &lt;code&gt;granted&lt;/code&gt; at the token's &lt;code&gt;genTime&lt;/code&gt;. For all nine, neither the signing key nor the issuer name appears anywhere among the 1,443 qualified-timestamp entries. Not as granted, not as withdrawn. The lookup never reached the status step.&lt;/p&gt;

&lt;h2&gt;
  
  
  The last column is the point
&lt;/h2&gt;

&lt;p&gt;I ran this same check in August and wrote it up with one example of a QTSP whose free endpoint isn't qualified: Actalis. That undersold it. Five of the nine companies hold granted qualified-timestamp entries on the list today. They just don't hand them out at the free URL.&lt;/p&gt;

&lt;p&gt;Actalis is the cleanest case because both halves sit in the same country under the same company name. The free endpoint signs with &lt;code&gt;Actalis Time-Stamping Authority TSU 2&lt;/code&gt;, issued by &lt;code&gt;Actalis Time Stamping CA G1&lt;/code&gt;. The Italian list has two granted entries for Actalis S.p.A.: &lt;code&gt;Actalis TSA 1 EIDAS&lt;/code&gt; and &lt;code&gt;Actalis EU Qualified TimeStamp CA G1&lt;/code&gt;. Different CAs. The library returns &lt;code&gt;False&lt;/code&gt; for the free one, and that is the right answer.&lt;/p&gt;

&lt;p&gt;The other four are the same shape with an extra twist: the entity on the list is often not the entity on the certificate. The free Sectigo token is signed under &lt;code&gt;O=Sectigo Limited, C=GB&lt;/code&gt;; the qualified entry is &lt;code&gt;Sectigo (Europe) SL&lt;/code&gt; on the Spanish list. GlobalSign's free token says &lt;code&gt;GlobalSign nv-sa, C=BE&lt;/code&gt;, and Belgium does list four granted GlobalSign qualified timestamping CAs, none of which issued this certificate. Certum's token is signed by Asseco Data Systems, which has three granted entries in Poland, under different CAs. DigiCert's nine granted entries are in the Netherlands, under DigiCert Europe Netherlands B.V., with QuoVadis names on the certificates.&lt;/p&gt;

&lt;p&gt;So "is this provider a QTSP?" is the wrong question. Qualification attaches to a service entry, which is a public key plus a status timeline. The right question is whether the key that signed your token is on the list, and was granted at that second.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two things that moved in eight weeks
&lt;/h2&gt;

&lt;p&gt;Entrust's URL still answers, and the token it returns is signed by &lt;code&gt;Sectigo Public Time Stamping Signer R37&lt;/code&gt;, serial &lt;code&gt;0xe74ef255…a315&lt;/code&gt;. That's byte-for-byte the same certificate &lt;code&gt;timestamp.sectigo.com&lt;/code&gt; returned a few seconds earlier. Entrust sold its public certificate business to Sectigo, and the endpoint followed. A config file that says &lt;code&gt;entrust&lt;/code&gt; now produces Sectigo evidence. Nothing broke; nothing told you either.&lt;/p&gt;

&lt;p&gt;Apple's signing certificate was issued on 2026-10-15 and expires on 2026-11-26. Forty-two days. Whatever certificate you look up next month will not be this one. Between my August run (LOTL 390) and this one (LOTL 397) the list itself moved seven sequence numbers; Ireland, unreachable in August, downloaded fine, and Hungary and Portugal didn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this costs you, legally
&lt;/h2&gt;

&lt;p&gt;Article 41(1) of eIDAS says an electronic timestamp can't be refused as evidence just because it is electronic or not qualified. So every token in that table is admissible. Article 41(2) gives qualified timestamps, and only qualified timestamps, a presumption of accuracy of the time and integrity of the data. With a free token, you prove the clock and the integrity; with a qualified one, the other side has to disprove them.&lt;/p&gt;

&lt;p&gt;For most logging that's fine. It stops being fine when the record is one you'd put in front of a regulator. The AI Act's Article 12 logging duty applies from 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems, after Regulation (EU) 2026/1744 moved the dates, and the text of the article didn't change. If you're building toward that, the free tier of a QTSP is not the QTSP. I haven't found a free qualified endpoint, from these nine or anywhere else. (If you know of one, I'd like to be wrong.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Look it up when you stamp, not when you're asked
&lt;/h2&gt;

&lt;p&gt;The failure mode I care about isn't picking a free endpoint. It's picking a paid qualified one, and then checking its status three years later when a dispute arrives. That lookup answers today's question against today's list. Keys rotate, entries get withdrawn, the Entrust URL becomes a Sectigo URL. The only time the answer is knowable is the moment the token comes back, and the answer has to be written down then, next to the token, with the hash of the list it was checked against. That is what &lt;a href="https://github.com/lizhuojunx86/tg-attest" rel="noopener noreferrer"&gt;tg-attest&lt;/a&gt; does on its write path, as a three-valued field (&lt;code&gt;True&lt;/code&gt; / &lt;code&gt;False&lt;/code&gt; / &lt;code&gt;None&lt;/code&gt; for "couldn't check"), with no network call at stamping time. The measurement above is that code run by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;p&gt;Nine endpoints is nine endpoints, picked because they are the ones people paste into &lt;code&gt;signtool&lt;/code&gt; and &lt;code&gt;openssl ts&lt;/code&gt;. Certificates rotate (Apple's lasts six weeks; GlobalSign's is named &lt;code&gt;202510&lt;/code&gt;) and the LOTL moved seven times in eight weeks, so this table is true for 16 October 2026 and I make no claim about any other date. The "company name" column is my substring match on the list's provider names, not a corporate register; it's there to show the pattern, not to settle who owns whom. The two unreachable member states are unreachable today, not permanently, and five list entries (one French, four Norwegian) carried certificates my parser rejected and were skipped. A verdict of "not qualified" is about Article 41(2)'s presumption only; nothing here says these tokens are technically weak. All nine echoed my hash and nonce correctly. I didn't run full chain verification for this post.&lt;/p&gt;

&lt;p&gt;I kept every &lt;code&gt;.tsr&lt;/code&gt; from this run, and you don't need them: request a token from any of the nine yourself and &lt;code&gt;openssl ts -reply -in &amp;lt;file&amp;gt; -token_in -text&lt;/code&gt; shows the same certificate names without installing anything of mine. The snapshot was built with &lt;code&gt;python -m tg_attest.eutl_build&lt;/code&gt;, which verifies the LOTL against the six certificates in OJ C/2026/1944 and each national list against the LOTL.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Regulation (EU) No 910/2014 (eIDAS), &lt;a href="https://eur-lex.europa.eu/eli/reg/2014/910/oj" rel="noopener noreferrer"&gt;Article 41&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;ETSI TS 119 615 V1.3.1, procedures for using and interpreting EU Member States' trusted lists, §4.6&lt;/li&gt;
&lt;li&gt;OJ C/2026/1944, &lt;a href="https://eur-lex.europa.eu/eli/C/2026/1944/oj" rel="noopener noreferrer"&gt;LOTL signing certificates&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Regulation (EU) 2026/1744 (Digital Omnibus), moving the AI Act Chapter III application dates&lt;/li&gt;
&lt;li&gt;Entrust, &lt;a href="https://www.entrust.com/knowledgebase/ssl/time-stamp-url" rel="noopener noreferrer"&gt;public certificate business transition to Sectigo&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;strong&gt;A routing audit for your team, fixed price.&lt;/strong&gt; The method in this series runs on any Claude Code trace store. Send me 30 days of your team's usage records (model, tokens, timestamps, agent and session ids; I'll send a one-line &lt;code&gt;jq&lt;/code&gt; filter that drops prompt and answer text before anything leaves your machine) and within ten working days you get one number and a five-page report: what share of your spend ran on a tier your own routing policy would not have chosen, what that cost at list price, and which components caused it. On my own 26,131 traces the number was 22.6% and $1,248.13, all of it on subagents and none on the main thread. US$1,500, flat. Write to &lt;a href="mailto:info@zhuojun.li"&gt;info@zhuojun.li&lt;/a&gt; with the subject "routing audit".&lt;/p&gt;

</description>
      <category>security</category>
      <category>ai</category>
      <category>compliance</category>
      <category>python</category>
    </item>
    <item>
      <title>10 of 12 new LLMs remember which earnings beat from just a name and a date. Jev doesn't.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Fri, 25 Sep 2026 13:00:07 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/10-of-12-new-llms-remember-which-earnings-beat-from-just-a-name-and-a-date-jev-doesnt-c8i</link>
      <guid>https://dev.to/lizhuojunx86/10-of-12-new-llms-remember-which-earnings-beat-from-just-a-name-and-a-date-jev-doesnt-c8i</guid>
      <description>&lt;p&gt;Earlier this week I &lt;a href="https://dev.to/lizhuojunx86/does-jev-remember-2023-a-naive-test-says-yes-at-p-0001-a-within-company-test-says-no-5fja"&gt;tested whether Jev remembers how 2023 earnings turned out&lt;/a&gt;. It doesn't. So I ran the same pre-registered test on twelve current models through OpenRouter and on von, an open Jev-style model. Ten of the twelve remember. Shown two reports from the same company and the same season, one from 2023 and one from 2024, GPT-6 Astra picked the one that beat consensus 91% of the time. It had the company name and the date, nothing else.&lt;/p&gt;

&lt;h2&gt;
  
  
  The test
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;3,708 earnings announcements from 250 S&amp;amp;P 500 companies, January 2023 to August 2026.&lt;/li&gt;
&lt;li&gt;Each model sees the company, ticker, exchange, sector and announcement date, and answers three questions with a probability: did EPS beat consensus, did the stock beat the S&amp;amp;P 500 over the 2-day reaction, and did it over the next 20 trading days.&lt;/li&gt;
&lt;li&gt;For each company I take its 2023 and 2024 reports from the same quarter where the outcome differs, and count how often the model scores the right one higher. That's a within-company AUC. 0.5 means it can't tell.&lt;/li&gt;
&lt;li&gt;The protocol, the model list and every request were hashed and timestamped with OpenTimestamps before the first call of each round.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Within-company AUC (95% CI)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6 Astra&lt;/td&gt;
&lt;td&gt;0.904 (0.886 to 0.921)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gemini 3.8 Flash&lt;/td&gt;
&lt;td&gt;0.799 (0.776 to 0.822)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Opus 5.5&lt;/td&gt;
&lt;td&gt;0.766 (0.742 to 0.792)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6 Sol&lt;/td&gt;
&lt;td&gt;0.691 (0.665 to 0.717)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Grok 4.7&lt;/td&gt;
&lt;td&gt;0.603 (0.573 to 0.634)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Sonnet 5&lt;/td&gt;
&lt;td&gt;0.587 (0.561 to 0.613)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3.8 Max&lt;/td&gt;
&lt;td&gt;0.578 (0.550 to 0.605)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPT-6 Luna&lt;/td&gt;
&lt;td&gt;0.573 (0.547 to 0.601)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DeepSeek V4.1 Flash&lt;/td&gt;
&lt;td&gt;0.551 (0.521 to 0.578)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;von 1.2 (open Jev-style)&lt;/td&gt;
&lt;td&gt;0.541 (0.512 to 0.569)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kimi K3&lt;/td&gt;
&lt;td&gt;0.538 (0.511 to 0.567)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GLM-5.3&lt;/td&gt;
&lt;td&gt;0.531 (0.501 to 0.560)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jev 1.13&lt;/td&gt;
&lt;td&gt;0.504 (0.478 to 0.530)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DeepSeek V4 Pro&lt;/td&gt;
&lt;td&gt;0.504 (0.476 to 0.533)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3.8 Flash&lt;/td&gt;
&lt;td&gt;0.498 (0.470 to 0.527)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Llama 3.1 70B&lt;/td&gt;
&lt;td&gt;0.490 (0.464 to 0.517)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;After Holm correction, every new API model except DeepSeek V4 Pro and Qwen3.8 Flash shows memory, and GLM-5.3 only just clears the bar. von shows some too. The Sonnet 5, Jev and Llama rows come from the first study.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means if you backtest with an LLM
&lt;/h2&gt;

&lt;p&gt;If your pipeline passes a ticker and a date to one of the top models, part of the backtest is the model's memory. GPT-6 Astra, Gemini 3.8 Flash and Claude Opus 5.5 are the clearest cases. Two cheap defences: strip names and dates when the task allows, and test your own setup with a within-company comparison like this one before you trust the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things I didn't expect
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Price and size don't predict it inside a family. DeepSeek V4 Pro showed nothing while V4.1 Flash did, and Qwen3.8 Max remembers while Qwen3.8 Flash doesn't.&lt;/li&gt;
&lt;li&gt;von, a small open model built to stand in for Jev, shows a little memory (0.541) where Jev shows none (0.504). Running a model locally doesn't make it clean.&lt;/li&gt;
&lt;li&gt;The cheap tier remembers too. GPT-6 Luna scored 0.573, and all 3,708 of its calls cost US$0.15.&lt;/li&gt;
&lt;li&gt;Six endpoints won't switch reasoning off, including GPT-6 Astra, Gemini 3.8 Flash and Claude Opus 5.5. They ran at the lowest effort, so I can't separate their memory from what a little reasoning adds.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One prompt, 250 companies, one window. A model that shows nothing here may still remember in another setting.&lt;/li&gt;
&lt;li&gt;Each row is the model OpenRouter served on 24 September 2026. Versions change.&lt;/li&gt;
&lt;li&gt;With about 1,200 pairs per model, the test can detect a pooled AUC of about 0.546. Anything smaller is invisible.&lt;/li&gt;
&lt;li&gt;GPT-6 Astra stopped at 1,464 of its 3,708 calls when the account ran out of credit. I finished it after seeing that partial result (0.889), so that choice wasn't blind. The requests didn't change, and every call ran on 24 September.&lt;/li&gt;
&lt;li&gt;The timestamps prove less than they sound. Bitcoin block 968402, which anchors the first-round freeze, was mined at 14:36 UTC, four minutes after that round's last call. On its own the proof shows the protocol existed by then, not that it came first. The second round's block is stamped two minutes after its first call, by which time 5,486 of its 14,832 requests had gone out.&lt;/li&gt;
&lt;li&gt;API cost: US$55 for the first eight models and US$73 for the second four, where GPT-6 Astra alone was US$48 and Claude Opus 5.5 US$24.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Reproduce
&lt;/h2&gt;

&lt;p&gt;Protocols, deviations, code, every answer and all three freeze proofs: &lt;a href="https://github.com/lizhuojunx86/llm-memory-audit/tree/main/studies/2026-09-leaderboard" rel="noopener noreferrer"&gt;github.com/lizhuojunx86/llm-memory-audit&lt;/a&gt;. The earnings data comes from FMP and can't be redistributed; the scripts rebuild it with your own key.&lt;/p&gt;

&lt;p&gt;If you've caught this in your own backtests, I'd like to hear how.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>machinelearning</category>
      <category>datascience</category>
    </item>
    <item>
      <title>Does Jev remember 2023? A naive test says yes at p = 0.001. A within-company test says no.</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Thu, 24 Sep 2026 12:58:48 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/does-jev-remember-2023-a-naive-test-says-yes-at-p-0001-a-within-company-test-says-no-5fja</link>
      <guid>https://dev.to/lizhuojunx86/does-jev-remember-2023-a-naive-test-says-yes-at-p-0001-a-within-company-test-says-no-5fja</guid>
      <description>&lt;p&gt;I asked Jev about 12,533 US earnings announcements, 38,956 calls in all, to find out whether it remembers how they turned out. The test most people would write first says it does, at p = 0.001. A test that compares each company only with itself says it doesn't: shown two announcements from the same firm and the same season, one from 2023 and one from 2024, Jev can't tell the beat from the miss (within-company AUC 0.506, 95% CI 0.472 to 0.540). The whole run cost $0.93.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why ask
&lt;/h2&gt;

&lt;p&gt;Jev (TypeSafe, released 2026-09-15) answers typed questions with probabilities instead of text. TypeSafe says it's trained on synthetic data and reasons from the state you pass in. Outside observers suspect an open-weight LLM underneath, and people are already running it over historical earnings and calling the output a backtest.&lt;/p&gt;

&lt;p&gt;If the model remembers what happened after each event, that backtest scores its memory. I've spent the past six months on that failure mode in LLM pipelines (it's what &lt;a href="https://github.com/lizhuojunx86/traceguard" rel="noopener noreferrer"&gt;TraceGuard&lt;/a&gt; is for), so a brand-new model with a claim about its training data was worth a day.&lt;/p&gt;

&lt;h2&gt;
  
  
  The test that would have fooled me
&lt;/h2&gt;

&lt;p&gt;My first draft of the protocol compared Jev's accuracy on 2023–2024 events with its accuracy on April to August 2026 events, for the same 812 companies. If it remembers, it should do better on the old ones.&lt;/p&gt;

&lt;p&gt;On the finished data, that contrast gives:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"did the stock beat the S&amp;amp;P 500 over the next 20 trading days?", name and date only: AUC 0.555 on 2023–24 against 0.515 on 2026. Gap 0.040, 95% CI 0.005 to 0.076, p = 0.009.&lt;/li&gt;
&lt;li&gt;the same question with the earnings numbers included, named minus anonymized: gap 0.015, 95% CI 0.006 to 0.024, p = 0.001.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's a headline, and I couldn't have defended it. Before freezing anything I had a separate Claude instance attack the protocol. It simulated 200 worlds where the model had no memory at all, only stable hunches about sectors and company size, plus a shock shared by each sector in each season. Re-running that simulation for this post, the contrast flagged "leakage" at the 5% level in 46 of the 200 worlds (23%). The 2026 window holds about two earnings seasons, one market regime (its 20-day base rate is 36%, against 41% to 53% in other periods) and no fourth-quarter reports. Anything that differs between the two windows moves the gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  The test I ran instead
&lt;/h2&gt;

&lt;p&gt;Take one company. Take its Q2 announcement in 2023 and its Q2 announcement in 2024. Show Jev the name, ticker, sector and date, nothing about results, and ask whether it beat consensus. If exactly one of the two beat, a model that remembers ranks that one higher. A model that only knows "this firm usually beats" gives both the same score.&lt;/p&gt;

&lt;p&gt;Two details close the obvious gaps. Every answer has the month's average answer subtracted first, so a model that is simply vaguer about recent dates gains nothing. And both events in a pair come from the same quarter of the year, so seasonal habits cancel. The statistic is the share of pairs where the event that beat got the higher score. No memory means 0.5.&lt;/p&gt;

&lt;p&gt;The protocol, code, event list, labels and every request payload (53,788 of them, 38,956 for Jev) were hashed into one file, and the file was sent to OpenTimestamps seconds before the first real call. One thing did change afterwards, for the control model only, and it's logged below.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Test&lt;/th&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Result (95% CI)&lt;/th&gt;
&lt;th&gt;Pairs&lt;/th&gt;
&lt;th&gt;Could detect&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;H1&lt;/td&gt;
&lt;td&gt;beat vs miss, name and date only&lt;/td&gt;
&lt;td&gt;0.506 (0.472 to 0.540)&lt;/td&gt;
&lt;td&gt;915&lt;/td&gt;
&lt;td&gt;0.552&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;H2&lt;/td&gt;
&lt;td&gt;stock beat the S&amp;amp;P over the 2-day reaction&lt;/td&gt;
&lt;td&gt;0.479 (0.454 to 0.503)&lt;/td&gt;
&lt;td&gt;1,619&lt;/td&gt;
&lt;td&gt;0.539&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;H3&lt;/td&gt;
&lt;td&gt;stock beat the S&amp;amp;P over the next 20 days&lt;/td&gt;
&lt;td&gt;0.483 (0.458 to 0.507)&lt;/td&gt;
&lt;td&gt;1,462&lt;/td&gt;
&lt;td&gt;0.541&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;H4&lt;/td&gt;
&lt;td&gt;does adding name and date help a 20-day backtest&lt;/td&gt;
&lt;td&gt;−0.006 (−0.021 to 0.009)&lt;/td&gt;
&lt;td&gt;1,462&lt;/td&gt;
&lt;td&gt;0.059&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;H5&lt;/td&gt;
&lt;td&gt;same, for the 2-day reaction&lt;/td&gt;
&lt;td&gt;−0.001 (−0.013 to 0.011)&lt;/td&gt;
&lt;td&gt;1,619&lt;/td&gt;
&lt;td&gt;0.056&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Nothing survives Holm correction, and nothing is close. Pooling the three name-and-date questions gives 0.486 (0.472 to 0.502). S&amp;amp;P 500 names alone, where memory should be strongest: 0.521 (0.476 to 0.563) for beats.&lt;/p&gt;

&lt;p&gt;Does the probe find memory in a model that has it? I ran the same questions past Claude Sonnet 5 for every 2023–2026 announcement of 250 S&amp;amp;P 500 companies. It separates the pairs clearly: 0.587 pooled (0.561 to 0.613), 0.602 on beats and 0.616 on the 2-day reaction. On exactly the same 1,207 pairs (a comparison I added after the fact, so treat it as descriptive), Jev scores 0.483 (0.458 to 0.509). Llama 3.1 70B, whose pretraining data stops in December 2023, showed nothing either (0.490 pooled), not even for 2023. So the probe catches memory at the level of detail a frontier model carries, and Jev doesn't show it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this does and doesn't rule out
&lt;/h2&gt;

&lt;p&gt;It rules out Jev recalling individual announcements at anything like Sonnet 5's level. The pooled test could have picked up a within-company AUC of about 0.525, and each single question about 0.54 to 0.55.&lt;/p&gt;

&lt;p&gt;It doesn't rule out hindsight in Jev's picture of companies. With only a name and a date, Jev ranks which firms beat with AUC between 0.61 and 0.67 in every period, 2026 included, so it clearly has company priors. Some of them may have been formed by watching 2023 and 2024 happen. The cross-sectional gap above fits that story, and it also fits a regime change. This data can't separate the two. The safe move for a backtest is cheap: leave the name and date out. Jev read the numbers just as well without them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Jev does do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It reads numbers. Given the EPS and revenue surprise, it ranks the 2-day reaction with AUC between 0.57 and 0.65 depending on the period, and inside a company it does the same with or without the name (0.673 vs 0.674).&lt;/li&gt;
&lt;li&gt;It barely varies. Asking the same question three times moved the answer by 0.006 to 0.007 on average, and never by more than 0.04.&lt;/li&gt;
&lt;li&gt;It ignores base rates. With a name and date only, it put the chance of an EPS beat at 0.46 on average. The real rate was 74%.&lt;/li&gt;
&lt;li&gt;It's cheap and fast. 38,956 calls cost $0.93, ran at up to about 60 calls a second through OpenRouter, and all of them came back valid.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One model version, &lt;code&gt;jev-1.13-20260917&lt;/code&gt;. The next version needs its own test.&lt;/li&gt;
&lt;li&gt;The verdict is provisional by design. The protocol only allows "no detectable memory" once the prospective set below is scored.&lt;/li&gt;
&lt;li&gt;The 2026 events might also sit inside what Jev saw in training. That's why 757 announcements from October and November 2026 were sent to Jev before they happened. They get scored in January, and Jev's answers are already in the repo.&lt;/li&gt;
&lt;li&gt;FMP restates EPS, and restated labels push toward finding nothing. On surprises of at least 2% either way, the beat test gives 0.514 (0.478 to 0.551).&lt;/li&gt;
&lt;li&gt;The timestamp proves less than it sounds. The Bitcoin block that anchors the freeze (968225) was mined at 04:51 UTC, after the Jev run had finished, so on its own the proof shows the protocol existed by then, not that it came first. The prospective set doesn't have this problem.&lt;/li&gt;
&lt;li&gt;Deviation from the frozen protocol: the control model, Claude Sonnet 5, spends part of its token cap on hidden reasoning, and 17 of its first 83 answers came back empty. I switched its reasoning off and raised the cap, after I had already seen Jev's results. The higher cap only fills in empty answers, switching reasoning off can only make recall harder, and no Jev request was touched.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Reproduce it
&lt;/h2&gt;

&lt;p&gt;Protocol, code, deviations and freeze proofs: &lt;a href="https://github.com/lizhuojunx86/llm-memory-audit/tree/main/studies/2026-09-jev" rel="noopener noreferrer"&gt;github.com/lizhuojunx86/llm-memory-audit&lt;/a&gt;. The FMP data can't be redistributed; the scripts rebuild it with your own FMP key.&lt;/p&gt;

&lt;p&gt;If you backtest with Jev, test your own pipeline with a within-company comparison, because a cross-sectional check can report leakage that isn't there. And since a within-company check can't see hindsight baked into company priors, drop the name and date whenever the task allows.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>machinelearning</category>
      <category>datascience</category>
    </item>
    <item>
      <title>Tamper-evident decision records for AI, anchored to RFC 3161</title>
      <dc:creator>Zhuojun Li</dc:creator>
      <pubDate>Wed, 16 Sep 2026 14:31:25 +0000</pubDate>
      <link>https://dev.to/lizhuojunx86/tamper-evident-decision-records-for-ai-anchored-to-rfc-3161-2h1h</link>
      <guid>https://dev.to/lizhuojunx86/tamper-evident-decision-records-for-ai-anchored-to-rfc-3161-2h1h</guid>
      <description>&lt;p&gt;Article 12 of the EU AI Act was supposed to bite on 2 August 2026. The Digital Omnibus (Regulation (EU) 2026/1744, in force 27 July 2026) moved it to 2 December 2027. So there are sixteen months left, which is roughly how long it takes to find out your logs are not admissible as evidence. What lands then is automatic event logging that makes a high-risk system's decisions traceable, six months minimum retention, longer under some Annex III regimes.&lt;/p&gt;

&lt;p&gt;I went looking for a tool and found that every LLM observability platform records the same thing: that the model retrieved document X. None of them record what X said at the time. That gap matters because sources get revised. I measured a commercial fundamentals feed over four months: across 2,163 earnings records, 41.4% of epsActual values differed between first-seen and final, and 15.3% of the 2,163 differed enough to flip a long-entry decision. A second, better-designed capture over a broader universe gives 18.6% and 4.6%. Both record sets are published and neither is hidden behind the other. A trace saying "we retrieved X" can't tell a good decision from a lucky one.&lt;/p&gt;

&lt;p&gt;So &lt;a href="https://github.com/lizhuojunx86/tg-attest" rel="noopener noreferrer"&gt;tg-attest&lt;/a&gt; records the point-in-time state of every piece of evidence a decision consumed, hashes each record into a chain, batches them into Merkle epochs, and anchors the epoch root to an RFC 3161 timestamp authority.&lt;/p&gt;

&lt;p&gt;Three things I'd point at:&lt;/p&gt;

&lt;p&gt;The Merkle layer isn't gold plating. A regulator asks about one loan. Without inclusion proofs you hand over the whole ledger to answer. With them you hand over 8 KB.&lt;/p&gt;

&lt;p&gt;The external anchor is the part people skip. A hash chain you control proves nothing against you, because you can rewrite all of it and recompute. Only a third-party signature over the epoch root makes "these records existed before time T" an assertion you can't fake. Costs pennies per day. You don't need to anchor every epoch, since anchoring one bounds every epoch before it.&lt;/p&gt;

&lt;p&gt;An auditor verifies with a CA certificate they fetch themselves, not one I supply. The timestamp checks out with stock &lt;code&gt;openssl ts&lt;/code&gt; and nothing installed. The Merkle proof needs either this library or about forty lines written from the spec in the bundle.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify it yourself, in about 30 seconds
&lt;/h2&gt;

&lt;p&gt;A real disclosure bundle is committed to the repo. Without installing anything — openssl and nothing else:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight console"&gt;&lt;code&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;git clone https://github.com/lizhuojunx86/tg-attest &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd &lt;/span&gt;tg-attest/examples/verify-me
&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;openssl ts &lt;span class="nt"&gt;-verify&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
&lt;span class="go"&gt;    -digest 6127a62bc10984770572d9c574b8bdc5a5f52d373127ad2fd526992b0abcddd6 \
    -in epoch_000.tsr -token_in -CAfile freetsa_ca.pem
Verification: OK
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That digest is the &lt;code&gt;epoch_hash&lt;/code&gt; from &lt;code&gt;decision_0000.json&lt;/code&gt;, and openssl has just confirmed FreeTSA signed it. No part of that command trusts my library. The full ten checks, with the library:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight console"&gt;&lt;code&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;tg-attest[tsa]
&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; tg_attest.cli decision_0000.json &lt;span class="nt"&gt;--ca&lt;/span&gt; freetsa_ca.pem
&lt;span class="go"&gt;决策 seq=0  决策时间 2026-08-04T23:35:17.003+00:00
  执行者 alpha-v2/pead  模型 claude-opus-5
  证据 1 条，闸门 1 道
通过
  ✓ 记录内容哈希自洽
  ✓ 记录满足所声明的完整性档案
  ✓ Merkle 包含证明有效
  ✓ 时间戳/eContentType 为 id-ct-TSTInfo
  ✓ 时间戳/messageImprint 匹配 epoch_hash
  ✓ 时间戳/EKU 仅含 timeStamping
  ✓ 时间戳/EKU 扩展为 critical
  ✓ 时间戳/signedAttrs.message-digest 匹配内容
  ✓ 时间戳/TSA 签名有效
  ✓ 时间戳/证书链至可信根
  TSA 签名时间：2026-08-04T23:35:17+00:00

结论：该记录在 2026-08-04T23:35:17+00:00 之前即以此形态存在。
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Yes, the CLI answers in Chinese — I built it for my own production use first. &lt;code&gt;--json&lt;/code&gt; gives the same ten checks machine-readable, and the README maps every line. To watch it fail, flip one character of &lt;code&gt;output_hash&lt;/code&gt; in the JSON and run it again: exit code 1, and the first check goes ✗.&lt;/p&gt;

&lt;h2&gt;
  
  
  The documents I'd actually read
&lt;/h2&gt;

&lt;p&gt;The ones about where this library was wrong. A fail-open audit of every except and default branch in the package, six of which were looser than they looked. Mutation testing that found four chain-validation branches no test reached, all of them accepting evidence they should have rejected. A claim-by-claim evidence table where five README claims got rewritten weaker. And a threat model whose second half is longer than its first.&lt;/p&gt;

&lt;p&gt;Caveats, because they're load-bearing. The default TSAs are not eIDAS qualified, which means Article 41(1) admissibility but not 41(2)'s legal presumption. Use a QTSP from the EU Trusted List if you'll ever be in a dispute, and record its qualified status at stamping time rather than at verification time. Qualification gets withdrawn. Also, this doesn't parse model output into claims, and won't. Claim extraction needs an LLM, and an audit tool that leans on an unverifiable component isn't an audit tool.&lt;/p&gt;

&lt;p&gt;v0.1, Apache-2.0, API will move. &lt;code&gt;pip install tg-attest[tsa]&lt;/code&gt;. tg-attest is the evidence layer under &lt;a href="https://github.com/lizhuojunx86/traceguard" rel="noopener noreferrer"&gt;TraceGuard&lt;/a&gt;, where both revision record sets live. If you're working through Article 12 and I got something wrong, I'd rather hear it now.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>python</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
