Different trust levels, different jobs, intentional paths between them. Describe the principles without exposing the actual addressing plan.
03 / The collection
The lab.
An unnecessarily complicated set of networks, services, automations, and lessons learned the interesting way.
A map, minus the useful details.
This communicates the shape of the work without publishing real addressing, hostnames, management paths, exposed ports, or a convenient reconnaissance document.
What the lab says indirectly.
The point is not the number of machines. It is the ongoing practice of designing boundaries, operating services, noticing failure modes, and leaving the system easier to understand than you found it.
Updates, monitoring, backups, access, certificates, and all the quiet work that makes a service continue existing.
Diagrams and notes that make future changes less archaeological. This site can link to sanitized writeups in Notes.
Public doors.
Only list services meant to be public. Management interfaces, internal dashboards, real host inventories, and private endpoints do not need a place on this page.
Document the lesson, not the secret.
Sanitized diagrams, postmortems without identifiers, patterns you reused, and hard-earned troubleshooting notes make excellent portfolio material.