title(vs-claude): 'hanzo.ai vs. claude.ai' (was 'Sovereign vs. Closed')

defense/hanzo-vs-claude.tex

@@ -1,7 +1,7 @@
 \documentclass[11pt,letterpaper]{article}
 \usepackage{hanzo-defense}
 
-\doctitle{Sovereign vs.\ Closed:\\Hanzo AI versus Centralized Cloud AI}
+\doctitle{hanzo.ai vs.\ claude.ai:\\Owned, Self-Hostable AI versus a Centralized Cloud}
 \docid{HAI-2026-011}
 \docversion{Version 1.0}
 \docdate{2026}

site/src/config/papers.ts

@@ -66,8 +66,8 @@ export const siteConfig: SiteConfig = {
     },
     {
       id: 'hanzo-vs-claude',
-      title: 'Sovereign vs. Closed',
-      subtitle: 'Hanzo AI versus Centralized Cloud AI',
+      title: 'hanzo.ai vs. claude.ai',
+      subtitle: 'Owned, self-hostable AI versus a centralized cloud chat',
       abstract: 'Owned, self-hostable AI versus a metered cloud chat — on deployment and control, not benchmark scores. Includes a measured productivity case: on a regulated build where every engineer had the same frontier model (Claude), the client\'s own audit found one engineer on Hanzo\'s agentic stack shipped more than three contractor pods combined at ~250x-900x lower cost per line — the differentiator being the owned agentic stack, not the model. Covers data residency, air-gapped operation, provenance, post-quantum security, and cost at scale.',
       pdfUrl: '/pdfs/hanzo-vs-claude.pdf',
       latexUrl: 'https://github.com/hanzoai/papers/blob/main/defense/hanzo-vs-claude.tex',