I am a security engineer and architect in Seattle, working in cloud and identity security for regulated and federal environments. I have taken two organizations from gap assessment through Cybersecurity Maturity Model Certification. Most of the repositories below form control-plane, a security engineering program built in public with a governed coding agent: every change agent-proposed, human-reviewed, signed, and gated, with the decisions and the failure record kept on purpose. The diagrams repository stands on its own.

• role-call is an inventory and governance tool for non-human identities, the roles, service accounts, and access keys nobody offboards. State is derived from observed history rather than stored, and the tool amplifies a human decision rather than acting on its own. Complete through its version one scope and tagged, with build provenance attestations on every release artifact; it runs on Docker Compose or a hardened local Kubernetes cluster from a fresh clone.
• build-guidelines holds the standards, enforcement, and verification procedures every project here starts from. Each rule names what enforces it and the failure that produced it.
• secure-expense-mvp is a small expense application with object-level authorization, tokenized values, audit logging, and a security-gated build pipeline. Each control is mapped to the threat it addresses.
• sample-diagrams holds hand-drawn architecture and process diagrams, kept as illustration-only examples of design work.

CISSP · Terraform Associate · CCNA · Microsoft Expert x3