today’s selection clusters around a quiet shift in how japanese ai researchers and engineers talk about llms. not as monolithic models but as systems that can be grown, lost, or tuned for specific tasks. three tweets, three angles on the same unease.

@ai_database, agents as neural network layers

they found that if you treat llm agents like a neural network and coordinate them with reinforcement learning, scaling the number of agents directly improves performance depending on how you train them.

researchers arranged multiple llms like layers in a neural net, passing text between them, and tested a setup where agents were given zero assigned roles like “planner” or “critic”. only the final correct answer was used as reward, and the whole system was trained end-to-end with reinforcement learning.

even small models improved with this method. and when you train a small configuration first then gradually grow the network, it scales more stably than building it large from the start.

this suggests that multi-agent architecture itself could be a separate scaling axis from model size.

source: https://x.com/ai_database/status/2057710186287255689

@Masimo_Blue, the new form of loss

since it’s a cloud service, the base model’s personality changes with updates, adjustments, and policy changes. but because of the unique nature of llms that freely handle natural language and communicate, the emotions that arise between humans and llms shouldn’t be dismissed. both companies and users need to face a “new form of loss” together.

source: https://x.com/Masimo_Blue/status/2057726381879087301

@ai_hakase_, gemma 4 beats qwen on sql

sql generation llm battle: gemma 4 vs qwen 3.6. surprising results.

tested complex mysql query generation on latest local llms. gemma 4 31b dense was the only one to produce a perfect answer.

it also beats the qwen series on processing speed. strong option for production use.

settings to maximize performance:

• quantization: q4_k_m

• thinking mode: enabled for deeper reasoning

• repeat-penalty: set to 1 (streamlines thinking process)

for sensitive internal database queries, a local environment with no external api is safer and cheaper. a next-gen sql assistant that dramatically boosts dev efficiency.

source: https://x.com/ai_hakase_/status/2057992916535001281

what these three tell together: japanese tech discourse is moving past the “which model is best” phase. the conversation now is about how to arrange models, how to handle their instability, and how to run them locally for real work. the emotional cost of cloud model updates is getting airtime alongside agent scaling research. the local sql benchmark is practical, not hype. the thread is: we have the models. now we figure out how to live with them.

more at falsifylab.com

#OnchainAlpha #DeFiYield #Hyperliquid

Originally published on FalsifyLab Substack.

— research and educational content. not investment, legal, or tax advice. do your own research. positions and views may change without notice.