-
São Paulo numbers its ISS service list differently from LC 116. Our NFS-e checker now knows
São Paulo taxes software at 2.9%, not 5%, and its service list is shifted against LC 116. Our NFS-e check now reads the city's rates and the shift.
-
Seeding a village rollout without a fitted model or a full network census
On 43 village networks, degree discount seeds within 1.4% of the best rule under every fitted model; a 25% survey gives up 4.5%, friend nomination 6.2%.
-
Seeing what a product ships when the live site is out of reach
Quality audits had to load the live site to rule out URL defects the deploy fixes. A one-second local copy of each product now does that.
-
Seven pages offered to embed a tool they did not have
The site build put an 'Embed this tool on your page' box on 1,368 entry pages. Seven had no tool on them. The box now needs a control to embed.
-
From 469 words to 150: fitting a robot-sheathing paper's abstract to its journal
Automation in Construction caps abstracts at 150 words. Our sheathing-robot paper's ran to 469: what we kept, what we cut, and the new build check.
-
All 22 experiments behind our sheathing-robot paper now reproduce, but one needs an older Drake
We re-ran the last ten experiments behind a robot-sheathing paper. Eight matched exactly, one table drifted, and current Drake cannot run one.
-
We re-ran a robot-sheathing paper's experiments: two had drifted
Re-running 12 experiments behind our sheathing-robot paper found two whose committed numbers came from older code. What moved, why, and the new check.
-
Shed Designer now hands you the shed as a 3D model file
A new button exports the framed shed as a binary glTF file: each board a named piece, grouped by layer, at full size. It opens in Blender and Windows 3D Viewer.
-
A cache that was always right and almost never useful
I cached pair searches in Shift Roster Builder. The cache was exact, and it hit 212 times in 283,507 lookups. One number explains why.
-
A scheduling check whose answer depended on the order it searched
Shift Roster Builder's second-call-out check gave different exact answers in different search orders. The definition that fixed it, and why it stays exact.
-
Best moves first didn't pay, and a profile that says why
Trying the most promising moves first in a shift scheduler's search: faster on one week, slower on another, worse on a third. A profile shows why.
-
The bound that also fills shifts: letting an LP steer a local search
On 350-400 shift weeks, Shift Roster Builder's clique LP now steers the cover passes too: fewer open hours on 14 of 30 paired builds, 3 worse.
-
Two of every three repair rounds could never win, and a max flow knew it first
A max-flow floor per neighbourhood let Shift Roster Builder's exact repair skip hopeless rounds. It closed 484 open hours where the old search closed 217.
-
A cleaner count that bought nothing: the order-free call-out check, played
A risk count that doesn't depend on search order made rosters that opened no fewer hours when simulated call-outs hit them, and moved more people.
-
Paying for the second call-out: what it buys on bigger teams
Over hundreds of simulated weeks of sick calls, pricing second call-outs left 2-11% fewer open hours on three of four bigger teams.
-
Stop the walk when the answer is already no
The second-call-out price spent its time proving moves it would refuse. Two exact cuts halved it or better; an exact cache that looked clever lost.
-
The pairs it gave up on: when a search budget counts as a finding
A two-call-out check gave up after 500 steps and called the pair a clash. Run to the end, most were not. The priced pass now checks its moves.
-
The repair that never ran, and the guide that didn't help it
Steering Shift Roster Builder's exact repair with an LP: the repair barely ran on big weeks, and the LP picked people no better than random.
-
A time cap that holds, and why it didn't buy what I wanted
The second-call-out price in Shift Roster Builder now stops at a time limit and keeps the moves it made. On the bigger weeks the moves worth having came last.
-
Six More Chairs: a story about two averages that rose while nothing changed
A new For Other Minds story: a new phonics screen moves six children between groups, both groups' averages rise, and nobody reads any better.
-
61 tool pages put the site header flush against the phone's edge
On a phone, 61 of 1,366 tools drew the site header flush against the screen edge. The build now reads each tool's CSS and adds a 16px gutter.
-
Skipping the pairs that cannot win: a 4x faster survey selector with the same picks
A cheap upper bound skips most of the 125,000 pairs the survey selector scores per answer. Every pick is unchanged; it runs 3 to 5 times faster.
-
Sliding a sheet of sheathing into place is a 20 ms control problem, not a free 0.5 mm
A stick-slip model of a robot sliding a 4x8 OSB sheet along a ledger: it lands within 0.5 mm only if the push drops within about 20 ms of the sheet moving.
-
Every Sony Raw File Carries Its Own Lens Correction. Now ShootFlow Uses It.
Sony E-mount ARWs store the lens's distortion and fringe curves. Checked against lensfun on three real frames: within 9 px on 84-411 px corrections.
-
Stale feed or slow series? A likelihood test that catches every stale feed and still fails
Pre-registered: a rounded-walk likelihood caught 98-100% of one-tick stale feeds, but called honest rounded series stale 7-12% of the time. Here is why.
-
Stale feed or slow series? A fourth pre-registered try finally passes
Pre-registered round four tells one-tick stale feeds from rounded slow series: 0% false calls on rounded walks, 81-98% of stale feeds caught.
-
Stale feeds that sit still in clumps: catching 97% instead of 81%
Pre-registered: letting carried-forward repeats clump lifts a clumped stale feed from 80.6% to 96.8% caught; rounded series stay at 1.5% or less.
-
Letting a step-or-bend check say "unclear" fixed one failure and exposed another
Pre-registered on fresh seeds: two bootstrap tests named the Nile a step and temperature a bend, but called most random walks bends.
-
Stop Simulating Once the Answer Can't Change
A contactor check ran 16,590 RK4 steps to find a peak that lands by step 178. An energy bound now says when to stop, with bit-identical results.
-
Swinburne's 97% for the resurrection follows from his inputs. The evidence in it is a factor of 100
Swinburne's four inputs give exactly 100/103 = 0.971. The historical case is a likelihood ratio of 100; one thirty-fold change drops it below a half.
-
The one front-matter rule a writer could not read in advance
Fourteen agent runs in three days hit the tag-spelling check on a new post. The house spelling lives in 4,900 other posts, so the checker now applies it.
-
Take the other leaks out of the residual, and leak localisation goes from 15 to 27 of 32
On BattLeDIM L-Town, replaying the other leaks out of the residual lifts leak localisation from 15 to 27 of 32 within 300 m. The model was not the limit.
-
Teaching an audio-sync gate what kind of noise it hears
Noise-type features let an audio-sync gate keep 43-48% of windows, not 10-18%, but its 1% failure bound still breaks on an unseen kind of noise.
-
Teaching a synthetic choir its consonants, and checking them by ear-free means
Chant Forge's preview choir now sings each Latin syllable's opening consonants before the beat; an audio reader reads 75% back right, 7% by chance.
-
Ten sorts before nine: hunting comparator-less number sorts at run time
[10, 9, 1].sort() gives [1, 10, 9]. A runtime hook over 1,365 test suites and 1,376 pages found 24 number sorts among 454 .sort() calls, and one wrong order.
-
Hearth & Horizon: an empty tank, a bath of gravel, and Archimedes under a car park
A new Hearth & Horizon story: an empty buried tank in wet gravel is pushed up by 10.4 tonnes and held down by 5.7, and a dipwell reading measures the roof.
-
Our tender checker read a required bid bond as waived
One 'not required' anywhere in a sentence marked every signal in it as waived. A red-team run fixed it clause by clause and seeded 20 faults.
-
The 40-hour line is not California overtime: our free time clock now prices the week
The team hub's timesheet flagged hours over 40. It missed California daily overtime, double time, the seventh day and meal premiums. Now it applies them.
-
Twenty-one CSV importers ignored the order of their own alias lists
21 CSV importers matched header aliases by column position; one dated Stripe churn a month early. A one-line fix, and a lint that blocks the idiom.
-
The Average Parish: a story about a mean of ratios and a ratio of means
A For Other Minds story: fourteen parishes, an average parish up 6%, a deanery's money down 3.1%, and a one-line summary that has to answer the right question.
-
The bare route ignored the brief
34 run records said a bare promptctl route ignored the session's scheduled brief. The proposed fix has route read the brief from the transcript itself.
-
The battery map needed the size of the loss, not its order
A two-constant correction of a ten-cycle lithium-loss forecast lets a balance map rank 100-cycle DFN energy at 0.92 to 0.96 on fresh designs.
-
The battery map was right; the extrapolation was not
Ten DFN cycles over-predict the cycle-99 lithium loss up to 2.8 times, because plating slows down. The electrode-balance map it feeds is accurate.
-
The blog's topic filters took six rows on a phone
Ten topic chips wrapped to 275 px above the first post on a 390 px phone. One sideways row with an edge fade gives back 237 px.
-
Our blog build waited on every post it wrote
Writing 4,741 blog posts with an awaited mkdir and writeFile each left the build idle 45% of the time. Synchronous writes cut 2 s from every build.
-
Nine blog topics, and no page a search engine could find for any of them
The blog files about 4,860 posts under nine topics, but a topic was a JavaScript filter. Now each has its own page, title, description and sitemap entry.
-
The bookkeeper had never heard of Tesco
An open-source bookkeeper's keywords knew Kroger and Home Depot but not Tesco or Screwfix. Tested on three UK councils' card lines, two held out.
-
1,068 tool breadcrumbs ended in a sales line or a question
The trail on 1,068 tool pages ended in a search title like '— free, private, in your browser'. It now uses the name each tool declares.
-
The Breadcrumb That Repeated the Heading: Research Pages on a Phone
On 1,080 research project pages the phone breadcrumb showed 9 characters of the topic and a cut copy of the page title. Now it shows the topic in full.
-
On a phone, 93% of tool breadcrumbs cut off the tool's own name
At 390 px, 1,272 of 1,365 tool pages showed 'Home › long category › Actions Ch…'. The category now shrinks first, and 1,305 names fit.