mirror of https://github.com/hanzoai/papers.git synced 2026-10-22 17:20:17 +00:00

Files

T

zooqueenandHanzo Dev 44ec401a31 ci: a gate that can fail, and the 24 papers it catches

`make -k all` returned 0 over any number of broken papers, so CI was green the
whole time it existed. Four things had to be true for that:

  - every recipe line ended in `|| true` and the rule printed "FAIL" instead of
    exiting, so make never saw a failure;
  - nonstopmode emits a PDF for almost any input, so "the PDF exists" is not
    the same question as "the paper compiled" — zen-nano_whitepaper produced
    one through 23 LaTeX errors;
  - pdfs/ was tracked, so a checkout handed the "check every paper came out"
    step 100 of the PDFs it was about to look for;
  - discovery was three wildcards, so 69 of the repo's 219 papers were
    compiled by nothing at all, defense/ by a second copy of the same
    swallowing loop written inline in ci.yml.

The rule is now one latexmk per paper and its exit status is the gate:
-halt-on-error (no PDF from a broken paper), -bibtex (a declared bibliography
must resolve rather than being skipped when the .bib is absent), -Werror (an
undefined citation is a defect, not a log note), -cd (each paper compiles from
its own directory, so zen/ finds references.bib and defense/ finds
hanzo-defense.sty). .DELETE_ON_ERROR so a failed run leaves nothing behind,
and pdfs/ is untracked because it is output.

Run against the tree it was guarding, the honest gate fails 24 papers:

  6  \begin{itemize} with its backslash-b eaten, leaving a bare `egin{itemize}`
     and no \end — artist, designer-instruct, eco, nano, next, omni
  3  the same list with the opener deleted outright, so five \item stood in no
     environment — artist-edit, designer-thinking, scribe
  4  \and in a cover page's raw \@author: it expands to \end{tabular} and closed
     a tabular nothing had opened, and \thanks left hyperref pointing at a
     footnote anchor that was never created; plus five stray \end{table} at the
     end of those documents — director, foley, musician, video
  9  \color{gray} under \usepackage{color}, which defines eight names and not
     that one — xcolor is the superset the working papers already load
  6  \bibliography{references} naming a database that was never written, so
     every citation rendered [?] — zen/references.bib now holds all 27 works
  9  \bibliographystyle+\bibliography in papers with no \cite at all — dropped
  3  characters pdflatex has no glyph for: CO₂ -> CO\textsubscript{2},
     ↔ -> $\leftrightarrow$, Persian letters -> their code points, the
     SentencePiece marker -> \textvisiblespace
  1  \IF{...} \COMMENT{...}: algorithmic's \IF opens a list and the comment
     landed in it before any \item; the comment slot is \IF[...]{...}
  1  \ref{eq:anchor_update} to an equation the paper never writes

All 219 papers now compile from a clean tree: `make -k all` exits 0.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-28 17:35:30 -07:00

5.8 KiB

Raw Blame History

Hanzo AI Research Papers

Technical papers covering Hanzo AI compute infrastructure, agent frameworks, ML inference, platform services, and defense applications. Includes the Zen model family co-developed with Zoo Labs Foundation.

About

