Preemptive Compliance

Compliance as a filter, not a tax

The pattern treats regulatory cooperation not as reactive overhead absorbed only when a court compels it, but as a proactive product feature built in from the start. Describing his bank Erebor, Palmer Luckey frames the posture directly: "rather than working with the intelligence community only under court order... we're preemptively going out there and saying, no, we're going to work with them from the very beginning."¹ He positions it explicitly as "the opposite of HSBC," the bank he characterizes as laundering cartel money while "desperately trying to avoid any government intervention that would make that clear to the public markets."

The self-sorting mechanism

The strategic claim Luckey makes is that preemptive compliance sorts the customer base by design. He describes three consequences. People who intend to commit fraud avoid a bank hard-wired to law enforcement and go elsewhere, which he treats as a benefit because it pushes bad actors onto competitors. People who do not want fraud are, in his words, "thrilled" to be on a platform where it is structurally rare. And if fraud does occur against a customer's will, they know they have "a willing partner that is willing to work with the government rather than hide these things."¹

In this account compliance is the mechanism that constructs the customer base rather than a cost imposed on it. The slow, expensive work of screening, audit trails, and law-enforcement cooperation functions as a barrier to entry, and Luckey's argument is that the institution willing to do it deliberately captures the legitimate demand that has nowhere clean to go. It is a way of weaponizing adverse selection: where most platforms fear that hostile actors will exploit them, Luckey's framing turns the bad actors' avoidance into a cleaning function.

How the pattern relates to trust-based advantage

Luckey's version rests on the trustworthiness of the institution being the product itself, with verifiable cooperation as the way that trust is signaled. The structure resembles other atoms-and-relationships moats more than a software feature. Like physical retail as trust layer, the defensible asset is something a competitor cannot cheaply assert into existence, and it stands apart from no moat in software precisely because the barrier is institutional and relational rather than a replicable product feature. The alignment Luckey describes with the "Department of War and intelligence community" is abstract until it manifests as concrete cooperation to suppress fraud, which is what makes the compliance posture the operational engine of the broader strategy rather than a marketing stance.

Tensions Luckey's account leaves open

The same feature that repels fraudsters concentrates law-enforcement visibility into customers' finances. A bank wired to the intelligence community "from the very beginning" is, by construction, a powerful surveillance node, attractive to the target customer and alarming to a privacy-minded one, and the source does not resolve that trade-off so much as accept it. A second unresolved boundary is where cooperation stops. Luckey says Erebor will refuse "spurious foreign rulings" while preemptively assisting US authorities, but the line between legitimate cooperation and over-cooperation is asserted rather than specified.¹ The pattern's strength, that the barrier is the feature, is also the source of its cost: the more thoroughly compliance sorts customers in, the more it centralizes visibility over them.