Safe Harbor is a collection of personal financial systems and insights. There isn’t some grand plan behind it, and I’m not claiming this is “the best” way to do anything. These are systems I’ve built, tested, and kept because they continue to work under real conditions—busy weeks, stress, and limited attention—not just when everything is calm. The goal is stability and clarity: fewer decisions to make, fewer ways for things to break, and less ongoing management—not optimization, not cleverness, and definitely not for show.
I’m a high school chemistry teacher, not a financial planner, and that means my time and energy are limited. These systems have to fit inside a normal schedule, not a lifestyle where managing finances is a full-time job. Because of that, they can’t rely on constant monitoring or adjustment. If something only works when everything is controlled and predictable, it won’t hold up during real life. Limited time and attention push everything toward simpler setups that keep working without needing frequent input.
The goal is simple: calm and boring.
That might not sound appealing at first, but that’s exactly the point. Systems that feel exciting usually demand attention—they need to be watched, adjusted, and sometimes fixed when something goes wrong. Once a system needs that level of involvement, it stops working reliably during busy or stressful periods. Calm systems don’t have that problem. They run in the background and keep working without pulling your attention away from other things. Over time, that reliability matters more than small improvements that only work if you keep managing them.
Underneath all of this is a straightforward idea borrowed from Epicurean thinking: the goal isn’t to maximize wealth, it’s to maximize durable comfort—having your needs met in a stable, low-stress way over time. That shifts the focus toward meeting needs reliably, reducing unnecessary stress, and avoiding setups that are fragile or volatile—things that either break easily or change unpredictably. When you follow that idea through, you keep landing in the same place: stability over squeezing out extra gains, sufficiency over excess, and peace of mind over optimization.
One of the clearest ways this shows up is in my preference for systems over willpower. If something depends on remembering what to do, making repeated decisions, or resisting urges in the moment, it will eventually fail—not because of a personal flaw, but because attention and discipline are limited resources. Good systems remove that burden by using automation, defaults, and structure so the right behavior happens without needing constant effort. Once something is set up correctly, it should keep running with minimal involvement.
Friction plays a big role in how these systems behave. Here, “friction” means how easy or difficult it is to take a particular action. Every decision has a cost in attention and effort, so the system needs to control where that cost shows up in your behavior. Good design reduces friction where consistency is important—making good choices easy—and adds friction where risk needs to be limited—making bad choices harder. The goal isn’t to eliminate friction entirely, but to place it deliberately so the system guides behavior instead of relying on constant vigilance.
What you’ll find here are those kinds of systems—low-friction, low-maintenance setups—along with the thinking behind them. Some posts focus on structure—how things are built and why they’re arranged that way—while others focus on tradeoffs and the points where a system needs to change as conditions or scale shift. The visuals are there to make those patterns easier to recognize and reuse, not just to decorate the page.
What you won’t find here are predictions, stock picks, or attempts to beat the market. I’m not interested in chasing marginal gains or building systems that require constant attention to maintain. That approach comes with an ongoing cost—time, energy, and mental overhead that has to be paid continuously—and most of the time it’s not worth paying. These systems are built to avoid that trap of constant management and complexity.
Safe Harbor is for people who want stability and clarity without constant input. It’s for people who are tired of unnecessary complexity and would rather have something that just works. When a system is doing its job—handling defaults and routine decisions for you—you shouldn’t have to think about it very much.
The posts themselves follow an old structure: the inverted pyramid. The main idea comes first, followed by supporting detail, so the reader doesn’t have to dig to find the point. That keeps things usable—easy to read and quick to apply—and reflects the same principle these systems are built on. It’s also a direct rejection of the kind of click-driven writing that hides the answer behind unnecessary buildup—a style that’s everywhere on the internet.
You can’t control the ocean, and conditions are always going to change. What you can do is build something that holds steady anyway—something that doesn’t need constant adjustment to keep working. That’s what these systems are designed to do in practice.
🦜 Cap'n Edward Shapard
Design and systems by Cap'n Edward, whith assistance from Fred Jones