The Sovereign Journal
SOVEREIGN
All entries
3 min read Governance Before Compute

Anthropic got the moonshot. Who holds the governance layer?

Anthropic just joined the ARPA-H clinical AI moonshot. That is the compute layer moving. The governance layer is a different question entirely.

Anthropic joined the ARPA-H clinical AI moonshot this week, per STAT. Closed-door health care event to follow. The compute layer is moving fast.

Nobody is asking who holds the governance layer.

That is the question I built Sovereign Shield around. Not because governance is noble or because it sounds good in a pitch. Because without it, the compute layer runs on someone else’s rules, inside someone else’s architecture, answering to someone else’s board.

The layer order matters

Sovereign Shield has three layers. Governance sits at the bottom. Infrastructure sits in the middle. Products sit on top.

Most builders start at the top and work down. They ship a product, then realize they need infrastructure, then eventually bump into the governance question when something goes wrong. A data breach. A contract dispute. A federal audit. A tribal council that asks who exactly owns what ran through this system.

We start at the bottom and build up. Not because it is slower, though it is. Because the layers that come later can only be as stable as the layer beneath them.

The governance layer is Adaptive Inclusive Leadership Theory. AILT is a framework I developed through doctoral research at Liberty University and published as a book. At its core it holds one idea: an organization’s ability to adapt is bounded by how widely it includes voices before adapting. That is Inclusive Adaptive Capacity. The people who will live with the decision need to be in the room before the decision, not after.

For sovereign AI infrastructure, that means the community holds the governance decisions before the racks arrive. Not as a checkbox. As a structural requirement.

What happens when you skip it

Anthropian-scale compute dropped into a clinical setting without a governance layer is not neutral. It imports the values embedded in the training data, the liability structures embedded in the enterprise agreement, and the roadmap priorities of whoever controls the model weights.

For a tribal health clinic or a rural FQHC, that import is invisible until it is not. The night-shift nurse follows the AI’s sepsis flag. The AI was trained on a patient population that does not look like hers. The flag is wrong. The patient is harmed. The question then becomes: who was in the room when that model was approved for deployment here?

If the answer is nobody from this community, the governance layer was absent. The compute layer was present. That gap is the problem.

AILT’s second core construct

Participatory Sensemaking holds that meaning is made collectively. Decisions made with the room hold longer than decisions made for it. This is not a soft idea. It is a durability claim.

A sovereign AI deployment that the community helped design, approved, and understands will outlast a deployment that arrived ready-made. When the model makes an error, the community knows the process that produced it. They can correct it. When the model performs well, the community understands why. They can extend it.

Without Participatory Sensemaking, every AI deployment is a black box that arrived from outside. Corrections require the vendor. Extensions require a new contract. The community is a customer, not an owner.

What sits on top of governance

The infrastructure layer is the Sovereign Prompt Shield architecture. Sovereign micro data centers. Domain-specific fine-tuned models. AES-256-GCM encryption on-device before AI processing. Raw PHI never leaves the local node. The community holds the keys. Append-only audit logs track everything.

The Sovereign Health LLM runs at 97.78 percent accuracy on 41,000+ training pairs. That number means something only because the governance layer determined what it should be trained on, who validated the outputs, and what populations it should serve. The accuracy figure is downstream of the governance decisions.

On top of infrastructure sits seventeen live products serving tribal nations, FQHCs, and sovereign and rural communities. Each product is the same architecture serving a different community. The architecture does not change. The community does.

The ARPA-H question

Anthropics’s moonshot with ARPA-H will produce powerful tools. I have no doubt. The question is not whether the compute is capable. The question is whether the governance layer exists in the communities where those tools will land.

If it does not, the pattern repeats. Sophisticated infrastructure. Absent governance. A community that holds the outputs but not the keys.

Pick up enough crumbs, you get a loaf of bread. But you have to own the oven.

Get the journal by email

One email when there is an entry. Nothing else. No pitch. Unsubscribe whenever you want.