How it works
Publish the guide once
Nothing extra to set up beyond the guide you already made.
Maintenance
Libraries that refresh themselves when your product changes.
The Clueso agent re-runs an existing guide against the current product and regenerates what changed, so a library stays current without anyone re-recording it.
Written six months ago, against the UI of the time.
What Clueso does
Re-runs it against the live product
Triggered runs, with a cap on how many go at once.
What you get
A library that doesn't rot
The stale-content problem stops being a person's job.
What it actually does
The controls an evaluator asks about, not a restatement of the headline.
Triggered, not manual
Runs fire on a trigger rather than waiting for someone to notice the guide is wrong.
Concurrency is capped
A limit controls how many guide runs go at once, so a refresh sweep can't swamp anything.
A cap on eligible guides
How many guides are eligible for automatic refresh is itself a limit.
Shares the recording path
The same orchestration that produces a new recording produces a refreshed one.
Without it
With Auto Updates
Without it
A guide was correct on the day it published and quietly wrong for every month after.
With Auto Updates
The guide tracks the product. Drift is handled before a customer finds it.