The rules engine really runs

Nothing on this page is a recording. The evaluation is about 1,400 lines of TypeScript running in your browser, on whatever text is in the message box. Paste your own inbound and it will be parsed, scored and routed by the same code. There is no server call and no API key.

The replay clock only paces the reveal. The answer is known before the first connector turns green. Same input plus same rules gives the same score, the same route and the same reply, every time, which is what makes it safe to screen share.

The extraction is keyword work, not a model

Nine fields are pulled out with regular expressions and keyword tables. That is honest and it is also fallible, which is the point. Every field carries a confidence number, and anything under the threshold is held rather than guessed.

In production the extractor is the piece you swap for a model call, and the route becomes a real CRM write. The confidence gate, the scoring weights and the ordered rules stay exactly as they are. That gate is the part that matters, and it is the part a model does not give you for free.

The refusal has a real donor

Attio has this exact moment. Its checklist shows an amber icon tile with a warning triangle next to plain grey copy, and its unconfigured blocks carry a rose warning chip on the node card. Triage reuses both, unchanged, for a held extraction. Attio never colours warning body text, so neither does this. Three colours, and the restraint is the craft.

Where this breaks the 1:1 rule

Attio is a two pane app wearing a nav rail. Triage needs three panes, so the left pane holds the lead instead of navigation. Its width, its surface, its right edge and its section headers are all Attio, measured and unchanged. Only the content inside it is different, and that is the one structural break.

Three things have no donor anywhere in the capture set and are original work in Attio's vocabulary. The score readout is built out of Attio's own stat block, which is why it is a plain black number with no meter, gauge or gradient. The drafted reply panel is built out of the node card header and the config footer. The narrow layout is invented, because every Attio capture is desktop only and there was nothing to copy.

Things worth trying

Open the Rules tab and drop the confidence threshold to 0.50. The budget figure becomes trusted, the score jumps, and the lead reroutes to enterprise leasing. Raise the score condition to 82 instead and the same lead falls to the nurture branch. Run history keeps both, so you can click back and compare.

The voicemail preset has no email address in it. Watch what the engine does rather than what it invents.