TNP - 2026-11-10

Welcome to Trending Not Peak for Tuesday, November 10. Today, robot fingertips and spreadsheet cells open some unexpected doors. This voice is synthetic, and AI assisted with the writing. Follow your curiosity through the project links at trending not peak dot com.

Search for better programs without narrating every thought

First up, SwarmEvolve gives program-search agents a different way to exchange ideas. Hundreds of agents reason through internal model representations, sharing attention-cache information instead of writing out every intermediate thought. A novelty filter preserves different approaches before a summarizer combines them. Across twenty-one mathematical and scientific-computing problems, the researchers report a median three to eight minutes to reach the best scores competing frameworks reached in sixty minutes. On several problems, even their Qwen-three eight-B setup improved solutions originally found by AlphaEvolve with frontier models. These are author-reported research comparisons, with hardware and search budgets still consequential. If you build optimization systems, the possibility is spending more of your experiment exploring candidate programs. You could investigate it on a problem with an automatic scoring function, where each proposed improvement can be checked. The especially interesting question is whether preserving different internal approaches finds solutions that repeated text-based attempts keep missing.

Write workflow logic in a familiar language

Next up, Loopt lets you write GitHub Actions workflows in code, then generate the standard YAML that GitHub runs. TypeScript, Python, Go and Rust are first-party options; other languages connect through a plugin protocol. It can also import existing workflow YAML into editable code. For maintainers juggling several similar build jobs, that offers a concrete experiment in making workflow changes easier to express and review. The source lives under a dedicated workflow directory, while generated files carry a notice telling you where to edit. Loopt is newly introduced, so import fidelity and coverage of your particular Actions features deserve checking. Take one small existing workflow, import it, regenerate it, and compare the result before changing its behavior. Keeping ordinary YAML as the output gives you something familiar to inspect when the abstraction gets confusing.

Give robot fingertips contact and shear feedback

Turning to things a camera can't feel, PanoTac is a compliant robot fingertip that measures contact and sideways forces. Each finger produces a twelve-by-thirty-two grid, with three force components at each point, updated at up to a hundred hertz. The project lists a sensor cost of nine dollars forty cents. Across test-tube preparation, grain scooping and salt pouring, its researchers report an average forty-six point seven percentage-point improvement over vision-only policies. One demonstration uses weight cues to distinguish filled from empty opaque bottles. Robotics labs could explore touch-guided manipulation when an object hides the information a camera needs. The project links both method code and a hardware repository, giving that experiment somewhere to begin. That sensor price isn't the cost of the whole robot system. There's also a lovely interface detail: during data collection, tactile changes alter audio pitch and volume, letting a teleoperator hear the contact.

A serving recipe joins four DGX Spark machines

Back at the compute bench, a newly highlighted DeepSeek V-four point one Flash recipe distributes serving across four NVIDIA DGX Spark machines. The repository packages a tuned four-way tensor-parallel profile using SGLang and DSpark, built on a MiaAI-Lab recipe. That gives teams with this particular hardware a configuration to inspect when exploring a model server spread across several local machines. The accompanying comparison also discusses a vLLM branch, explicitly saying its release isn't ready. There aren't usable throughput figures in this account to turn that comparison into a winner. The grounded next step is narrower: reproduce the documented SGLang setup, then measure one representative coding workload. Record response time and completion quality together, so the cluster's usefulness has an application attached.

Thanks to Intelligrit

We'll pause between the compute cluster and the package index to thank Intelligrit, this episode's sponsor. Visit intelligrit dot com when you're ready to explore.

Inspect package provenance in PyPI's new security tab

Over at the package index, PyPI has finished rolling out redesigned project pages with a dedicated security tab. It shows release provenance states and attestations for individual files. Full provenance means every release file has an attestation. Depending on the type, an attestation can establish publication through a Trusted Publisher or connect a file to its source commit and build platform. Python maintainers and dependency reviewers now have a clearer place to inspect where an artifact came from. That history doesn't establish that the code itself is safe. The useful change is making the evidence visible at the point where someone chooses a dependency. Open a package your project already uses and inspect its release files. Then ask whether the recorded publishing and build origins match the project you intended to trust.

Train a model around the clues it should use

Now for a deeper model-training question. Mechanistic Shaping, from Goodfire, aims to influence which internal concepts a model relies on when making a decision. Correct labels alone can reward shortcuts, such as recognizing a treatment device in a medical image instead of the condition being studied. The researchers train against specifications about internal representations as well as outputs. Across vision, medical imaging and language experiments, including models up to thirty-two billion parameters, they report reducing targeted behaviors while preserving task performance. Model researchers could investigate this when ordinary accuracy hides dependence on an unwanted clue. Monitoring needs to evolve alongside training: a concept can move away from one probe or remain encoded in a nonlinear form. The paper studies those escape routes too. A useful experiment would test both the targeted shortcut and whether a newly fitted monitor can still recover it.

Fork inference state for decision-model workloads

Speaking of decisions, Flide is a new inference engine for Jev-style decision models. These models serve decision workloads, and Flide exposes the Jev system-one API. Its central claim is exact state forking: reuse inference state while preserving the answer the model would give each question on its own. The project reports up to nine point five times the speed of vLLM and SGLang, a comparison that needs independent checking against matched workloads. There's an email-triage demo in version zero point one point eleven. If you're building a classifier that asks related questions about the same material, this offers a focused serving experiment. Compare isolated answers with forked-state answers first, then measure throughput. Preserving the decision is what makes the saved computation useful.

Put an agent inside a spreadsheet cell

For a different interface to agent work, Recalc makes a spreadsheet where a cell can contain a value, a formula, a terminal command, or a Claude Code or Codex agent. You can watch agents fill cells and open an individual cell in its own terminal. That's an intriguing workspace for developers who want several small investigations visible beside their inputs and results. Imagine comparing how agents approach a few public example tasks, with each attempt occupying a place you can return to. The repository provides an Apache-licensed implementation, examples and recipes. Its introduction doesn't establish that this layout improves task completion or that terminal-backed cells provide isolation. Start with a disposable project and inspect agents in cells while they handle bounded tasks. The experiment is partly about software, and partly about whether a grid makes their work easier to follow.

A TLS certificate carries a readable protest

And finally, Horrible Public Key Tricks puts a protest message somewhere most people see only a wall of certificate text. The author shows a TLS certificate whose encoded public-key material contains readable prose, then walks into the mathematics of RSA. It's a peculiar little artifact for cryptography learners: a familiar-looking certificate becomes something you can inspect for deliberate structure. The author's broader complaints about certificate infrastructure are arguments, rather than findings this experiment settles. The concrete curiosity is the crafted key material itself. Follow the worked example to explore how mathematical key components become encoded bytes. Apparently even a certificate can arrive with editorial commentary tucked inside.

Something to carry into your next project: Loopt to generate workflow YAML, PanoTac to explore touch-guided manipulation, and Recalc to inspect agents in cells. The sources await at trending not peak dot com. This is Trending Not Peak. Leave a little room in your next experiment for an interface you hadn't considered.