AI search that shows its working

Type "we need an ABM manager" into cord's AI candidate search and there is almost nothing in the sentence to filter on. cord searched anyway, on whatever it could pull out.

It now works out what the role implies, shows you where each guess came from, and waits to be told to go.

Additional Features

• What it fills in: A prompt that states no requirements gets skills, titles and seniority inferred from cord's own data, with a line explaining each one. What cord decided against sits in a collapsed "What else I considered". A prompt that already says what it wants skips the stage entirely.

• Where the numbers come from: Every figure in the explanation is read off cord's pool rather than written by the model. 135 verified people hold the Account Based Marketing skill, and their job titles are Head of Marketing (40%), Growth (30%) and Digital (24%), so those are the titles the search targets. A skill fewer than 25 people hold is left out, as is a title with fewer than 150 people behind it.

• It waits to be told: An inferred filter is a guess, so the search stops and asks before it runs. Anything that isn't plainly a yes is read as a correction, which is the recoverable direction to get wrong.

• Refining continues the conversation: A follow-up used to replace the whole exchange and reopen with "Got it, looking for a...", so changing one thing read as starting over. Earlier turns now stay on screen above the live one.

Fixes

• The readback reads as a sentence: Of 675 saved search names, 16% were plural ("a Software Engineers"), 15% opened on a vowel ("a AI Engineer") and 37% carried no role noun at all ("a Senior React"). The role is now written separately from the name, so "a AWS Cloud Engineer London Hybrid" reads back as "AWS cloud engineers".

• Skill chips: An inferred set of skills matches anyone holding one of them, but the chips said AND. Six inferred skills read as though every person had all six. The row now shows what the filter actually does.