T

hanzo-dev 215c9c9fea Pin the chart the publisher stands behind; drop the second deploy path

0.1.0 is the version the chart workflow's own comment names as never having
matched its source, so every Application claimed a chart nobody could
reproduce. 0.1.11 is what lux pins and what the registry actually holds.

ci.yml applied manifests with kubectl on every push, beside an ApplicationSet
that reconciles the same namespaces. Two delivery paths let the cluster
disagree with git while both report success; CD is the one that stays.

Claude-Session: https://claude.ai/code/session_01WAriF9qmzQJnBHfumZMxnd

2026-09-03 13:23:44 -07:00

.github

Name Zen in the hero card's font stack

2026-08-28 11:44:08 -07:00

.hanzo/workflows

Pin the chart the publisher stands behind; drop the second deploy path

2026-09-03 13:23:44 -07:00

architecture

docs(arch): desktop stack decomposition + brand-variant build flow

2026-05-04 11:28:31 -07:00

configs/genesis

chore: sync working tree

2026-07-26 10:16:32 -07:00

deploy

Pin the chart the publisher stands behind; drop the second deploy path

2026-09-03 13:23:44 -07:00

e2e

rpc: /ext/ -> /v1/ on our own hosts

2026-08-03 21:02:21 -07:00

infra/k8s

feat(iam): Zoo's own app graph — 5 clients, one issuer, proven end to end

2026-07-26 19:02:15 -07:00

k8s

zood-mv: GOMEMLIMIT — an OOM here can mint a divergent certified chain

2026-08-06 09:58:44 -07:00

manifests

safes: 2026-07-28 on-chain re-verification + honest MPC/KMS state (zoo-treasury-v1 is degree-0)

2026-07-28 09:35:36 -07:00

scripts/ci

fix(zoo): pass luxd flags to zoo-chain so validators stay up

2026-06-23 19:21:58 +00:00

.gitignore

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

.npmrc

Route npm through our own registry

2026-09-03 11:04:58 -07:00

AGENTS.md

chore: symlink AGENTS.md and CLAUDE.md to LLM.md

2026-04-01 14:10:32 -07:00

chain.yaml

rpc: /ext/ -> /v1/ on our own hosts

2026-08-03 21:02:21 -07:00

CLAUDE.md

chore: symlink AGENTS.md and CLAUDE.md to LLM.md

2026-04-01 14:10:32 -07:00

compose.yml

rpc: /ext/ -> /v1/ on our own hosts

2026-08-03 21:02:21 -07:00

GEMINI.md

chore: symlink AGENTS.md + GEMINI.md + CLAUDE.md -> LLM.md

2026-09-02 01:53:57 -07:00

LICENSE

chore: add Apache-2.0 LICENSE

2026-02-14 05:27:03 -08:00

LLM.md

rpc: /ext/ -> /v1/ on our own hosts

2026-08-03 21:02:21 -07:00

Makefile

feat(iam): Zoo's own app graph — 5 clients, one issuer, proven end to end

2026-07-26 19:02:15 -07:00

package-lock.json

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

package.json

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

playwright.config.ts

rpc: /ext/ -> /v1/ on our own hosts

2026-08-03 21:02:21 -07:00

README.md

retire: name the canonical universe at this tip

2026-08-20 17:33:59 -07:00

tsconfig.json

chore: sync local changes

2026-03-26 22:45:36 -07:00

README.md

Zoo Universe — retired

Read-only from here. Canonical: https://git.hanzo.ai/zoo/universe

This tip is an ancestor of canonical main, so no commit reachable from this branch is unique to it — the canonical repo is a strict superset. Nothing was lost by stopping here.

Two universes for one org is a split brain: a push lands somewhere real, reports success, and never reaches a cluster, because CD reconciles the other one (deploy/applicationset.yaml names the canonical URL). One repo per org means that failure cannot happen.