Reading List – 2026-10-28
Several pieces point to the same engineering problem: passing the first check doesn’t guarantee a safe outcome. A model can propose a valid business change, but the orchestrator still needs to recheck live records and control writes. An authorized SSH session can also exceed its intended permissions. I find that distinction useful: correctness has to hold across the whole path, not just at the initial gate.
The Counting House
The Counting House puts lower-tier models on hardened rails inside human workflows, then measures their performance against human counterparts. That’s a different design problem from Wheelhouse, where agents can see the whole system and act independently to support exploratory software development. I find the separation useful: teams can improve high-volume casework without first solving autonomous coding. The open question is how much variation those rails can handle before the workflow needs human judgment.
The useful boundary here is that a model proposes a business outcome, while a mechanical orchestrator owns the write. It rechecks eligibility against live records, enforces idempotency, and runs multi-step changes as sagas, with approvals or compensating actions where needed. I’m interested in this separation because it treats model quality and transaction correctness as distinct problems, rather than trusting a capable-sounding response with durable state. The hard part is still encoding business rules and exception paths faithfully.
The Counting House · The Counting House — Steve Yegge
An architectural comparison of Obsidian Canvas and Heptabase
The key architectural choice is whether a board owns the relationship: Canvas stores arrows in its .canvas JSON, while Heptabase records connections on cards across whiteboards. Canvas layouts stay portable but absent from Obsidian’s graph; Heptabase exposes relationships across cards but can’t export them as an open interactive graph. I find that boundary more consequential than the UI: it determines whether structure survives a tool change or compounds inside one system. For long-lived notes, decide which failure you can tolerate.
Readwise Books: Step Three of Our Master Plan
Readwise’s ebook launch treats publisher access as a product dependency, not a later sales task. The post says deals with the Big 5 had to land together: opening with half the catalog would weaken customer confidence, while publishers wanted proof the store could sell books. Readwise says it secured the deals, but leaves the chicken-and-egg solution unexplained. I find that sequencing constraint more interesting than the app’s feature list; software quality can’t make up for missing supply at launch.
Atuin Threads: All your agent sessions on every machine
The design choice worth noting is modeling agent sessions as append-only logs, letting Atuin reuse its sync engine to search, resume, and fork work across machines and agent harnesses. Unlike shell history, these sessions retain intent, output, and failed attempts, giving later agents a record of why earlier work took a particular path. I like the shift from syncing commands to syncing the work around them; for teams, though, session sharing remains opt-in and is still being built.
Ghostty 1.4.0
A small per-read kernel limit, not parser speed alone, was throttling Ghostty’s macOS terminal throughput. The kernel caps each pty read at about 1 KiB, so Ghostty now drains the pty on one thread while another parses. The release reports 25% to 55% higher end-to-end I/O throughput on macOS. What catches my attention is how directly this connects to backpressure: when profiling streaming software, measure whether producers are waiting on parsing, not just how fast the parser runs.
Survival LLM: AI assistant and emergency library that runs on your own computer
Survival LLM makes the hardware tradeoff explicit: it selects a model based on available memory, and its blackout and first-aid test ranged from 14/22 to 21/22 correct. The test used an earlier library build and only 22 questions, so those scores aren't a broad measure of emergency reliability. What catches my attention is the source display, which highlights the passage behind an answer, especially when smaller models make more mistakes. Offline access helps, but high-stakes advice still needs checking.
Google’s New AI World Model Can Generate Human Voices, Not Just Video
Genie 4’s weak point may be continuity: Google says visual consistency and audio accuracy still suffer in longer, more complex simulations. That matters if developers use prompt-driven worlds to prototype game interactions; a convincing short scene doesn’t establish that characters and sound will stay coherent as users change conditions. I find that limitation more interesting than the realism claim: how much iteration can teams tolerate before a prototype stops being a useful test?
Tailscale SSH: Findings and fixes
The failure Tailscale describes was in the privilege boundary after authorization: under certain conditions, an authenticated session could exceed its configured local user’s permissions, including through SSH forwarding. Exploitation still required an existing foothold on an authorized peer and SSH access allowed by tailnet policy. What catches my attention is that passing the access check doesn’t settle the harder question of what a session can do afterward. For systems that delegate privileged session setup, enforcement needs to hold across forwarding and user transitions too.
Ten days later, Git on macOS still trusts the compromised eMudhra certificates
The sharpest risk is that Git’s trust store can turn an HTTPS clone or pull into a path for attacker-chosen code, while exposing credentials in transit. The post says Apple’s October macOS update still left developer tools trusting compromised eMudhra roots and reverted users’ manual workaround, despite Safari already being protected. I’m struck by the gap between fixing the browser and fixing the tools used to build software. Until a system update fixes it, teams need to check and reapply the workaround, including on macOS CI runners.
Gemini Notebook can now record lectures and meetings without the upload shuffle
I find the one-hour cap funny, especially because a recorder meant to remove file shuffling still creates a boundary to plan around. The article says longer sessions need separate recordings; in my experience, an hour of speech roughly matches Gemini Flash’s output context limit. For longer audio, I need to split it across multiple model calls, which makes the cap less arbitrary but still adds handling work. For long meetings, plan on segmentation rather than one uninterrupted capture.
#Agents #AI #Obsidian #SoftwareEngineering