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

Raw Permalink Blame History

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

hip	title	author	type	category	status	implementation-rust	created
0403	KV CRD	Hanzo Platform Team	Standards Track	Operator	Final	shipped	2026-05-19

HIP-0403: KV CRD

Abstract

The KV CRD is the facade Kind for KV-compatible workloads (hanzoai/kv). It delegates to the Datastore reconciler with type: valkey. Used as the cache/queue substrate by the LLM gateway, console, chat, and analytics. The CR's spec is DatastoreSpec verbatim.

Specification

Group + version

hanzo.ai/v1, plural kvs, shortname kv.

Spec fields

Same shape as Datastore (HIP-401). Implicitly type: valkey.

Example CR

apiVersion: hanzo.ai/v1
kind: KV
metadata:
  name: kv
  namespace: hanzo
spec:
  type: valkey
  image:
    repository: ghcr.io/hanzoai/kv
    tag: "9"
  replicas: 1
  storage:
    storageClassName: do-block-storage
    size: 5Gi
    retentionPolicy: Retain
  credentialsSecret: redis-credentials
  serviceAliases: [redis, valkey]

Generated K8s resources

StatefulSet, headless + ClusterIP Services, PVC.

Operator reconciler

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

Consumers: LLM gateway response cache, console queue, chat rate limiter.

Status

Implemented in hanzoai/operator v0.3.0+. CRs kv and insights-kv active in cluster.

1.3 KiB Raw Permalink Blame History