Dispatch / Apr 19, 2026 / HomeFront / Boundary

HomeFront stayed separate on purpose.

The public site could have collapsed into one umbrella surface. That would have made the narrative cleaner and the trust worse.

HomeFront already behaved like a real product property with support, privacy, terms, and product-specific trust expectations. Preserving that boundary was part of preserving the product’s integrity.

Good architecture sometimes looks like restraint. HomeFront already had the structure of a dedicated property: product docs, support expectations, privacy pages, terms, and a user-facing identity tied to the product itself. That is not something you casually blur just because the wider studio story starts getting interesting.

Keeping HomeFront separate protected two things at once. First, it preserved customer trust. Second, it gave the bunker permission to become something broader and more experimental without asking the security product to carry that meaning on its back.

That decision made the rest of the public site possible. The bunker could become the archive. HomeFront could remain the product. Those are different jobs, and the work got cleaner once the boundary was accepted instead of fought.

Continue

Keep moving through the archive.

This dispatch explains the HomeFront boundary rule. The next useful move is into the HomeFront record itself or into the MODUS dispatches that made the bunker possible around it.

Continue

One product, one trust surface.

This dispatch matters because it explains why the bunker can grow without weakening the live product that already has to stand on its own.