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.9 KiB

Raw Permalink Blame History

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

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

HIP-0406: DNS CRD

Abstract

The DNS CRD models DNS zone serving and management. It deploys CoreDNS as the authoritative + cluster nameserver, optionally syncs zones to Cloudflare, and reads/writes zone records from a backing database (SQL CR). The CRD encapsulates a complete DNS stack rather than individual records.

Specification

Group + version

hanzo.ai/v1, plural dns, shortname hdns.

Spec fields

Field	Type	Description
`zones`	[]DNSZoneSpec	name + optional Cloudflare zone ID
`coredns`	CoreDNSSpec	image, replicas, api/dns ports, resources
`cloudflare`	CloudflareSyncSpec	enabled, credentials ref
`database`	DatabaseSpec	enabled, credentials ref, syncInterval
`oidc`	OIDCSpec	enabled, issuer, audience
`ingress`	IngressSpec	management API ingress

Example CR

apiVersion: hanzo.ai/v1
kind: DNS
metadata:
  name: dns
  namespace: hanzo
spec:
  zones:
    - name: hanzo.ai
    - name: hanzo.id
  coredns:
    image: ghcr.io/hanzoai/dns:0.10.0
    replicas: 2
    apiPort: 8053
    dnsPort: 53
  cloudflare:
    enabled: true
    credentialsRef:
      name: cloudflare-credentials
  database:
    enabled: true
    credentialsRef:
      name: dns-db
    syncInterval: 30s
  oidc:
    enabled: true
    issuer: https://hanzo.id
    audience: app-dns

Generated K8s resources

Deployment (CoreDNS, multi-replica)
ClusterIP Service (port 53 UDP/TCP + management API)
Optional Ingress for the management API
Optional CronJob for Cloudflare reconciliation

Operator reconciler

~/work/hanzo/operator/src/controllers/dns.rs.

HIP-0049 (DNS Service Standard) — overarching design doc.

Status

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

1.9 KiB Raw Permalink Blame History