Documentation / Modules
Documentation & credentials
Documentation that reconciles against observed state, and a credential vault where access is itself audited.
Documentation that checks itself
Documented facts reconcile against observed state continuously. A document that stopped being true becomes an exception the day it drifts, not at audit time.
Every documentation platform rots by default. Drift detection is the answer to that, and it is why documentation lives inside the platform rather than beside it.
Change detection
What changed in this tenant since Tuesday, and who changed it — ranked by consequence rather than recency. A domain controller change outranks a workstation's, and an undocumented change outranks a documented one.
Where the source cannot attribute a change, it renders unattributed — never guessed, and never left blank as though nobody asked.
The vault
- Credentials encrypted at rest with keys never present in the application
- Access itself audited — who read what, when, and why
- Rotation tracked, with age surfaced
- Break-glass credentials excluded from automation by construction
What Genie can and cannot do
He reads documentation to answer questions and proposes updates where he observes drift. He never edits a document or reads a credential outside an action that needs it — and every such read is recorded.
Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.
Thirty days · read-only · no card
Run it beside what you already have, against your real clients. It tells you what your tools are reporting that is not true.