Build1 distinct publisher3 min readPublished
Shipping meeting assistants mark coverage the moment a topic comes up. Junwei Lai's intake adjudicates each open item in its own call and defaults to insufficient, which pushes the missing answer back into the room while the patient is still there.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
Mention-detection ships because its trigger is observable. Microsoft's Facilitator marks a topic covered once the discussion for that topic has started [1], which is a claim about the agenda rather than about the record, and Balto ticks when an item is mentioned [2]. Both verdicts are decidable from the transcript alone, and both fail without noise. A wrongly ticked item raises no error. It produces a blank field the practitioner finds at her desk that evening, when closing it costs a phone call or a second visit [6].
Adjudication is the harder problem because the verdict is a judgement: does "a couple of wobbles" satisfy a form item that asks for the number of falls and the circumstances of the most recent [7]. Junwei Lai's build, called intake and written for an August 2026 hackathon [8], makes that judgement the gate and then spends the engineering on making it cheap.
Two mechanisms carry that. The first is that the slot state is the state, not the transcript. The obvious design accumulates the conversation and re-asks the model what is still missing each turn, which turns a forty-five minute interview into tens of thousands of growing tokens that degrade as they grow [18]. Instead, each call receives the open items, a fixed-size struct of current values, and the new audio, so a three-hour interview costs the same per chunk as a ten-minute one [19]. Flat per-chunk cost is what makes a long home visit affordable at all.
The second is fan-out behind a router. Each open item gets an isolated adjudication call, so a wrong verdict cannot corrupt a neighbour, each item is separately scoreable by the eval, and k concurrent calls cost about one call's wall time [20]. The bill is tokens, not wall time. Without the router, every open item was adjudicated against every chunk, and each independently decided a vague remark was relevant to it, so "a couple of wobbles" attached itself to mobility, memory and low mood as well as falls [21]. One cheap classification call cut items touched from seven to two [22]: a 71 percent reduction in adjudicator calls per chunk [23], and five fewer chances per chunk to be wrong about the same sentence [27].
Then there is the line that proves the intent. The coach's output schema has a field for a question and a field for quotes, and no field an answer could go into, so it structurally cannot suggest one [25]. The agent tracks coverage against a human-authored form and quotes the span it relied on, saying that item M14 has no recorded answer rather than that something may indicate falls risk [24]. That is the right place for the rule, because a prompt instruction is advisory and a schema is enforced.
The numbers transfer only under conditions the writeup names. The 47 labelled cases are the product, and they were authored by the same person who wrote the prompt [9]; the harness exits non-zero when an answer labelled insufficient is marked sufficient [10], which is the operating point that matters, because a false sufficient is indistinguishable from the mention-level behaviour being replaced [11]. Twelve of the cases are adversarial [13], and Lai's own standard is worth keeping: a set that scores 100 percent on its first run cannot tell you anything [16]. The text available to us stops mid-sentence before any behavioural evaluation figure [26], so the accuracy is unreported rather than good. Per-item isolation also assumes items are independent; a form whose item is derived from three other answers breaks the fan-out.
Ranked by verification strength, evidence, and original report placement.
The first thing built was not the UI but an eval harness; eval/ holds 47 labelled cases, giving for each required item answers that should count and answers that should not.
The harness scores the adjudicator against the live service and exits non-zero if any answer labelled insufficient was marked sufficient.
The naive design accumulates the conversation and re-asks the model what is still missing every turn, so a forty-five minute interview becomes tens of thousands of growing tokens, expensive and degrading as it grows.
Instead each call gets the open items, a fixed-size struct of current values, and the new audio, so a three-hour interview costs the same per chunk as a ten-minute one.
The available text of the writeup ends mid-sentence at "Behavioural evaluation found th", so it reports no pass rate or accuracy figure for the eval harness.
In the scenario the author uses, a community nurse has ninety minutes and a form she is legally required to complete; she asks about falls in the last twelve months and the answer is "Oh, I've had a couple of wobbles", which every AI scribe on the market ticks.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 31, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
An ACT floor of 0.90 lands inside the model's own 0.85 to 0.95 confidence band1 distinct publisher
build
CrisisMesh paged its floor warden about the same missing teacher every 25 seconds1 distinct publisher
build
One instruction to delete the sample data surfaced three invisible defects in an hour1 distinct publisher
build
Gemini 3.7 Flash goes GA on one model layer, and that is the actual news1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Specific, self-reported, unchecked
The engineering detail is unusually concrete for a hackathon post — 47 labelled cases, twelve of them adversarial, a named bug with the transcript that caused it, a router that took items touched from seven to two — and all of it is checkable against a public repo. None of it has been checked, by us or anyone else. Two things hold the score down: the comparative claim about Teams, Balto and Otter cites no vendor material, and the number that would decide the whole argument, how often the adjudicator gets sufficiency right, never appears before the text breaks off.
A repo and a running instance, nobody using them
Adoption here is one deployed service the author's own harness can call, plus a GitHub URL posted the same day. No practitioner, trust, clinic or pilot appears anywhere; the community nurse who anchors the argument is an illustration. That is the expected footprint for a hackathon entry, and it is close to the floor.
Restrained prose, one unearned comparison
Most of this post undersells itself: it publishes its own bug, admits a privacy claim is narrower than the slogan, and argues that an eval set scoring 100% on the first run is worthless. The overstatement sits in one seam. The project positions itself as beating mention-level products, and the story it appears in frames that as pushing the missing answer back into the room, while the harness result that would justify either statement is absent and the competitors' behaviour is characterised without documentation.
Hackathon deadline, Google stack, named rivals
This is a submission, and submissions are written to win. The author is judged on a build completed for an August 2026 hackathon, the entire stack is Google's, and the sharpest paragraph is the one asserting that Microsoft, Balto and Otter all stop short of what his project does. An unedited note to self — set published: true when you post it — survived into the published text, which tells you how close to the deadline this went out. Nothing suggests payment or a vendor relationship; the pull is reputational and competitive rather than financial.
Clear on what was built, blind on how well
We can say with reasonable certainty what this system is and how it is meant to fail, because the design is described precisely and consistently and the code is public. We can say almost nothing about whether it works, and only the author's word stands behind the competitive baseline. One publisher, one witness, one truncated text — enough to assess a design, not enough to assess a result.