Welcome
Context
This is a personal lab.
It exists to document systems I run, experiments I try, and ideas that survive contact with reality. Most things here start as curiosity, turn into breakage, and sometimes get rebuilt into something stable enough to write down.
Goal
- document real infrastructure work, experiments, and design choices
- keep notes grounded in systems that can be inspected or verified later
- preserve thinking in motion instead of pretending everything is already complete
Environment
- personal infrastructure lab repository
- notes covering incidents, design work, experiments, and setup runbooks
- public-facing markdown intended to remain readable outside Obsidian
The Final State
This repository is not a finished artifact. It is a record of thinking in motion.
If something feels incomplete, it probably is. If something sounds confident, it should still be checked against the assumptions and the system state that produced it.
Verification
The verification model for this repository is note-level rather than homepage-level:
- individual notes should carry their own commands, evidence, or architectural proof
- the repository should remain readable as plain markdown without vault-specific dependencies
Failure Modes Worth Caring About
- turning the repo back into a generic note dump instead of an infrastructure lab
- publishing notes without evidence, validation steps, or explicit uncertainty
- reintroducing Obsidian-only structure into the public-facing content
References
- Start with the incident, lab, or setup notes relevant to the system you care about.