Decoupled by design, so no single failure takes the system

The Five-Entity Architecture

Assets, regulatory exposure, technology, insurance, and legal advocacy are separated into five entities with strict zero-conflict boundaries.

Revised 8/3/2026

Why one company cannot win

A single company doing all of this is a single target: one regulator, one lawsuit, one carrier relationship, one acquisition offer away from the whole thing ending. Decoupling is not corporate theater — it is survivability.

The five pillars

RRCA LLCFounding sponsor and primary contractor node. The ground-level proof of concept and field execution engine. Revenue: contracting margins, network override fees, onboarding, safety certification.

ClaimStore, Inc.Public benefit clearinghouse. The neutral central clearinghouse and escrow framework for loss verification. Revenue: verification fees, per-claim transaction fees, bulk clearinghouse fees.

Market Applications, LLC (dba JoeBack)Core technology provider. Develops and hosts the engine, the niche trade portals, and the multi-tenant infrastructure. Revenue: SaaS access tiers, API licensing, enterprise deployments.

SelfInsurity, Inc. (dba RoofLac)InsurTech. Supplemental roof assurance for property owners; pay-per-project GL and Workers' Comp for contractors. Revenue: premiums and underwriting income.

ClaimBuddy / BuddyClaimLegalTech and advocacy. Standardized terms of service, service level agreements, and property-owner contingency rights. Revenue: document generation, certified mailing, escrow coordination.

The legal firewall

Each entity holds its own contracts, its own liabilities, and its own books. The clearinghouse must stay neutral to be credible; the contractor node must stay independent to be sovereign; the technology provider must stay a vendor rather than an owner of anyone's data. The boundaries are the product.