mirror of
https://github.com/hanzoai/hips.git
synced 2026-11-04 03:42:23 +00:00
zooqueenandzeekay
fdba791a43
HIP-0065 rendered as "HIP-53" on the site. YAML 1.1 reads a
leading-zero integer as octal, so `hip: 0065` parsed as 0o65 — decimal
53. 130 of the 140 HIPs are written with leading zeros, so most of the
corpus was displaying a number nobody assigned it. The numbers are
quoted now: an identifier is written 0065 and read 0065.
Every "Edit on GitHub" and "View Raw" link 404'd — all 140. They were
built as `HIPs/hip-${hip}.md`, but the files carry a slug
(hip-0065-backup-disaster-recovery-standard.md) which cannot be derived
from the number. The real filename is carried through from the loader
and used instead.
"Requires: HIP-HIP-0027" came from prefixing values that already
carried the prefix. The renderer adds it only when it is missing, and
splits a comma-separated string rather than printing it whole.
(cherry picked from commit 6f9fd22d249000aa2ab35255b2ab1fa2056c45b7)
3.2 KiB
3.2 KiB
hip, title, author, type, category, status, created, requires, references, tags
| hip | title | author | type | category | status | created | requires | references | tags | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0303 | Hanzo adopts LP-0010: Brand Sovereignty and Federation Discovery | Zach Kelling ([email protected]) | Meta | Governance | Living | 2026-05-29 | HIP-0014, HIP-0018 | LP-0010 |
|
HIP-0303: Hanzo adopts LP-0010: Brand Sovereignty and Federation Discovery
Abstract
Hanzo adopts LP-0010 verbatim. The Lux Proposal is the canonical spec for the schema, the per-org sovereignty rule, the white-label-by-fork model, the /.well-known/<appId>.json discovery endpoint (IETF RFC 8615), and the ConfigMap peer overlay. Hanzo's hanzoai/* repos carry only Hanzo brand data; HTTP federation discovery for Hanzo apps happens at /.well-known/<appId>.json per the shared spec.
This document records Hanzo-specific adoption details and the commit log; the normative text lives in LP-0010.
Hanzo-specific notes
- Canonical brand package:
@hanzo/[email protected](npm, source at~/work/hanzo/brand). Deprecated alias@hanzoai/brand404s on npm — do not use; any remaining references MUST migrate to@hanzo/brand. - Hanzo subnet branding: the Hanzo subnet runs on the Lux primary network (chainId 36963). Hanzo apps that surface chain identity (block explorers, bridges) MAY display the chain name "Hanzo Mainnet" — chain identity is network metadata, not brand identity, and is therefore exempt from LP-0010's cross-brand pollution rule. The inverse also holds: Lux's canonical explorer displaying "Hanzo subnet" or a Hanzo chain logo is network metadata, not cross-brand pollution.
- Hanzo source-tree scope:
hanzoai/*GitHub repos host Hanzo brand data only. No Lux / Zoo / Pars brand presets, k8s manifests, or federation peer URLs in source. Cross-org image references (ghcr.io/luxfi/nodepulled as an upstream OSS dep) are exempt per LP-0010 §7. - IAM white-labeling:
hanzoai/iamis white-labeled by domain at runtime (same code, brand resolved from the JWKS issuer config) rather than by fork.
Reference implementation (Hanzo)
| Repo | Commit | Action |
|---|---|---|
hanzoai/market |
29a77cb + da7008e |
Bot Hub → Hanzo Market rebrand (145 files); only Hanzo + generic presets remain |
hanzoai/exchange |
56ae5c8 |
@hanzoai/brand (404) → @hanzo/[email protected]; Zoo→Hanzo cleanup (had been forked from Zoo) |
hanzoai/iam |
9a1fd61b |
Cross-brand refs removed; added /.well-known/iam.json |
hanzoai/base-studio |
c38131a |
Added /.well-known/base.json |
@hanzo/brand |
1.3.0 |
Canonical published Hanzo brand package |