System changes
A screen, field, permission, or workflow path changes after the procedure was approved.
The difference is what happens after publish.
InteractiveDox re-checks approved procedures against the systems and rules they describe. When a step goes out of date, a fix is drafted for review instead of quietly misleading the next person.
Rules change
A policy, regulation, requirement, or operating standard changes underneath the documented work.
People change the handoff
The informal handoff changes, but the SOP, video, course, or portal still teaches the old path.
validation run
What a check hands you.
Not an alert. A record of work that actually ran: every captured step replayed against the live product, a screenshot kept for each one that cleared, and a written result filed against the document. Here is that run, screen by screen.
Everything the team has captured, in one tree: recorded walkthroughs, runbooks and authored documents.
It replays, it does not guess
A real browser follows the recorded steps against the live product and captures proof for each one.
It asks instead of storing
When a step needs a credential or a judgement call, the run pauses and asks. The answer is used, then hidden in the record.
The run is the evidence
Screenshots, timings, and a written verdict stay attached to the document, so the next check has something to differ from.
Will it work against your system?
The honest answer, by surface. Sensitive checks run on infrastructure you control. The checker uses credentials you approve, and InteractiveDox never needs standing access to production.
browser workflows
every planA real browser replays the documented steps against the live system, on the schedule you set or after releases.
systems behind the browser
enterpriseHTTP APIs, SSH, databases, and cloud systems through enterprise adapters, running on machines you control.
rules & regulations
enterpriseRegulation watch monitors the rules a document depends on and flags changes with sources.
routine doc health
every portalLinks, translation freshness, search setup, spelling, grammar, and writing style, checked automatically.
NewAutomated checks
Watch InteractiveDox test your SOP, then fix it in front of you.
A check replays every captured step in a live browser, proves what passed with screenshots, and asks you when it needs a value. What comes back is a set of repairs you can accept or reject.
Live run
✦Heal runheal_3f822783Running
1 of 12 · 8%
5m 55s
Steps · 121 passed0 skipped
✓1. Navigate to /login (Cognito hosted UI)Passedbrowser
2. Click "name@host.com" email fieldRunningbrowser
3. Enter the email addressQueuedbrowser
4. Click the password fieldQueuedbrowser
5. Enter the passwordQueuedbrowser
6. Click "Sign in"Queuedbrowser
7. Follow callback code redirectQueuedbrowser
8. Exchange stale auth tokenQueuedbrowser
9. Open PMO HUB → IssuesQueuedbrowser
10. Open project settingsQueuedbrowser
11. Scroll to the Danger ZoneQueuedbrowser
12. Assert Danger Zone is visibleQueuedbrowser
▢Agent activity
• Status
Heal agent ready. Capabilities: Browser (Playwright).
It actually replays the flow
A real browser follows your recorded steps against the live product and captures proof for each step.
It asks you when it's stuck
If a value needs human judgment, the check pauses and asks. Answer once and it keeps going without storing brittle secrets in the recording.
You approve the repairs
Every outdated step becomes a before-and-after change you can accept or reject before the docs, video, and API page update.
Runs on your machine, with your keys
Bring your own AI key if needed. Give the checker access only to the systems it needs. Secrets stay in your OS vault and are never shown back.
BrowserHTTPSSHAWSDockerKubernetesGCPAzurePostgresMongoDB
Verification questions, answered.
What is documentation verification?
Documentation verification means checking whether an SOP, guide, training flow, or walkthrough still matches the system, workflow, or rule it describes. InteractiveDox can run that check on a schedule and identify the specific step that went out of date.
What does it mean when guidance is out of date?
Drift means the approved guidance is now out of date. A button moved, a field changed, a permission differs, a rule changed, or a handoff evolved while the published procedure stayed the same.
What happens when verification fails?
InteractiveDox flags the affected step, records evidence from the run, and drafts a revision. The drafted update is routed for review so a human can approve or reject the change.
Can verification run inside our environment?
Enterprise verification can run on customer-controlled machines and networks, using only the credentials and connected systems approved for the workflow being checked.
What systems can InteractiveDox verify?
InteractiveDox can verify browser workflows and can support desktop apps, internal services, cloud systems, and databases depending on your deployment.
Does InteractiveDox automatically publish changes?
No. InteractiveDox can draft the correction, but official publication remains controlled by your approval process. AI detects; humans decide.