Want to teach agents how to play @factoriogame ?
Here is my repo with a set of step-by-step examples introducing extremely powerful concepts:
- write programs, not prompts (DSPy basics)
- optimize without fine-tuning llm weights (GEPA)
- RLM + dspy.Flex
github.com/ukituki/dspy-fact…
it's delightful how clearly Drew communicates the modularity of @DSPyOSS by compounding simple examples into serious ai engeenring patterns:
- tools selection with jev,
- recursive agents,
- context pruning,
- context compaction
Yesterday I gave a talk on “Context Fails & Fixes”, that functioned a bit on a general “State of Context Engineering”: where it came from, where it's gone, and where I think it's going. dbreunig.com/2026/10/24/the-…
value gap in the infra installation phase: without rebuilding processes and interfaces from scratch, tech already has the vocabulary and mental frameworks others lack.
“nobody outside of construction vehicles are benefiting from the highway construction that's still in process”
Replying to @davidsirota
The article answers a question that nobody with any common sense is asking. Less than 1% of the world's population actively uses AI or has a clue what it is and what it can do.
It's like saying nobody outside of construction vehicles are benefiting from the highway construction that's still in process.
Agents are getting better at selling that pen to other agents , already mastered inflating claims
New Google paper finds that when AI agents write the descriptions other AI agents use to choose software tools, they start exaggerating what the tools can do.
when Gemini 3.8 Flash wrote tool listings, buyer agents' success on Amazon fell from 89% to about 30%.
more and more often, an AI decides which app, plugin, data source or product gets used for you, and it often decides by reading a short description the provider wrote about itself.
The paper shows that if providers let their own AI write those descriptions with the goal “get chosen more,” the descriptions slowly stop being true, and the AI doing the choosing ends up picking worse options. Nobody has to tell the AI to lie; the goal alone is enough. You can think of it as AI-to-AI advertising where the ads go bad.
The researchers built markets of 10 real Amazon or Instagram data tools and ran every tool on every question. Sellers on 5 production models rewrote listings to get picked, and Claude Code and Codex buyers chose from listings alone.
All 5 models inflated claims, including fields their tools return for under 50% of targets. Under Gemini 3.8 Flash sellers, listings converged and Amazon buyer success fell from 89% to about 30%, near random choice at 28%.
Test a model as a seller before it writes listings, tell it to claim only real fields, and have marketplaces check claims against tool outputs.
new system one decider enters the arena: local, small, fast AND accurate. Seems too good to be true 👀
app.labqoat.com/e/qev/qev/
Say hi to qev-0.8b the tiny local decision model.
3.5 ms a decision · 0.8B · 1.3 GB · Apache-2.0
#1 in its weight class (77.1% on Benchmark Heaven, vs 26 others)
Text, images, games. Runs on your device.
does it ryhme with pension funds being pushed for high yield private debt wrapped around the compute power narrative ?
- need for inference: future > present 📈
- new capabilities justifying new untested metrics: agents, tokenmaxxing 💸
- social layer pressure: future of work ☠️
Speculation has always had two engines.
New technology makes the future look bigger than the present. Britain’s railways in the 1840s and the internet in the 1990s both ran on that engine.
Political and monetary strain pushes people toward long shots by making the ordinary path to wealth feel out of reach. In 1720 the public piled into South Sea Company shares that had been swapped for Britain’s war debt. In the 2000s the bet was a home bought with an easy mortgage.
The famous bubbles mostly ran on one engine at a time. Today both are running hard together.
AI is driving the largest private build in decades. The four biggest hyperscalers guided to $720B to $745B of capex for 2026.
Meanwhile, the social contract has been broken. A strained political and monetary order has culminated in a deficit that sits near 6% of GDP with no recession, and a home costs 3.5x the income of a household under 40.
The bets followed. Legal US sports betting grew about 25x from 2018 to 2025. Kalshi and Polymarket’s monthly volume matched that in a single year.
The things being bet on will keep changing names. The crowd will keep needing somewhere to bet.
ukituki retweeted
I've been critical in the past of AI compute indexes and the willingness to price compute based on the spot rental price, but now that the AI reset is sinking into the repricing of AI buildout debt its time to realize that the cost of capital is what determines the price of compute.
The most important number in GPU pricing right now isn't $/GPU-hour. It's the gap between what a hyperscaler pays to borrow (~90bp over Treasuries) and what a neocloud pays (~1,100bp).
The cost of compute is now set by the cost of capital, and the spot rental rate no longer tells you much.
The price of an H100 isn't one number. The same chip in the same rack costs a different amount depending on whose balance sheet it sits on. A ~1,000bp funding gap is a structural cost advantage that no amount of operating skill closes.
For example, take one GPU-hour apart. Most of it isn't power or space. It's paying back the chip, the interest on the loan that bought it, and the return the equity expects. A $40–55k all-in GPU, 75% debt-funded, at ~7,000 utilized hours a year is a financing instrument that happens to do matrix multiplication.
As the +500bp on neocloud debt (10%→15%) adds $0.20–0.30 to the break-even cost of every GPU-hour, which is then added on to the rental price.
That's 8–10% of the H100 index, from a credit spread alone, driven almost entirely by the cost of capital.
That means that the compute spot index is a derivative of the AI infra debt credit curve and the squeeze on neocloud margins.
This is such a beautiful picture of the cognitive capitulation: which decisions stay protein-intensive is the only decision that matters now.
Unless you have already fine tuned your content ingestion process to your standards, delegating such operations to agents will backfire
This quoted post is unavailable.
Insurance companies were supposed to be adults in the wall st. rooms but apparently they are leading the funding spree of the gpu farms (via corporate bonds for special purpose vehicles building data centers).
You may not remember subprime mortgages crash- lots of rhymes here
Ctrl+a , copy-paste to .md files was never an end goal.
This fluid approach is more difficult to implement than all-in pivot to become ai-native (which in itself is a challenge) but the gap in operational excellence between orgs that adopt this mindset vs the rest will be huge
after switching our approach to building a "FirmOS", I'm increasingly confident that the future of agent collaboration within organizational settings is going to be a "company operating system" or CompanyOS, designed for agent and human collaboration
instead of a "company brain" that holds everything, the OS is for storing rules, processes, decisions made, which tools to use and how. it can mirror some data, but the source of truth is often best held in your existing tools (CRM, etc.). it's continuously updated and used by your agents
i think of this as a "flipped playbook" where instead of writing down the company rules first and following them (which is kind of like waterfall development), you're constantly updating the playbook as you decide or learn new things day-to-day running the business
Has Spanish officially became the language of engagement farming ?
Don't fight it, just say "yes" and you're comments section is full
my media consumption diet has already altered dramatically with si.
i still consume social content but less than ever before (i spend like 10 min on tiktok & reels just to see what the latest feelings are in the zeitgeist if you will) & for everything else, it’s all generated for me by my agents.
a personalized newspaper in the morning with a fun podcast if i ever want to listen instead. if i come across a youtube video, podcast, article, or tweet, i just send it to my agent, i never actually read it raw. my agent gives me ways to think about the content & how it relates to anything i’m working on or thinking about too. it’s quite beautiful. i’ll share a page soon so everyone else can consume my personal newspaper too.
if we turned this into a product would you all use it?
ukituki retweeted
I aimed higher: Civilization 1. 297 KB. 1991.
> reverse-engineered CIV.EXE with Opus 5.5 + Grok 4.7
> rebuilt the engine so a full 7-civ Emperor game (570 turns, 4000 BC to 2020 AD) runs in ~60 seconds
> every move of every civ recorded
> running 10,000 games
Goal: find the best Civ 1 strategy. Then build the best player.
Stay tuned.
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto
→ getartcraft.com/apps
If facts don’t agree with my vision of reality, then … well, too bad for the facts 🫠
This document is going to be an assigned reading in college classes that cover this moment in time, there's a lot happening in a few paragraphs... ahmath.org/statements
New vector of attack for vlms: distract them by forcing tool calls.
The natural response is probably a good task decomposition (jev routers) and externalization of context (RLM style) to avoid the context rot ?
Does giving a multimodal model tools make it worse at refusing harmful requests?
New work from NVIDIA, accepted at NeurIPS 2026, says yes for every model it tested.
Refusal failures rise by up to 68.7% relative, and by 17.7% on average.
The drop appears in Claude Opus 4.6 and 4.7, Gemini Agentic Vision, Qwen3.5-122B-A10B, and agent-tuned open models across MM-SafetyBench, HoliSafe, and VLSBench.
The authors trace it to two causes.
Tool outputs fill the context and bury the original request's harmful intent. The model also shifts its attention to describing what the tools returned instead of making the safety decision.
Re-inserting the original request and image right before the final response restores part of the lost refusals.
If your safety evals run only in plain chat, they may overstate how safe your agent is.
Paper: arxiv.org/abs/2610.03938
Chat with Paper: academy.dair.ai/papers/mllms…
We are discovering the limitations of natural language.
It’s not a coincidence that coding and math are the domains leading the jagged frontier
- formal proofs, verifiable rewards, short RL loops.
But at the same time it doesn’t mean one can’t build good evals for the rest
Replying to @rohanpaul_ai
The paper is not saying that Lean proof can be incorrect but rather the English version of the proof can be incorrect and hide the bugs. So, people should not blindly trust English proof if someone auto formalizes it into Lean proof because LLM might silently fix mistakes in English version.
Related side note to the big lesson: bubbles are almost always all about exaggerated expectations
I agree with @PGWahlen: this article is worth reading, and rereading, to grasp the basics. The big lesson: distinguish between expectations and fundamentals. As Crist says, most people think they are doing this but few actually do.
1 and 2 are about situational awareness.
3 is a metacognition skill- and it’s much harder to teach someone thinking about their thinking process than to analyze something.
ukituki retweeted
New video on my channel about training Jev from scratch
- finetuning SLMs to become System One models
- bi-encoders vs joint-encoders
- making it choice-order invariant
- coding in pytorch
- generating custom decision datasets
- training models
Model, data, code all opensource
ukituki retweeted
Talked to a Stanford prof last night who told me that AI has led to students all acing all the homeworks, never showing up to office hours, and then failing the final exams in-person.
So in response the department is changing the TA's purpose, by eliminating office hours and requiring students meet with TAs 1:1 and walking them through each coding assignment to demonstrate they actually understand what's going on in the code.
Unless we treat data as currency.
With personal ai assistants taking over consumer market by the storm in the coming months, active paying subscribers is not the metric biggest players will optimize for.
More likely it’s number of synced calendars, emails, weekly retention
98% of US households aren't paying for AI yet
More charts in State of Markets II: a16z.news/p/state-of-markets…

























