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

Raw Permalink Blame History

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

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

HIP-0404: DocDB CRD

Abstract

The DocDB CRD is the facade Kind for DocumentDB workloads (hanzoai/docdb). DocumentDB exposes the DocumentDB wire protocol over SQL, giving us DocumentDB-compatible APIs without a DocumentDB server. The reconciler delegates to the Datastore controller with type: docdb.

Specification

Group + version

hanzo.ai/v1, plural docdbs, shortname docdb.

Spec fields

Same shape as Datastore (HIP-401). Implicitly type: docdb. Typical deployment runs DocumentDB as the wire-protocol front-end with a SQL CR as the storage backend.

Example CR

apiVersion: hanzo.ai/v1
kind: DocDB
metadata:
  name: docdb
  namespace: hanzo
spec:
  type: docdb
  image:
    repository: ghcr.io/hanzoai/docdb
    tag: v1
  replicas: 1
  storage:
    storageClassName: do-block-storage
    size: 1Gi
  env:
    - name: FERRETDB_POSTGRESQL_URL
      value: postgres://hanzo@localhost:5432/docdb
  credentialsSecret: docdb-credentials

Generated K8s resources

StatefulSet, headless + ClusterIP Services, PVC (small — DocumentDB itself is stateless on its own backing SQL).

Operator reconciler

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

No standalone DocDB CR currently runs in do-sfo3-hanzo-k8s (DocumentDB is invoked via library by services that need a DocumentDB-compatible layer).

Status

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

1.6 KiB Raw Permalink Blame History