Operations

Armory Operations

The public Armory is maintained as a registry pipeline: GitHub is the reviewed source of truth, GHCR is the signed OCI distribution plane, and Cloudflare Pages serves the human catalog plus static API.

Production surfaces

• Catalog: https://armory.styrene.io
• Catalog API: https://armory.styrene.io/api/index.json
• OCI namespace: ghcr.io/styrene-lab/omegon-armory
• Source: github.com/styrene-lab/omegon-armory

Maintenance model

Operators edit manifests and package source files. The site, catalog API, OCI index, and static pages are generated from those inputs. Generated JSON and build output are artifacts, not hand-maintained source of truth.

Validation

node --test tests/armory-entry-suite.mjs
cd site && npm run build

Deployment

The site workflow publishes site/dist to Cloudflare Pages. The OCI workflow builds artifacts, pushes them with ORAS, signs them with cosign, then smokes the published index and representative package manifests.

Full runbook

The repository runbook is maintained at docs/armory-operations.md and this page mirrors the operator-facing summary. Once published from main, the source markdown is also available from the Armory GitHub repository.