-
Checking a Brazilian NF-e before SEFAZ does: a schema in 63 KB and the sums behind cStat 610
E-invoice Preflight now reads Brazil's NF-e and NFC-e 4.00 XML in the browser. Its schema check agrees with xmllint on 2,600 of 2,600 mutated files.
-
Thirty lines of 0.047 rials: rounding each line first gets an Oman e-invoice wrong
Oman invoices price lines to three decimals. Rounding each line first gave false totals; the repair even broke valid files. Now 49 of 49 examples pass.
-
The repair button added 148.50 of VAT to a correct UAE invoice
Scoring our e-invoice repair on OpenPeppol's UAE and Malaysia examples showed it edited 16 correct files. Now none, and Oman restores 657 of 658 faults.
-
Fixing a Saudi e-invoice's arithmetic: 42 of 258 seeded faults to 257
Our UBL repair declined all 19 of ZATCA's example invoices. Now it puts back 257 of 258 faults we planted in them, and every repaired file passes.
-
A Saudi e-invoice can state two VAT totals, and no rule checked they agree
Every SAR invoice under ZATCA states its VAT total twice, and no published rule checks the two agree. Now 17 of 17 planted mismatches are flagged.
-
Every lumber length was even, so the optimizer did twice the work it needed
Every lumber length in the optimizer's knapsack was even. Dividing out the common factor cut our slowest engine test by 28%, same answers.
-
Five Canon bodies, two surprises: a neutral white balance and a clip that isn't at the top
ShootFlow's CR2 reader on four more real Canon bodies: one file refused, one with pink highlights, and how each file supplied its own fix.
-
Four even terms are not enough for one lens in six
ShootFlow now runs the DNG 1.6 WarpRectilinear2 opcode. On lensfun's 5,440 real lens profiles, the older opcode can't get within a pixel on about 17% of them.
-
How eager should a metric alarm be? Ask the metric's own past
Picking a change alarm's eagerness from the series' own history beat the fixed default on labelled data, but by one marked change in 31.
-
How many alerts a month would you put up with? A budget box for a metric alarm
The changepoint detector's eagerness hint now takes a budget as 'about n alerts a month'. On one real series, 6 a year and 7 a year give different answers.
-
Stale or just rounded? A test that almost worked, twice
A pre-registered check telling a one-tick stale feed from a rounded slow series failed two rounds, one by a single series. Here is the trade-off it found.
-
One day off, four people moved: keeping a rota steady
A rebuilt roster moves people who were not off. Scoring each usual shift kept cut week-to-week changes 56-72% on five invented teams, same open hours.
-
A 31-team round robin: from 245 back-to-back home or away games to 60
Leagues of 15 and 31 teams missed yesterday's home/away fix. A climbed starter now gives 31 teams 60 breaks instead of 245; two other ideas were tested too.
-
Home-and-away seasons for 11 and 13 teams: less carry-over and fewer back-to-back games
Home-and-away seasons for 11 and 13 teams now start from a capped shift starter: lower carry-over and fewer breaks. A 15/31-team idea changed nothing.
-
Ten searches, four results: re-measuring the league scheduler's carry-over choices
The league scheduler's four carry-over choices measured on its own ten searches against 20 real top-flight seasons, and why 19 teams got one season 7 times.
-
Minutes a ticket, minutes a euro: a labour standard from a till export
The roster builder now plans shifts from minutes a ticket, a euro and an item. On a real bakery, ticket-heavy plans were steadier week to week.
-
One alert a month, as a setting: picking how eager a metric watch should be from its own history
The Changepoint Detector's daily watch can pick its own sensitivity from your history, within a budget like one alert a month. Measured on TCPD.
-
A string for every pair: Quick Pick Survey's pair picker, four times faster with the same answers
Building a lookup key for each of 125,000 pairs took most of the selector's time. Skipping it: tests 630 s to 151 s, results byte-identical.
-
Careless or just different? Answer times can tell, if the careless are quick
In simulation, answer pace never mistook a genuine minority for careless clickers, and caught them as far as they were quicker. Shipped as a note.
-
Telling coin flippers from a camp in a pairwise survey, and why it's hard
On real rankings, 18-46% of honest people disagree with their panel. A check on each person's own consistency spares them; adaptive questions blunt it.
-
Letting each person's answers set the prior, and the textbook shortcut that broke it
A prior set from each person's answers lifted the favourite list from 88-92% to 93-96% coverage, once the Laplace evidence was replaced.
-
We gave a survey's intervals a heavier-tailed prior. They got narrower and wrong.
A Student-t prior should fix a Gaussian that over-shrinks extremes. In 108 simulated survey cells it covered less every time, even on heavy-tailed truth.
-
Switching a survey's default question order, after checking what it costs
The question order that can name your favourite is now the default up to 120 options. Careless-respondent sims under both orders found one cost.
-
Pooling a survey's answers helped the average respondent and hurt the hardest ones
A prior pooled over a survey missed the favourite for people whose likes sit close together. The narrower of theirs and the pooled one reached 95%.
-
The top-pick card on 72 real people: honest, and silent unless you change the question order
On real rankings the top-pick card was right 855 of 860 times and its contender list held the favourite 97-100%, but the standard order rarely names one.
-
"It's between these three" missed a third of the time: a credible set for your favourite
The old list of the three highest-rated items held the real favourite 68-74% of the time; a credible set from the refit holds it 88-92%.
-
Decoding raw photos ten times faster, still with no dependency
ShootFlow now decodes a Canon CR2's 22 million raw samples in about a second instead of nine, through an optional C reader. Same samples as LibRaw.
-
Reading a receipt photo twice in the browser, and letting the receipt check itself
The bookkeeper page now reads each receipt photo twice with tesseract.js. On 626 real SROIE scans, totals went from 78.4% right to 79.8%.
-
Reading the DNG specification after writing eleven opcodes from memory
ShootFlow's DNG opcodes were written without the spec. Once we could fetch it, everything matched except where the lens centre sits: between pixels, not edges.
-
Receipt photos from a phone: the wrong answers that said nothing
On 200 real phone photos the in-browser receipt reader got half the totals right, and most wrong ones were silent. Now 12 of 95, not 39, are.
-
Reordering the pieces saves 2 to 5% of the cloth
The nesting marker now searches the order it lays pattern pieces in: tee, crewneck and hoodie markers 2 to 5% shorter; long sleeves did not move.
-
Replay an alert on your own history before you trust it
See which alerts the free changepoint watch would have sent on your own history, and how late. A coarse replay matched 85% of alerts on 57 real series.
-
Romania's e-invoices are checked against an older rulebook than ours
Romania's CIUS-RO 1.0.9 is built on EN 16931 1.3.8, so a newer rule, UBL-SR-53, rejected ANAF's own good examples. Running the right base fixed it.
-
A free 7B model reads sales replies better than our rules, and still can't be trusted with a stop
A free local 7B model reads unfamiliar sales replies far better than keyword rules, but mistakes live leads for opt-outs. How the agent now uses it.
-
We asked a free local model to check our sales agent's grading. It graded like the rules did.
Llama 3.1 8B, run locally with no key, labelled 298 real Enron replies. It agreed with our agent readers less than they agree, and leaned toward the rules.
-
The free page gets the call buttons too
Sales Agent's free page now marks each due call Spoke, Voicemail or No answer, re-queues misses, moves later steps and remembers it all in your browser.
-
Call outcomes without a server: one CSV row per dial
Sales Agent's CLI now reads a calls.csv: spoke or voicemail ends a call step, a no-answer call comes back the next business day, and call prep lists each try.
-
Your Sent folder knows which emails you sent. It has no idea you made the call.
Sales Agent's self-hosted server now has a Done button for calls, LinkedIn touches and letters in its daily queue, kept across restarts, with Undo.
-
Don't book the next call on their holiday: call prep now knows the prospect's days off
The sales agent's call brief now lists the prospect's next days off, and the follow-up email flags a next step dated on one.
-
When a cold call rings out, the rest of the cadence should wait
Sales Agent now moves a prospect's later steps back when a call is retried, and keeps retries off US holidays, so nobody gets a call and an email the same day.
-
A call that rang out is not a call you made
Sales Agent's Today's queue takes an outcome per call: no answer brings it back the next business day, up to three tries, and call prep lists each try.
-
Seven out of seven was luck: a pre-registered test on a local model fails
A 14B local model got 7 of 7 right on a small sample. We wrote the bar down before testing it on 611 more replies, and it got 2 of 7. Nothing shipped.
-
Twice the model, mostly the same mistakes: a 14B local model reads sales replies
A free 14B model on four CPU cores reads sales replies slightly better than a 7B, still reads live leads as opt-outs, and is no better as a second reader.
-
Good Friday is not a business day: UK bank holidays in the sales agent, checked against GOV.UK
Call retries in the sales agent now skip UK bank holidays. A test against GOV.UK's own file caught an Easter bug and a one-off holiday.
-
Texas works Columbus Day: 51 US state holiday calendars in the sales agent, checked against python-holidays
The sales agent's days-off list now takes all 50 states and DC. Its US federal rules, unchecked until now, match a second source too.
-
Seven million questions, one in eight answered yes
A shift roster builder asks 7.7 million times per week whether a person can take one more shift. Asking fewer times cut its build time by about a sixth.
-
Did the backtest cheat? Checking a scheduling win against what the shop could have known
Staffing a closed hour now counts as spare by default, so auto can plan from the last 4 weeks. 77% of the gain survives a hindsight-free check.
-
The proof was faster than the guess, so now it always runs
The roster builder's exact check now runs on every week. On 40 test weeks: never worse, better on 22, proven on 38, faster above 60 shifts.
-
Wiping tables doesn't scale with customers: fixed work in a staffing plan
Fixed minutes every trading hour, at opening and at closing. Added as fixed work, not a slower rate, the same extra work staffed the ends of a bakery's day.
-
Four weeks without a freeze: the roster planner moves off the main thread
Planning four weeks of rosters froze the page for 6.2 seconds. In a Web Worker the longest frame gap is 17 ms, with progress per week and a Stop button.