Files
papers/hanzo-sdk-ecosystem/hanzo-sdk-ecosystem.tex
zeekay 0d1d121451 papers: cover-consistency + build pass on Hanzo Tier-2/3 catalogue
Fix shared/ include paths to ../shared/ for 55 subdirectory papers so
that hanzocover.sty and lstlang.tex resolve when building from each
paper's own directory (the build pattern used by latexmk per paper).

Build fixes:
- hanzo-operative/sections/03-screen-understanding-pipeline.tex: move
  \COMMENT from after \FOR{...} onto the \STATE line so the algorithmic
  env doesn't mis-parse.
- hanzo-network-architecture (abstract + sections 04, 12, 13): escape
  unicode mu (U+03BC) as $\mu$ for pdflatex.
- ntt-transform/sections/08-benchmark-results.tex: same mu escape.

All 55 Tier-2/3 papers now build clean with latexmk -pdf.
2026-05-13 01:11:04 -07:00

74 lines
2.2 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/hanzocover}
% Packages
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{booktabs}
\usepackage{listings}
\input{../shared/lstlang}
\usepackage{xcolor}
\usepackage[numbers]{natbib}
\usepackage{tikz}
\usetikzlibrary{arrows,shapes,positioning,calc}
% Theorem environments
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{definition}[theorem]{Definition}
\newtheorem{corollary}[theorem]{Corollary}
% Code listing style
\lstset{
basicstyle=\ttfamily\small,
keywordstyle=\color{blue},
commentstyle=\color{gray},
stringstyle=\color{red},
breaklines=true,
frame=single,
numbers=left,
numberstyle=\tiny\color{gray}
}
\title{\textbf{The Hanzo SDK Ecosystem:\\Multi-Language Commerce Integration}}
\author{
Zach Kelling\\
Hanzo Industries\\
\texttt{[email protected]}
}
\date{July 2019}
\begin{document}
\hanzocoverpage
\begin{abstract}
We present the Hanzo SDK Ecosystem, a suite of client libraries enabling commerce integration across JavaScript, Python, Go, and Ruby. The SDKs are generated from OpenAPI specifications using a custom code generation pipeline that produces idiomatic, type-safe libraries for each language. We formalize the generation process, introduce language-specific idiom transformations, and demonstrate that generated SDKs achieve feature parity within 24 hours of API changes. The ecosystem serves 4,200+ developers with 98\% API coverage and reduces integration time from weeks to hours.
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-sdk-architecture}
\input{sections/03-openapi-specification}
\input{sections/04-code-generation-pipeline}
\input{sections/05-javascript-sdk}
\input{sections/06-python-sdk}
\input{sections/07-go-sdk}
\input{sections/08-ruby-sdk}
\input{sections/09-shared-utilities}
\input{sections/10-automated-pipeline}
\input{sections/11-documentation-generation}
\input{sections/12-evaluation}
\input{sections/13-related-work}
\input{sections/99-conclusion}
\end{document}