This is the first post on the North Star blog, so it’s worth saying out loud what we’re doing here and why.
Athena Systems North Star is an appraisal-compliance platform. Two of us built it: Justin Moriarty, an active appraiser licensed in both Washington and Oregon with decades of Pacific Northwest field experience, and Darin Molnar, PhD, the technical co-founder who built the rule engine, the cryptographic audit chain, and the platform application. We’re a small bootstrap. We don’t have venture capital. We don’t have a sales team. What we have is a product that does one thing well: it evaluates an appraisal work file against a published library of rules, finds where the report falls short, and seals the result into a cryptographic record that anyone — appraiser, lender, AMC, regulator, attorney — can verify years later.
This blog exists for three audiences.
The first is the working appraiser who’s looking at our product and trying to figure out whether it’s worth their time. We’ll write about specific rules in the catalog, why they trigger, what evidence satisfies them, and what kickback they prevent. The 435 SME-reviewed rules in the library cover federal mortgage-finance regulation, state licensing and practice standards for WA and OR, USPAP, property-side overlays like Critical Areas and EFU zoning, hazard zones, and seller-disclosure obligations. Each one has a story. We’ll tell them.
The second is the technical reader — engineers, security researchers, auditors, anyone who wants to understand how the cryptographic audit chain actually works. The Decision Record is the part of the product that has to be honest with you. We’ll write about the design choices behind it: why we use ECDSA P-256 instead of Ed25519 (AWS KMS doesn’t support Ed25519), why the verifier compiles to WebAssembly so it runs in your browser tab, why the seal records what was evaluated and when but doesn’t claim the underlying file is correct.
The third audience is us. Writing publicly is how we think out loud about the product we’re building, the industry we’re building it for, and the trade-offs we’re making along the way. If you’re curious about what it looks like to bootstrap a regulated-industry SaaS from a two-person team, this blog will tell that story too.
The cadence will be roughly weekly, alternating between Justin’s practice-focused posts and Darin’s technical ones. We’d rather post nothing than post for the sake of posting — so when an article lands here, it’ll be because we had something genuinely worth saying.
Welcome. We’re glad you’re reading.