mirror of https://github.com/hanzoai/hips.git synced 2026-11-03 00:32:50 +00:00

Files

T

zeekayandHanzo Dev 7a9dcac628 What each runtime implements of the Hanzo corpus

An audit read the code and found the proposal that specifies it. Go reaches
all 122 capability proposals and 64 of the 121 other Standards Track ones;
Rust has 35, mostly the operator and the CLI; C++ has three, because the
complete original C++ in the estate is a ZAP handler, a bot nothing specifies,
and authored kernels inside forked CUDA and Metal crates.

    | | shipped | partial | none | not assessed |
    | Go   | 146 | 33 | 1 |  80 |
    | C++  |   1 |  2 | 0 | 257 |
    | Rust |  10 | 25 | 1 | 224 |

The large "not assessed" columns are the point rather than a gap. The model and
training specs are Python, the frontend and design-system proposals are
TypeScript, and recording `none` against those would read as a search that
came up empty when the honest statement is that the runtime was never the
question. Governance, Meta and Process are not graded at all.

Six proposals are Final with nothing found in Go and are left unwritten rather
than demoted: 0065, 0089, 0098, 0103, 0521 and 0902. HIP-0521 answers itself,
its own section reading "Not yet implemented". Three of the others name a
canonical Go file in consensus/protocol/auth that nobody wrote, in a package
where the four neighbouring proposals' files all exist with tests beside them.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-05 19:18:13 -07:00

1.8 KiB

Raw Permalink Blame History

hip, title, author, type, category, status, implementation-rust, created

hip	title	author	type	category	status	implementation-rust	created
0408	IAM CRD	Hanzo Platform Team	Standards Track	Operator	Final	partial	2026-05-19

HIP-0408: IAM CRD

Abstract

The IAM CRD is the facade Kind for the Hanzo identity service (hanzoai/iam). It is structurally a Service and delegates to the Service reconciler. The Kind exists so kubectl get iam yields the canonical identity workload directly rather than searching among generic services. See HIP-026 for the IAM design.

Specification

Group + version

hanzo.ai/v1, plural iams, shortname iam.

Spec fields

Same shape as Service (HIP-400). Conventionally:

image.repository: ghcr.io/hanzoai/iam
ports: containerPort: 8000
mounts the registry-signing-key secret for registry token issuance
consumes iam-secrets via envFrom

Example CR

apiVersion: hanzo.ai/v1
kind: IAM
metadata:
  name: iam
  namespace: hanzo
spec:
  image:
    repository: ghcr.io/hanzoai/iam
    tag: 2.381.0
  replicas: 2
  ports:
    - name: http
      containerPort: 8000
      servicePort: 80
  envFrom:
    - secretRef:
        name: iam-secrets
  readinessProbe:
    path: /api/health
    port: 8000

Generated K8s resources

Deployment, Service, optional Ingress (in practice Ingress is managed separately because IAM serves multi-tenant hostnames — hanzo.id, lux.id, zoo.id, pars.id, id.hanzo.ai, id.lux.network, id.pars.network, id.ad.nexus).

Operator reconciler

~/work/hanzo/operator/src/controllers/service.rs (via IAM facade in crd.rs).

HIP-0026 (IAM standard)
Consumers: every authenticated service in the cluster.

Status

Implemented in hanzoai/operator v0.3.0+. CR iam active in cluster.

1.8 KiB Raw Permalink Blame History