I create practical technical documentation designed to be used by the people who actually operate the environment:
- Network and system inventories
- Architecture documentation
- Standard operating procedures
- Engineering runbooks
- Troubleshooting procedures
- Configuration standards
- Operational workflows
- Knowledge transfer
Good documentation is more than an audit artifact. It is part of the control environment.
When appropriate and permitted, I use internally developed AI tooling to accelerate documentation development from authoritative source material, including genuine vendor documentation, existing configurations, engineering notes, and other approved technical evidence.
The important word is grounded.
I do not use AI to invent how an environment works. I use it to help organize, reconcile, and transform known technical information into useful operational documentation, followed by engineering review.
That approach lets me iterate quickly without sacrificing traceability or technical rigor.
The result is documentation intended to serve two audiences at once: the engineers who need to operate the environment and the auditors, assessors, or governance teams who need evidence that the environment is understood and controlled.
Where required, documentation can be structured to support NIST-aligned control frameworks, GAO/FISCAM audit expectations, internal control reviews, security assessments, and other compliance or governance requirements.
The goal is not documentation that merely exists.
The goal is documentation you can operate from, defend, and produce when someone asks, “Show me how this is supposed to work.”