Record MB-002 / product / live trust surface
A security product with its own trust boundary, preserved here as a product record rather than swallowed by the broader studio.
What matters about this record is not just that HomeFront exists. It is that the product stayed legible: dedicated website, dedicated trust surface, on-device security posture, and a clear separation between customer-facing promise and the internal lab that helps shape it.
Summary
HomeFront could have been folded into a generic studio story, but that would have weakened trust. The stronger move was to let the product keep its own front door while the bunker preserved the broader body of work around it.
Timeline
The HomeFront record matters because the boundary decisions were product decisions, not just branding preferences.
The public security product kept its own domain, support expectations, and product-specific trust surface instead of becoming a tab inside a generic portfolio shell.
The site strategy moved toward a broader public archive, but the rule held: do not turn `gethomefront.app` into the umbrella site.
DNS protection, breach checking, security scoring, and monitoring surfaces remain the substance of the product rather than fear-based red-screen theater.
Artifacts
These are the live product surfaces retained in the archive so the record points to the product itself, not just commentary about it.
Milestones
The key thing preserved here is not just feature inventory. It is the rule that a security product needs a clean, trustworthy boundary.
It has its own live site, support expectations, and product story rather than being asked to explain the whole Tyler + Modus system.
That means the customer-facing security promise stays clear even while the bunker records everything else being built around it.
The record keeps pointing back to on-device enforcement, DNS-level protection, and real monitoring surfaces rather than vague privacy rhetoric.
Continue
MB-002 is the boundary record. It makes more sense when read between the AiHD launch thread and the MODUS continuity thread around it.
The dispatch that explains why preserving the product boundary was a trust decision, not just a branding one.
Previous record MB-001 / AiHDGo back to the launch-prep record that pushed the bunker into public seriousness.
Next record MB-003 / MODUSFollow the continuity layer behind both products and see why the archive exists at all.
Related records
HomeFront lives in the bunker as a preserved product boundary: the logs explain why the split matters, the archive keeps it in context, and the live site remains the place where product trust has to be earned directly.