Terry Taylor
Security engineer and architect in Seattle: cloud security, identity, infrastructure, and security automation.
Most of the engineering work here belongs to one program, built in public with an AI coding agent under a written rulebook, with every change reviewed by a person.
What is here:
control-plane
The platform the applications run on, an AWS estate as code with every security choice explained beside it. The plan is written; the code is next.
manifest-identity
An application for reviewing who has access to what across an organization's cloud accounts and directories. It keeps a record, written by a named person, of what access each identity may have, imports what the systems report, and puts every difference in front of the person responsible. It never changes anything in the systems it reads.
build-doctrine
The rulebook. Standards for letting an AI agent write code a person is responsible for, with a scorer, a vetting tool, and a project template.
secure-expense-mvp
A small application that carries application security end to end, built before build-doctrine existed, as a learning exercise and kept as a reference.
sample-diagrams
Architecture and process diagrams, kept as point-in-time illustrations.
aws-azure-security-mapping
Ninety-nine AWS security concepts mapped to their closest Azure counterparts, including the ones with no clean equivalent.
anki-decks
Seven study decks, 1,262 cards, each with a CSV twin so a card change diffs line by line.