Files
zeekay 5a1289e458 Credit the organisation on every published surface
Leadership and team cards, board and founding prose, an AI persona modelled on a
named individual, contributor and partner entries, and personal correspondence
addresses all named one person. The organisation carries them now.

Other people keep their names. Where a card, a board list or a founding line
named someone else alongside, they stay exactly as they were; only the one entry
was removed, and prose that listed two names now reads with one.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so the IAM username defect the notes describe still reads as written.
The zoo/yapp MIT notice names the foundation that publishes it.
2026-09-01 08:53:13 -07:00

51 lines
1.7 KiB
TeX

\documentclass[11pt,twocolumn]{article}
\usepackage{../shared/hanzocover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{cite}
\usepackage{algorithm}
\usepackage{algorithmic}
\usepackage{listings}
\input{../shared/lstlang}
\usepackage{xcolor}
\lstset{
basicstyle=\ttfamily\small,
keywordstyle=\color{blue},
commentstyle=\color{gray},
stringstyle=\color{red},
breaklines=true,
frame=single
}
\title{Crowdstart: A Cloud-Native E-Commerce Platform}
\author{Hanzo AI Research\\
Hanzo Industries\\
\texttt{[email protected]}}
\date{March 2014}
\begin{document}
\hanzocoverpage
\begin{abstract}
We present Crowdstart, a cloud-native e-commerce platform designed from first principles for horizontal scalability and operational simplicity. Built on Google App Engine with Go as the primary implementation language, Crowdstart demonstrates that commerce infrastructure can achieve both developer ergonomics and production reliability without the operational burden of traditional deployments. Our architecture leverages eventual consistency, idempotent operations, and stateless request handling to enable automatic scaling from zero to millions of transactions. We describe the system design, evaluate performance characteristics, and discuss lessons learned from production deployments serving over 500 merchants.
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-background-and-motivation}
\input{sections/03-system-design}
\input{sections/04-implementation}
\input{sections/05-evaluation}
\input{sections/06-lessons-learned}
\input{sections/07-related-work}
\input{sections/99-conclusion}
\end{document}