Projects
Pipelines I built and run. Each one gets the same treatment: the problem it exists to solve, the stages it actually runs, what broke and what I did about it, and the code that fixed it. The bugs are the interesting part, so they are not skipped. For the subsystems these run on, see Platform.
- Automated server provisioning. Builds a server as one consistent fact across five systems at once, with a collision gate that refuses to reconcile a live host by accident. Read the full write-up →
- Automated certificate and secret renewal. Certificates and secrets across the platform renew automatically ahead of expiry, instead of on a fire drill. coming soon
- The template factory. Golden Windows images are rebuilt from code on a schedule instead of hand-patched, and the build verifies itself before anything is promoted live. coming soon
- The job reporting pipeline. Job search as a real pipeline: ingest, enrich, score, and report, with a truthfulness constraint hard-coded into the model prompt. coming soon
- Self-healing monitoring. Classifies every broken host, emails the full remediation plan, and heals only what a human has approved. coming soon
- Decommission, with the gate that says no. Destroys a VM only after asserting the plan actually deletes something, so an empty plan can never pass as a successful teardown. coming soon
- AIOps morning triage. Collects overnight alerts, CI, and backup results, correlates them in code, and escalates only the hard cases to a paid model. coming soon
Code on GitHub
Each project's own page carries its real code, lifted verbatim. What you will not find is a repository link next to each one, and the honest reason is better than a broken link: the AutomationLab repository is private and stays private. It is the live configuration of a running estate, and publishing it would mean publishing the shape of the network it runs. Anything that reaches the public side crosses a fail-closed scrub gate first, which is why this site exists and the ops repo does not. These three repositories are real, and they are all of them:
parsec-lab is this site's source: the static pages you are reading, mirrored out of the private repo through that scrub gate. production-automation is de-identified professional work predating the lab, each script documented with its story, its failsafes, and its setup: a Horizon VDI monitor, a three-phase Horizon patching run with a powered-on-image failsafe, and a rolling zero-downtime deployment across an IIS farm.