Tootfinder

In the Opener Initiative, we collaborate on implementing the #DectNRPlus standard.
The standard provides license-free radio (no cellular operators) in the 1.9GHz band, with all bells and whistles of a 5G radio standard for #IoT applications.
In Opener, we are working on a portable

Opener Initiative
Building Opener, an open reference implementation of the NR+ protocol stack.

The Signal Rail: A Deterministic Motion Grammar for Communicating Conversational Agent State in Terminal Interfaces
Matteo Grella
https://arxiv.org/abs/2608.10689 https://arxiv.org/pdf/2608.10689 https://arxiv.org/html/2608.10689
arXiv:2608.10689v1 Announce Type: new
Abstract: Terminal interfaces to conversational agents report rich internal state (listening, thinking, executing tools, awaiting input, failing) almost entirely through text, while the motion channel beside it, the one peripheral vision monitors without reading, carries a single bit: alive. We present the Signal Rail, a one-row terminal status instrument that gives that channel a grammar. Four ideas govern it: spatial semantics (input, processing, and output zones, with direction as meaning), a motion grammar (one kinetic rule per state, never color alone), determinism (frames as a pure function of explicit inputs, golden-frame testable), and honesty (no invented progress or activity). We contribute a 45-section normative specification and a reference implementation inside a working full-duplex local voice agent driven by real signals.
toXiv_bot_toot

from my link log —
Debian Code Search: Fast TurboPFor with Golang SIMD.
https://michael.stapelberg.ch/posts/2026-09-06-dcs-fast-turbopfor-go-simd/
saved 2026-09-06

Debian Code Search: Fast TurboPFor with Go SIMD
This August, I accomplished what I wanted for many years: I deleted the last cgo dependency in Debian Code Search! This was made possible by Go’s recently introduced SIMD support, because now we can implement the TurboPFor integer compression format as efficiently — more efficiently, in fact, by using the newer AVX512 instruction set! — as the reference implementation.

from my link log —
A Golang-style defer mechanism for C.
https://gustedt.wordpress.com/2020/12/14/a-defer-mechanism-for-c/
saved 2020-12-14

A defer mechanism for C
An overview of a paper that presents a reference implementation of a defer mechanism (co-authored with Robert C. Seacord) has been accepted for publication at SAC’21. The full version is avai…

Spec-Driven Hardware Evolution via Executable Contract Refinement and Proof-Guided RTL Update
Shibo Zhao, Yang Zhang, Mengxia Tao, Baoqi Zhang, Kezhi Li, Qiang Xu, Binwu Zhu, Hao Yan, Min Li
https://arxiv.org/abs/2608.12684 https://arxiv.org/pdf/2608.12684 https://arxiv.org/html/2608.12684
arXiv:2608.12684v1 Announce Type: new
Abstract: Hardware development is inherently evolutionary: major revisions typically begin by changing intended behavior and then updating a previously validated implementation, rather than regenerating RTL from scratch. Yet most recent LLM-based hardware research still frames the task primarily as prompt-to-RTL generation, offering limited support for semantic version evolution of trusted legacy designs. We present spec-driven hardware evolution, a contract-centered formulation for RTL version iteration. Instead of treating a new feature request as a direct prompt for RTL generation, we refine it into a reviewed executable contract for the next version. This contract specifies what must hold at the externally visible transactional level through a behavior-level reference together with explicit observation and checking semantics, while leaving how the change is realized in RTL to the evolution process. Based on this formulation, we organize hardware evolution into four stages: Specify, Plan, Implement, and Validate. After contract approval, the remaining stages proceed automatically: Plan derives cross-version semantic deltas and localizes affected RTL regions, aided by mutation-based semantic probing; Implement and Validate then perform legacy-aware RTL update under proof-guided checking and iterative repair. We evaluate the framework on a controlled version-evolution case study of a representative TPU datapath block under data-format changes. The results support the feasibility of contract-driven hardware evolution and demonstrate that the proposed backend workflow can effectively drive validated legacy RTL toward next-version functional convergence under a reviewed executable contract. An anonymous artifact for reproducibility is available at https://anonymous.4open.science/r/SDHE-3A6C.
toXiv_bot_toot