The runbook was right the last time someone ran it.
But is it right now?
Infrastructure, APIs, tools and environments move. A runbook that was correct when written drifts silently, and nobody finds out until it fails in the middle of an incident.
- ✓open the credentials vault
- ✓request rotation approval
- ✗step 3 · rotate and update the secret · field renamed on 3 June
- ·re-run the connection check
change detected · revision drafted for review
Technical procedures you can check against reality, from inside your own environment, on a schedule.
Don't just document the process. Check that it still works.
Supported guides run against the systems they describe, from inside your environment. Nothing needs to be reachable from the internet; it runs where the credentials already are.
Runs where your systems live
- Credentials stay local
- Screenshots stay local
- Private systems stay private
nothing leaves except the result
- Guide
Rotate database credentials
revision 3 · supported guide
InteractiveDox sends the run, receives the result
- Your machine / agent
Your machine
run now
Your scheduled agent
run on a schedule
- Private system
- Browser
- APIs
- Cloud infrastructure
- Kubernetes
- Database
credentials · secrets · screenshots stay here
- Verified
Every step matched
evidence recorded · result returned
If a step had not matched: flagged, revision drafted for review.
run · rotate-database-credentials · r3 · your-machine
- 00:00.4✓open the credentials vault
- 00:01.9✓request rotation approval · approver present
- 00:03.2✓rotate and update the secret
- 00:04.8✓re-run the connection check · 4/4 services reconnected
- 00:05.1●verified · 4 of 4 steps · evidence sealed
Run now
Verification executes from your machine against the systems and credentials you already use.
Run on a schedule
A customer-hosted agent can re-run supported guides against private systems on a schedule.
Your environment stays yours
Credentials, secrets, and validation screenshots remain local to the execution environment.
A change becomes a drafted revision, not a surprise during an incident.
- 1Change detected at the step that no longer matches
- 2Updated revision drafted, with the evidence from the run
- 3Human review decides what becomes the current runbook
For API reference, specs are imported and pages follow the spec; drift is checked the same way.
Only what solves this problem.
- Runbooks
- Technical procedures
- Browser / API / cloud / database validation
- Local execution
- Scheduled verification
- Human review of changes
Documentation that can be checked against reality.
01
Supported guides run against real systems
02
Runs from your machine or a customer-hosted agent
03
Credentials, secrets and screenshots stay local
04
A change becomes a drafted revision for review
Know the runbook is right now, not just the last time someone ran it.
Technical procedures you can check against reality, from inside your own environment, on a schedule.