papers/hanzo.yml

# papers.hanzo.ai. The Dockerfile IS the gate: it runs `npm ci && npm run build`
# on the Next.js source and a broken site cannot produce an image. No test:
# block duplicating it, and no LaTeX gate here — the paper set is compiled by
# .hanzo/workflows/ci.yml (`make -k all` under texlive-full), which is the right
# home for a 219-paper, texlive-sized job.
#
# papers.hanzo.ai serves a static export: the route in hanzoai/universe
# (static-sites.yaml, papers-static) reads s3://hanzo-sites/hanzo/papers, and
# site: below is what writes it, from main. The image is the build gate.
#
# No version: either. imgver reads the image's own context before the repo root,
# so site/package.json is where this version lives and a key here could only
# disagree with it. The series runs from there — 1.0.0, then a patch per build,
# each one derived from what is already published rather than typed.
images:
  - name: papers
    context: .
    dockerfile: site/Dockerfile
    repo: ghcr.io/hanzoai/papers
    # Both architectures the fleet runs, each built natively in-cluster by the
    # build door — no docker, and nothing emulated. That needs `mode: delegate`,
    # which needs a context at the repository root, which is why the context is
    # `.` and .dockerignore carries the weight instead.
    platforms: [linux/amd64, linux/arm64]
site:
  slug: papers
  dir: site/out
  build: cd site && npm ci && npm run build
  on: [main]