Executable guides
Stop describing the steps. Show them.
Four tiers of helpfulness instead of one. A cited answer, a guide card, an on-screen walkthrough on the customer’s real page — or, with consent, the agent doing it for them.
How it works
It escalates until the customer is actually unblocked.
- Tier 1A text answer with citationsGrounded in your own content, with every source named. Fine when the answer is a fact.
- Tier 2A guide card with step previewsWhen the answer is a procedure, the agent hands over the procedure — not a paragraph about it.
- Tier 3"Show me"A ~25KB runtime spotlights the real control on the customer’s actual page and advances on their actual click.
- Tier 4"Do it for me"The agent performs the steps behind a consent HUD, one at a time, with Stop always one click away.
In the product
Running on a live page
Dimmed content, one ringed control, an anchored tooltip. The customer never leaves the page they were stuck on, and never has to map a screenshot onto their own screen.
walkthrough-live.pngThe walkthrough on a live page: dimmed content, ringed control, anchored tooltip
The detail
Why a competitor cannot retrofit this.
It runs on structured element dataRanked selector candidates, roles, accessible names and positional hints, all recorded at capture time. A tool whose capture output is a PNG and a sentence has nothing to replay.
It survives navigationSPA route changes and full page loads both, because every step carries its own URL alongside its selectors.
It degrades honestlyWhen an element genuinely cannot be found, it falls back to the static guide and reports the failure into the loop. It does not point at the wrong button.
A ~25KB runtimeSmall enough that it cannot be the reason your page feels slow — which matters, because it loads on your customers’ pages, not yours.
Consent HUD for Tier 4Verified domains only, never payment or password pages, never a field marked sensitive, and every executed step audited.
Typed values come from the userCollected through a secure prompt and never generated by the model. The agent can click for you; it will not make up your email address.
Where this sits
Executable guides are capture and the agent, joined at both ends.
01Capture
02Knowledge
03Engage
04AI agent
Capture flows to Knowledge, to Engage, to the AI agent; a miss becomes a work order and a resolution becomes a draft, feeding back into Knowledge.
Honest limits
We have deliberately made this refuse in several situations.
You will find this section on every feature page. If a constraint would annoy you in week two, we would rather you knew in minute one.
- Verified domains only. Cairn will not drive a page you have not proven you control, which means setup is a step rather than a switch.
- Never on payment or password pages, and never into a field marked sensitive — even with explicit consent. There is no override.
- A page that renders to canvas with no accessible names cannot be walked. It degrades to the static guide, and the failure is reported rather than hidden.
Next
01 · CaptureRecord the work. Not a video of the work.A screen recording cannot be searched, cited, or replayed. Cairn records structure — the elements, the labels, the order — and generates everything else from it.Self-healing loopDocumentation doesn’t rot because people are lazy. It rots because nothing tells you it’s wrong.Two return paths nobody else has. A miss becomes a work order. A resolution becomes a draft. Usage improves the asset instead of wearing it out.