Hanzo AI is an American-owned, Techstars-backed ('17) applied AI lab, founded 2014, building the Zen frontier model family alongside a vertically integrated, post-quantum AI and cryptography stack. The work spans frontier models, an agentic runtime, edge inference, and production post-quantum cryptography — engineered to run sovereign and disconnected in defense, regulated, and air-gapped environments rather than on centralized cloud. The platform these papers document is generally available at hanzo.ai.

2026 Highlights

Each claim below is developed in the catalogued papers (INDEX.md):

Defense & Reindustrialization suite (16 papers + one-pager). Positioned for the American industrial base — sovereign AI, robotics, post-quantum, and low-latency on-chain coordination for factories, vehicles, drones, ships, and contested-edge systems. Strategy & case studies: sovereign-vs-closed AI (hanzo-vs-claude), the ~90% cloud-cost migration on real numbers (hanzo-cloud-economics), agentic engineering at regulated scale (hanzo-agentic-prowess), FHE-native confidential computing (hanzo-fhe-native), automated security auditing (hanzo-security), and audit-ready compliance (hanzo-compliance). Capability depth: autonomous agentic AI (hanzo-agentic-ai), DDIL/tactical assured networking (hanzo-assured-networking), FHE-mediated cross-domain MLS (hanzo-cross-domain), edge AI/ML (hanzo-edge-ai-ml), counter-exploitation (hanzo-countermeasures), full-spectrum cyber (hanzo-full-spectrum-cyber), quantum sensing/QKD (hanzo-quantum-sensing-qkd), verification & validation (hanzo-test-evaluation), and the ZAP protocol (hanzo-zap-protocol). Start with the one-pager (defense/hanzo-overview.pdf); the full suite is published at papers.hanzo.ai.
Engine / AI infrastructure (6 papers, measured on-device). A native Rust train-and-serve engine benchmarked on real silicon: ROCm decode parity with llama.cpp at 97% of the memory-bandwidth wall (hanzo-rocm-inference), measured AMD/NVIDIA/Apple edge inference (hanzo-cross-backend-inference), native training inside the inference stack (hanzo-native-training), continuously-learning private AI (hanzo-continuous-learning-privacy), serving economics (hanzo-platform-infra-desktop), and the unifying thesis (hanzo-native-stack-thesis). Unusually honest — they name their own stubs and reverted kernels and claim no win over NVIDIA.
Unified sovereign-tenant cloud (measured). The whole multi-tenant cloud as one Go binary — 56 in-process subsystems over shared-nothing storage, each tenant its own post-quantum-encrypted SQLite file. Measured on the production open path: ≈0.25 MB RAM per actively-served tenant, near-zero idle — memory scales with concurrency, not registrations, so one billion registered tenants at 1% peak concurrency fits ≈20 commodity 128 GB nodes (hanzo-unified-tenant-cloud; architecture companion cloud-unified-binary).
Production post-quantum cryptography. All three NIST PQC standards — FIPS 203 (ML-KEM), 204 (ML-DSA), 205 (SLH-DSA) — integrated into a live consensus system with hybrid classical/post-quantum security (hanzo-full-spectrum-cyber).
Formal verification. 50 machine-checked Lean 4 proofs, 18 cryptographic security reductions (incl. ML-DSA EU-CMA, ML-KEM IND-CCA2), and NIST Known-Answer-Test validation across FIPS 203/204/205 (hanzo-formal-verification).
ZAP (Zero-copy Application Protocol). 2.2 ns parse latency, 11.5M transactions/s, 91% memory and 96% energy reduction vs JSON-RPC; native post-quantum transport (ML-KEM-768 + ML-DSA-65) and W3C DID identity (hanzo-zap-protocol).
Agentic runtime. 83 specialized agents and 15 orchestrators executing 200–300 sequential tool calls, fully offline on embedded ARM with quantized Zen models (hanzo-agentic-ai, hanzo-edge-ai-ml).
Zen frontier models. An 18-model family (0.8B–1T+ parameters), co-developed with Zoo Labs Foundation, with owned weights and full provenance.

Structure

Each paper lives in its own subdirectory:

papers/
├── shared/             # cover styles, lstlang.tex, paperkit
│   ├── hanzocover.sty
│   └── lstlang.tex
├── <paper-slug>/
│   ├── <paper-slug>.tex          # main file (\input's sections)
│   ├── <paper-slug>.pdf          # compiled output
│   └── sections/                 # modular sections
│       ├── 01-intro.tex
│       ├── 02-architecture.tex
│       ├── 03-protocol.tex
│       ├── ...
│       └── 99-bibliography.tex
└── INDEX.md                      # auto-generated catalogue

Building

cd <paper-slug>
TEXINPUTS=".:..:" latexmk -pdf <paper-slug>.tex

Or build all — every paper, and a nonzero status naming any that did not compile:

make -k all

Index

See INDEX.md for full catalogue of papers.

Conventions

One paper, one directory. No top-level .tex files.
Modular sections. Main .tex \input's sections/NN-name.tex files for easy editing.
Shared cover. All papers use \usepackage{shared/hanzocover} and \hanzocoverpage.
Shared lstlang. All papers use \input{shared/lstlang} after \usepackage{listings}.
No AI slop. Technical, dense, citation-supported.
One paper per concept. Updates over time via versioning, not duplication.

5.8 KiB Raw Blame History Unescape Escape