mirror of
https://github.com/hanzoai/hips.git
synced 2026-10-30 15:04:16 +00:00
zeekayandHanzo Dev
7a9dcac628
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]>
74 KiB
74 KiB
| 1 | go:0004 | shipped | the gateway is pure Go and it is not in the repository the HIP names: ai (module github.com/hanzoai/ai) serves /v1/chat/completions with model routing at ai/router/routing_policy.go and per-request metering. hanzoai/llm, which the HIP gives as its Repository, is not on disk |
|---|---|---|---|
| 2 | go:0005 | partial | hsm/signer_mldsa.go:21 MLDSASigner over luxfi/crypto/mldsa and kms/sdk/go/cek.go:82 WrapCEKForMember (hybrid ML-KEM-768 + X25519 HPKE) are real. The at-rest opener cloud actually links, hanzoai/cek v0.2.3, is classical, and the AI-specific layers the HIP adds — encrypted weights, encrypted inference — have no Go |
| 3 | go:0009 | partial | agent/agent.go serves POST /v1/agent as a single tool-calling round with per-org SQLite history. The multi-agent network routing and shared-state plane the HIP specifies are in the Python and NPM packages, not Go |
| 4 | go:0026 | partial | cloud/plugin/iam/main.go:21 serves 159 operations over /v1/iam plus the OIDC discovery roots, so the standard's core is real; six operations in the HIP-0026 § operation table are not among them — /v1/iam/get-user, add-user, update-user, delete-user, get-account, get-app-login. The service serves REST collections (/v1/iam/users, /v1/iam/applications, /v1/iam/keys) instead of the verb-per-path spelling the table carries |
| 5 | go:0027 | partial | the Go server exists but not where the HIP puts it. ~/work/lux/kms (module github.com/luxfi/kms) holds it; kms/DEPRECATED.md retires the repository HIP-0027 names as its Repository |
| 6 | go:0033 | partial | cloud/apps/registry/registry.go:171 serves /v1/registry as an OCI distribution surface. The hanzoai/registry repository the HIP names contains no code at all |
| 7 | go:0036 | partial | the Go halves of the pipeline exist — cd is an ArgoCD fork that reconciles, and ci/declared.go:25 reads the pinned image out of a values file — but hanzoai/build, the repository this HIP designates, does not exist, and the workflow standard itself is YAML |
| 8 | go:0049 | shipped | dns is a CoreDNS fork carrying the Hanzo plugins in tree: plugin/hanzodns/{api.go,api_sync.go,cloudflare.go,kms.go,oidc.go} for API-driven records, plus plugin/geoip |
| 9 | go:0060 | shipped | cloud/plugin/functions/main.go:20 is the app binary and manifest/apps.go:217 the fleet row for /v1/functions; 11 operations resolve. The three /v1/functions/{my-function,embed-document,...} paths that do not are the HIP's worked examples of a caller-named function, not routes it fixes |
| 10 | go:0061 | shipped | cloud/plugin/notify/main.go:20 is the app binary and manifest/apps.go:409 the fleet row that routes /v1/notify; its own router projection cloud/plugin/notify/openapi.json publishes 4 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-0061 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 11 | go:0063 | shipped | cloud/plugin/flags/main.go:20 is the app binary and manifest/apps.go:67 the fleet row that routes /v1/flags; its own router projection cloud/plugin/flags/openapi.json publishes 8 operations, and every route HIP-0063 names resolves in the composed fleet document cloud/private.yaml |
| 12 | go:0065 | none | no Go backup or disaster-recovery service exists. hanzoai/replicate covers SQLite WAL only and there is no hanzo/backup repository, so the unified plane over SQL, KV, datastore, S3 and checkpoints has no implementation |
| 13 | go:0068 | shipped | ingress (module github.com/hanzoai/ingress) is the maintained Traefik v3 fork with the Kubernetes provider intact — 699 Go files, and no config-generation sidecar |
| 14 | go:0074 | shipped | cloud/plugin/sbom/main.go:20 serves 3 operations over /v1/sbom. The one path in the HIP that does not resolve is /v1/sbom/ghcr.io/hanzoai/iam, a worked example of an image reference rather than a fixed route |
| 15 | go:0085 | shipped | ~/work/lux/consensus/protocol/auth/account_id.go with account_id_test.go — the 48-byte ML-DSA-65 AccountID derivation the HIP pins |
| 16 | go:0086 | shipped | ~/work/lux/consensus/protocol/auth/tx_envelope.go with tx_envelope_test.go — the typed PQ transaction envelope |
| 17 | go:0087 | shipped | ~/work/lux/consensus/protocol/auth/permit.go with permit_test.go — the EIP-2612 replacement |
| 18 | go:0088 | shipped | all three files the HIP pins exist: ~/work/lux/node/network/kem/scheme.go (ML-KEM session primitives), ~/work/lux/node/network/peer/handshake.go (the state machine) and ~/work/lux/consensus/config/pq_mode.go (the canonical wire bytes) |
| 19 | go:0089 | none | status Final, but ~/work/lux/consensus/protocol/auth/beacon.go does not exist. The package holds account_id, tx_envelope, permit, precompile, scheme_ids, hash and contract_profile, and nothing that generates or verifies a randomness beacon |
| 20 | go:0098 | none | status Final, but ~/work/lux/consensus/protocol/auth/governance.go does not exist, in the same package that holds every other auth-surface file those HIPs name |
| 21 | go:0103 | none | status Final, but ~/work/lux/consensus/protocol/auth/bridge_profile.go — the canonical reference the HIP names three times — is absent |
| 22 | go:0104 | partial | ~/work/lux/consensus/protocol/auth/precompile.go:50 pins PrecompileAddrPQVerifyMLDSA65 = 0x301 and declares the four function-pointer types. The EVM wiring the HIP names, coreth/core/vm/contracts_pq.go and coreth/precompile/pqverify/, is not present, so the four addresses are declared and nothing dispatches to them |
| 23 | go:0105 | shipped | base/plugins holds extruntime, gojavm, wasmvm and v8vm (and jsvm, pyvm, starkvm) as Go packages, plus extbench — the runtime set the HIP specifies |
| 24 | go:0106 | shipped | cloud is the reference host and satisfies the contract as written. A plugin's main links its own subsystem and the request tier and nothing else — cloud/plugin/todo/main.go:1-27 is the shape, and all 127 share it; the paths it answers are declared in cloud/manifest/apps.go and projected from the plugin's own live router into cloud/plugin/<name>/openapi.json; cloud/plugin/gen-app-cmds/main.go holds the two views in bijection, refusing a manifest row with no plugin binary and a plugin binary with no row; and the declaration is checked by asking the composed router where each path goes — cloud/manifest/router_test.go:273 TestEveryServedPathReachesTheAppThatServesIt — rather than by reading a committed document |
| 25 | go:0107 | partial | vfs/replica/replica.go:171 PushLoop and fence.go:106 NewFencedStore give ship and hydrate with round fencing, which is what the HIP claims shipped. The generalisation is not there: hanzoai/replicate declares no replicate.Source interface and no --source flag, so the four adapters the HIP requires — sqlite-wal, zapdb-log, chain-state, generic-log — do not exist |
| 26 | go:0108 | shipped | ~/work/zap/zip/load.go:399 Load mounts a plugin that starts on the first request, :135 IdleAfter evicts it when traffic stops, and :852 supervise restarts it with capped backoff. The warm ceiling is derived from the container memory request at cloud/manifest/plugin.go:243 Warm() |
| 27 | go:0114 | partial | cloud/zapface/dispatch.go decodes a ZAP call and replays it through the whole Fiber app, and notify/internal/zaprpc/zaprpc.go carries the dot-prefixed RPC surface. Nothing implements the inter-VM thinking-chain hop the Draft is about |
| 28 | go:0118 | shipped | gateway/cmd/admin-guard/main.go is the single ForwardAuth gate: owner == AdminOrg reaches every admin surface, a brand-org admin reaches only admin.<brand>, and a non-admin is redirected rather than refused with 403 |
| 29 | go:0119 | shipped | cloud/serve.go:727 healthMux serves /healthz, /readyz (503 while draining) and /metrics on the ops listener only; config.go:310 binds :8080 from CLOUD_LISTEN and :328 binds 127.0.0.1:9090 from CLOUD_HEALTH_LISTEN — the two-listener split the HIP makes the contract |
| 30 | go:0125 | partial | placement exists and is not consensus-backed. cloud/shardrouter.go pins an org to one pod by rendezvous hashing through hanzoai/ha, and cloud imports no luxfi/consensus package at all. There is also no cloud.Register(name, order, fn): the composition root is the generated manifest plus zip.Load |
| 31 | go:0128 | shipped | cloud/apps/web3/web3.go:151 registers typed ops on the zip router, and that one registry projects the OpenAPI document, the CLI tree and the command palette — openapi/command.go hands the rendered document to zip.CommandsFromSpec rather than deriving a second command model |
| 32 | go:0132 | partial | POST /v1/event is the one ingest (cloud/apps/event) and cloud/telemetry.go installs a single tracer provider that routes co-resident or over the ZAP wire from one Send. The flat single-schema store that replaces the nine databases is not evidenced in Go |
| 33 | go:0133 | partial | the placement unit is the ORG, not an entity group: cloud/shardrouter.go pins org to pod by highest-random-weight and orgdb.go opens per-org stores through internal/org durability. No group manifest, no sub-org locality, no splitting, no promotion |
| 34 | go:0134 | shipped | ~/work/zap/zip/call.go:125 SocketPath is the one name-to-<RuntimeDir>/<name>.sock mapping and zip/load.go starts each child on its own private 0700 socket, so there is no plugin TCP port to authenticate. Identity is established once, at cloud/middleware_identity.go:228 SanitizeIdentity |
| 35 | go:0136 | partial | cloud/apps/platform/secrets.go:135 kmsSecretRef derives orgs/<org>/platform/<app>/<KEY> and is injective in (org, app, key), which is the derivability the HIP is for. The environment coordinate is dropped (env=default), so the path in use is not the <org>/<app>/<NAME>@<env> the HIP specifies |
| 36 | go:0139 | shipped | every gate the HIP names exists as a test rather than as prose. cloud/manifest/apps.go is the one place a capability's name and prefixes are decided; cloud/manifest/number.go carries the singular-canonical rule with the plural rewritten at the door, held by number_test.go:15, :52 and :85, the last of which refuses an alias that shadows a canonical prefix; cloud/manifest/router_test.go:273 asks the composed router where every served path goes; and cloud/openapi/misfiled.txt is the shrink-only ratchet for an address answered by an app not named in it — it now carries no entries, and openapi/misfiled_test.go:54 refuses a pair the file does not carry. In this repository the gate is scripts/coverage.py over capability-coverage.txt |
| 37 | go:0142 | none | Draft. No hanzo.yml under ~/work/hanzo carries a `kind:` key and no Go parses one — hanzoai/ci reads exactly one block, the image block at ci/declared.go:25, and nothing else |
| 38 | go:0300 | shipped | cloud/fleet/mcp.go:141 Use serves the fleet's POST /v1/mcp on the host and signposts the per-plugin framework path; manifest/door/door.go:14 pins the address so the challenge and the served route cannot disagree |
| 39 | go:0302 | partial | replicate ships the encrypted SQLite half — replica_encrypt_test.go, replicate_e2e_encrypt_test.go, the age envelope in replica.go. The ZapDB incremental-backup engine the HIP names as its second storage engine has no Go in the repository |
| 40 | go:0306 | shipped | ~/go/pkg/mod/github.com/luxfi/[email protected] is a Go module with pkg/{rules,sanctions,cases,screen,retention,replay,velocity} — the control families the HIP traces to named instruments |
| 41 | go:0412 | partial | a Go operator for this kind exists, under a different API group: nchain/api/v1alpha1/gateway_types.go with internal/controller/gateway_controller.go and config/crd/bases/nchain.hanzo.ai_gateways.yaml — nchain.hanzo.ai/v1alpha1, not the hanzo.ai/v1 the HIP pins, whose named reconciler is Rust |
| 42 | go:0414 | partial | nchain/internal/controller/network_controller.go:21 NetworkReconciler composes child NodeCluster, Chain, Indexer, Explorer, Bridge and Gateway CRs from api/v1alpha1/network_types.go:75 NetworkSpec, with generated CRD YAML — same group mismatch as HIP-0412 |
| 43 | go:0418 | partial | nchain/api/v1alpha1/indexer_types.go:8 IndexerSpec (chainRef, nodeClusterRef, storage) with internal/controller/indexer_controller.go and generated nchain.hanzo.ai_indexers.yaml. The HIP routes the kind through the Rust service.rs facade instead |
| 44 | go:0419 | partial | nchain/api/v1alpha1/explorer_types.go with internal/controller/explorer_controller.go, explorer_controller_test.go and generated nchain.hanzo.ai_explorers.yaml — again under nchain.hanzo.ai/v1alpha1 |
| 45 | go:0512 | partial | cloud/apps/experiment serves GET and POST /v1/experiment plus /:id, /:id/assign, /:id/analyze and /:id/decide (zipdoc_gen.go:10-134). The aggregates the HIP specifies — /v1/experiment/total, /project and /artifact — are absent |
| 46 | go:0516 | shipped | cloud/plugin/translate/main.go:20 is the app binary and manifest/apps.go:518 the fleet row that routes /v1/translate; its own router projection cloud/plugin/translate/openapi.json publishes 3 operations, and every route HIP-0516 names resolves in the composed fleet document cloud/private.yaml |
| 47 | go:0518 | shipped | ~/go/pkg/mod/github.com/luxfi/[email protected]/pkg/api/routes.go:201-211 registers POST /v1/aml/transactions, the case lifecycle, GET /v1/aml/rules and POST /v1/aml/rules/test — the surface the HIP specifies, in Go, in a module cloud's go.mod pins but never imports |
| 48 | go:0519 | shipped | cloud/middleware_identity.go:228 SanitizeIdentity is the one verification site, and the shard router runs immediately after it because the org is only trustworthy once minted there — which is the property this HIP is about |
| 49 | go:0520 | partial | the pinned-but-stateless cloud tier is real (cloud/shardrouter.go, highest-random-weight over ha.Owner) and plugins are reached over ZAP on a unix socket. The separate gateway tier is not what runs: HIP-0519 records the standalone gateway retired with Traefik fronting cloud, so the three-tier topology is one tier short in practice |
| 50 | go:0522 | partial | cloud/apps/graph/typed.go:43 serves assert, read, resolve, neighbors, search and vocabulary over a bitemporal fact store. The decision plane the HIP specifies — /v1/graph/decisions, /v1/graph/edges, /{id}/why and /v1/graph/provenance — is not registered |
| 51 | go:0523 | partial | cloud/apps/channels/envelope.go:61 Room is the envelope's room type with validated kinds, but the one store the HIP asks for does not exist: apps/channels, apps/team and apps/agents each hold a separate half of a conversation, which is the fragmentation the HIP documents as the problem |
| 52 | go:0524 | partial | cloud/apps/agents is Go and runs attributable runs (store.go Run.Actor), but the agent row is keyed by (org, name) with no user field and the store is one file per org, so the per-person agent the HIP requires cannot be represented. SeedPersonalities seeds an org, not a person |
| 53 | go:0902 | none | status Final, and no Go runs git ref updates through luxfi/consensus. git (module github.com/hanzoai/git) imports no consensus package, so the agreement half of the proposal is unimplemented |
| 54 | go:1000 | shipped | cloud/plugin/author/main.go:20 is the app binary and manifest/apps.go:455 the fleet row that routes /v1/admin/author, /v1/author; its own router projection cloud/plugin/author/openapi.json publishes 11 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1000 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 55 | go:1001 | shipped | cloud/plugin/books/main.go:20 is the app binary and manifest/apps.go:469 the fleet row that routes /v1/books/accounts, /v1/books/ask and 19 more; its own router projection cloud/plugin/books/openapi.json publishes 25 operations, and every route HIP-1001 names resolves in the composed fleet document cloud/private.yaml |
| 56 | go:1004 | shipped | cloud/plugin/licensing/main.go:22 is the app binary and manifest/apps.go:137 the fleet row that routes /v1/licensing; its own router projection cloud/plugin/licensing/openapi.json publishes 11 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1004 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 57 | go:1020 | shipped | cloud/apps/web3/web3.go:151-152 serves GET /v1/web3/chains and /chains/:chain from the operator-declared registry, and web3_test.go:86 pins that the registry never leaks the upstream URL |
| 58 | go:1021 | shipped | cloud/apps/web3/web3.go:153 POST /v1/web3/rpc/:chain forwards the JSON-RPC call to the resolved upstream and returns it unchanged; o.resolve gates it to ids that appear in the registry, which is the open-relay boundary the HIP is mostly about |
| 59 | go:1022 | shipped | cloud/apps/web3/web3.go:350 tokens issues exactly one eth_getBalance and returns only Native — the refusal to enumerate fungible or non-fungible positions is implemented as absence, as specified |
| 60 | go:1030 | shipped | cloud/openapi/openapi.go:1 — the document is projected from the live zip/fiber router through app.Fiber().GetRoutes(), so there is no second route registry to drift from; the fleet composition is openapi/fleet.go UseFleet over the 127 per-app subsets, and /v1/openapi.json and /v1/openapi/commands both resolve in cloud/private.yaml |
| 61 | go:1040 | shipped | cloud/apps/account/appearance.go:82 getAppearance and :105 setAppearance persist text size, density and accent on the IAM account rather than in the browser |
| 62 | go:1041 | shipped | cloud/plugin/authz/main.go:60 is the app binary and manifest/apps.go:99 the fleet row that routes /v1/authz/check, /v1/authz/health and 2 more; its own router projection cloud/plugin/authz/openapi.json publishes 3 operations, and every route HIP-1041 names resolves in the composed fleet document cloud/private.yaml |
| 63 | go:1042 | shipped | cloud/apps/account/avatar.go:147 putAvatar content-addresses the bytes — the key ends in the SHA-256 — and :254 getAvatar reads without credentials, both properties the HIP argues for |
| 64 | go:1043 | shipped | cloud/apps/account/csrf.go:82 CSRF mints a keyed MAC over the validated identity plus a timestamp; :104 RequireCSRF and :144 RequireCSRFOnSpend apply it, the latter reusing cloud.Intent so every paid seam is covered |
| 65 | go:1044 | shipped | the SuperAdmin cross-tenant org-settings row is served in Go at ai/controllers/zap_verticals-and-misc.go:130 — registerGatewayRoute behind the zapMiscAuthz gate, with ?owner selecting the subject org — at /v1/ai/org/settings rather than the bare /v1/org the HIP names |
| 66 | go:1045 | shipped | cloud/apps/account/onboarding.go with account.go's onboardResp carries the FIRST-RUN and ADDITIONAL distinction and mints the org's first credential once — AccessSecret is returned on the minting response only |
| 67 | go:1046 | shipped | cloud/plugin/risk/main.go:33 serves 11 operations — features, learn, policy, score, search, search/{id}, state, state/model and the app's own real health probe (OwnsHealth, so the generic always-ok liveness route cannot shadow it, manifest/apps.go:271). The HIP's §10 aside places labels, reference and datasets at nested /v1/risk/* addresses; the manifest gives each its own root (/v1/label, /v1/reference, /v1/dataset), which is what HIP-1261 and HIP-1262 specify and what the HIP says the code follows |
| 68 | go:1047 | shipped | cloud/plugin/security/main.go:20 is the app binary and manifest/apps.go:383 the fleet row that routes /v1/security; its own router projection cloud/plugin/security/openapi.json publishes 7 operations, and every route HIP-1047 names resolves in the composed fleet document cloud/private.yaml |
| 69 | go:1048 | shipped | cloud/plugin/team/main.go:20 is the app binary and manifest/apps.go:399 the fleet row that routes /v1/team; its own router projection cloud/plugin/team/openapi.json publishes 23 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1048 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 70 | go:1049 | shipped | cloud/plugin/validator/main.go:26 is the app binary and manifest/apps.go:296 the fleet row that routes /v1/validator; its own router projection cloud/plugin/validator/openapi.json publishes 4 operations, and every route HIP-1049 names resolves in the composed fleet document cloud/private.yaml |
| 71 | go:1060 | shipped | cloud/plugin/pubsub/main.go:20 is the app binary and manifest/apps.go:51 the fleet row that routes /v1/pubsub; its own router projection cloud/plugin/pubsub/openapi.json publishes 2 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1060 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 72 | go:1061 | shipped | cloud/plugin/mq/main.go:22 is the app binary and manifest/apps.go:65 the fleet row that routes /v1/mq; its own router projection cloud/plugin/mq/openapi.json publishes 15 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1061 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 73 | go:1062 | shipped | cloud/plugin/tasks/main.go:24 is the app binary and manifest/apps.go:478 the fleet row that routes /v1/tasks; its own router projection cloud/plugin/tasks/openapi.json publishes 10 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1062 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 74 | go:1063 | partial | cloud/plugin/auto/main.go:20 serves 17 operations covering connectors, flows, versions, runs and schedules. /v1/auto/pieces — the upstream-vocabulary alias the HIP requires beside /v1/auto/connectors so a client written against that contract needs no translation — is not registered |
| 75 | go:1064 | shipped | cloud/plugin/flow/main.go:22 is the app binary and manifest/apps.go:488 the fleet row that routes /v1/flow; its own router projection cloud/plugin/flow/openapi.json publishes 8 operations, and every route HIP-1064 names resolves in the composed fleet document cloud/private.yaml |
| 76 | go:1065 | shipped | cloud/apps/integrations/connectors.go:46 connectorRoutes with :560 refreshConn, :606 tokenConn and :653 dropConn — the per-user credential plane sharing the org registry and store, keyed by user |
| 77 | go:1066 | shipped | cloud/plugin/channels/main.go:20 is the app binary and manifest/apps.go:410 the fleet row that routes /v1/channels; its own router projection cloud/plugin/channels/openapi.json publishes 9 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1066 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 78 | go:1067 | shipped | cloud/plugin/destination/main.go:20 is the app binary and manifest/apps.go:389 the fleet row that routes /v1/destination; its own router projection cloud/plugin/destination/openapi.json publishes 5 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1067 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 79 | go:1069 | shipped | cloud/plugin/tel/main.go:23 is the app binary and manifest/apps.go:479 the fleet row that routes /v1/tel; its own router projection cloud/plugin/tel/openapi.json publishes 10 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1069 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 80 | go:1100 | shipped | cloud/plugin/ad/main.go:20 is the app binary and manifest/apps.go:294 the fleet row that routes /v1/ad; its own router projection cloud/plugin/ad/openapi.json publishes 7 operations, and every route HIP-1100 names resolves in the composed fleet document cloud/private.yaml |
| 81 | go:1101 | shipped | cloud/plugin/allowance/main.go:22 is the app binary and manifest/apps.go:180 the fleet row that routes /v1/allowance; its own router projection cloud/plugin/allowance/openapi.json publishes 1 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1101 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 82 | go:1102 | shipped | cloud/plugin/ask/main.go:20 is the app binary and manifest/apps.go:517 the fleet row that routes /v1/ask; its own router projection cloud/plugin/ask/openapi.json publishes 2 operations, and every route HIP-1102 names resolves in the composed fleet document cloud/private.yaml |
| 83 | go:1104 | shipped | cloud/plugin/base/main.go:20 is the app binary and manifest/apps.go:90 the fleet row that routes /v1/base, /v1/waitlist; its own router projection cloud/plugin/base/openapi.json publishes 3 operations, and every route HIP-1104 names resolves in the composed fleet document cloud/private.yaml |
| 84 | go:1105 | shipped | cloud/plugin/benchmark/main.go:20 is the app binary and manifest/apps.go:466 the fleet row that routes /v1/benchmark; its own router projection cloud/plugin/benchmark/openapi.json publishes 9 operations, and every route HIP-1105 names resolves in the composed fleet document cloud/private.yaml |
| 85 | go:1106 | shipped | cloud/plugin/blueprint/main.go:20 is the app binary and manifest/apps.go:220 the fleet row that routes /v1/blueprint; its own router projection cloud/plugin/blueprint/openapi.json publishes 3 operations, and every route HIP-1106 names resolves in the composed fleet document cloud/private.yaml |
| 86 | go:1107 | shipped | cloud/plugin/bot/main.go:36 is the app binary and manifest/apps.go:447 the fleet row that routes /v1/bot; its own router projection cloud/plugin/bot/openapi.json publishes 8 operations, and every route HIP-1107 names resolves in the composed fleet document cloud/private.yaml |
| 87 | go:1110 | shipped | cloud/plugin/campaign/main.go:20 is the app binary and manifest/apps.go:295 the fleet row that routes /v1/campaign; its own router projection cloud/plugin/campaign/openapi.json publishes 11 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1110 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 88 | go:1111 | shipped | cloud/plugin/captable/main.go:20 is the app binary and manifest/apps.go:343 the fleet row that routes /v1/captable; its own router projection cloud/plugin/captable/openapi.json publishes 31 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1111 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 89 | go:1112 | shipped | cloud/plugin/catalog/main.go:20 is the app binary and manifest/apps.go:427 the fleet row that routes /v1/catalog; its own router projection cloud/plugin/catalog/openapi.json publishes 1 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1112 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 90 | go:1113 | shipped | cloud/plugin/cloudflare/main.go:20 is the app binary and manifest/apps.go:390 the fleet row that routes /v1/cloudflare; its own router projection cloud/plugin/cloudflare/openapi.json publishes 33 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1113 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 91 | go:1115 | shipped | cloud/plugin/compliance/main.go:27 is the app binary and manifest/apps.go:508 the fleet row that routes /v1/compliance; its own router projection cloud/plugin/compliance/openapi.json publishes 17 operations, and every route HIP-1115 names resolves in the composed fleet document cloud/private.yaml |
| 92 | go:1116 | shipped | cloud/plugin/content/main.go:20 is the app binary and manifest/apps.go:229 the fleet row that routes /v1/content; its own router projection cloud/plugin/content/openapi.json publishes 6 operations, and every route HIP-1116 names resolves in the composed fleet document cloud/private.yaml |
| 93 | go:1117 | shipped | cloud/plugin/crawl/main.go:28 is the app binary and manifest/apps.go:421 the fleet row that routes /v1/crawl; its own router projection cloud/plugin/crawl/openapi.json publishes 1 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1117 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 94 | go:1121 | shipped | cloud/plugin/dataroom/main.go:21 is the app binary and manifest/apps.go:375 the fleet row that routes /v1/dataroom, /v1/admin/dataroom; its own router projection cloud/plugin/dataroom/openapi.json publishes 27 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1121 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 95 | go:1122 | shipped | cloud/plugin/deploy/main.go:20 is the app binary and manifest/apps.go:216 the fleet row that routes /v1/deploy/account/can-i, /v1/deploy/applications and 12 more; its own router projection cloud/plugin/deploy/openapi.json publishes 21 operations, and every route HIP-1122 names resolves in the composed fleet document cloud/private.yaml |
| 96 | go:1123 | shipped | cloud/plugin/domain/main.go:27 is the app binary and manifest/apps.go:199 the fleet row that routes /v1/domain; its own router projection cloud/plugin/domain/openapi.json publishes 7 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1123 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 97 | go:1124 | shipped | cloud/plugin/engine/main.go:22 is the app binary and manifest/apps.go:489 the fleet row that routes /v1/engine; its own router projection cloud/plugin/engine/openapi.json publishes 4 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1124 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 98 | go:1125 | shipped | cloud/plugin/esign/main.go:20 is the app binary and manifest/apps.go:458 the fleet row that routes /v1/esign; its own router projection cloud/plugin/esign/openapi.json publishes 13 operations, and every route HIP-1125 names resolves in the composed fleet document cloud/private.yaml |
| 99 | go:1126 | shipped | cloud/plugin/framework/main.go:38 is the app binary and manifest/apps.go:221 the fleet row that routes /v1/framework; its own router projection cloud/plugin/framework/openapi.json publishes 16 operations, and every route HIP-1126 names resolves in the composed fleet document cloud/private.yaml |
| 100 | go:1127 | shipped | cloud/plugin/gateway/main.go:20 is the app binary and manifest/apps.go:411 the fleet row that routes /v1/gateway; its own router projection cloud/plugin/gateway/openapi.json publishes 3 operations, and every route HIP-1127 names resolves in the composed fleet document cloud/private.yaml |
| 101 | go:1130 | shipped | cloud/plugin/guide/main.go:20 is the app binary and manifest/apps.go:506 the fleet row that routes /v1/guide; its own router projection cloud/plugin/guide/openapi.json publishes 19 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1130 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 102 | go:1131 | shipped | cloud/plugin/help/main.go:20 is the app binary and manifest/apps.go:228 the fleet row that routes /v1/help; its own router projection cloud/plugin/help/openapi.json publishes 4 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1131 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 103 | go:1132 | shipped | cloud/plugin/index/main.go:20 is the app binary and manifest/apps.go:426 the fleet row that routes /v1/index; its own router projection cloud/plugin/index/openapi.json publishes 17 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1132 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 104 | go:1133 | shipped | cloud/plugin/ingress/main.go:20 is the app binary and manifest/apps.go:75 the fleet row that routes /v1/ingress; its own router projection cloud/plugin/ingress/openapi.json publishes 18 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1133 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 105 | go:1134 | shipped | cloud/plugin/kms/main.go:20 is the app binary and manifest/apps.go:68 the fleet row that routes /v1/kms; its own router projection cloud/plugin/kms/openapi.json publishes 7 operations, and every route HIP-1134 names resolves in the composed fleet document cloud/private.yaml |
| 106 | go:1135 | shipped | cloud/plugin/legal/main.go:20 is the app binary and manifest/apps.go:516 the fleet row that routes /v1/legal; its own router projection cloud/plugin/legal/openapi.json publishes 11 operations, and every route HIP-1135 names resolves in the composed fleet document cloud/private.yaml |
| 107 | go:1136 | shipped | cloud/plugin/marketing/main.go:20 is the app binary and manifest/apps.go:293 the fleet row that routes /v1/marketing; its own router projection cloud/plugin/marketing/openapi.json publishes 35 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1136 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 108 | go:1137 | shipped | cloud/plugin/marketplace/main.go:20 is the app binary and manifest/apps.go:504 the fleet row that routes /v1/marketplace; its own router projection cloud/plugin/marketplace/openapi.json publishes 6 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1137 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 109 | go:1140 | shipped | cloud/plugin/ml/main.go:20 is the app binary and manifest/apps.go:231 the fleet row that routes /v1/ml/health, /v1/ml/models; its own router projection cloud/plugin/ml/openapi.json publishes 7 operations, and every route HIP-1140 names resolves in the composed fleet document cloud/private.yaml |
| 110 | go:1141 | shipped | cloud/plugin/pref/main.go:20 is the app binary and manifest/apps.go:408 the fleet row that routes /v1/pref; its own router projection cloud/plugin/pref/openapi.json publishes 2 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1141 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 111 | go:1142 | shipped | cloud/plugin/prompt/main.go:20 is the app binary and manifest/apps.go:200 the fleet row that routes /v1/prompt; its own router projection cloud/plugin/prompt/openapi.json publishes 6 operations, and every route HIP-1142 names resolves in the composed fleet document cloud/private.yaml |
| 112 | go:1144 | shipped | cloud/plugin/registry/main.go:22 is the app binary and manifest/apps.go:490 the fleet row that routes /v1/registry; its own router projection cloud/plugin/registry/openapi.json publishes 6 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1144 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 113 | go:1145 | shipped | cloud/plugin/research/main.go:20 is the app binary and manifest/apps.go:467 the fleet row that routes /v1/research; its own router projection cloud/plugin/research/openapi.json publishes 8 operations, and every route HIP-1145 names resolves in the composed fleet document cloud/private.yaml |
| 114 | go:1146 | shipped | cloud/plugin/sandbox/main.go:29 is the app binary and manifest/apps.go:419 the fleet row that routes /v1/sandbox; its own router projection cloud/plugin/sandbox/openapi.json publishes 19 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1146 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 115 | go:1147 | partial | cloud/plugin/search/main.go:17 serves POST /v1/search, the one ranked result set the HIP specifies. The fleet inventory reads § names — GET /v1/search/indexes and GET /v1/search/stats — have no route (cloud/plugin/search/openapi.json declares 3 operations) |
| 116 | go:1150 | shipped | cloud/plugin/seo/main.go:28 is the app binary and manifest/apps.go:425 the fleet row that routes /v1/seo; its own router projection cloud/plugin/seo/openapi.json publishes 7 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1150 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 117 | go:1151 | shipped | cloud/plugin/settings/main.go:20 is the app binary and manifest/apps.go:407 the fleet row that routes /v1/settings; its own router projection cloud/plugin/settings/openapi.json publishes 2 operations, and every route HIP-1151 names resolves in the composed fleet document cloud/private.yaml |
| 118 | go:1152 | shipped | cloud/plugin/share/main.go:27 is the app binary and manifest/apps.go:371 the fleet row that routes /v1/share; its own router projection cloud/plugin/share/openapi.json publishes 2 operations, and every route HIP-1152 names resolves in the composed fleet document cloud/private.yaml |
| 119 | go:1153 | shipped | cloud/plugin/social/main.go:20 is the app binary and manifest/apps.go:297 the fleet row that routes /v1/social; its own router projection cloud/plugin/social/openapi.json publishes 13 operations, and every route HIP-1153 names resolves in the composed fleet document cloud/private.yaml |
| 120 | go:1154 | shipped | cloud/plugin/sync/main.go:20 is the app binary and manifest/apps.go:341 the fleet row that routes /v1/sync; its own router projection cloud/plugin/sync/openapi.json publishes 6 operations, and every route HIP-1154 names resolves in the composed fleet document cloud/private.yaml |
| 121 | go:1155 | shipped | cloud/plugin/taxonomy/main.go:22 is the app binary and manifest/apps.go:432 the fleet row that routes /v1/taxonomy; its own router projection cloud/plugin/taxonomy/openapi.json publishes 5 operations, and every route HIP-1155 names resolves in the composed fleet document cloud/private.yaml |
| 122 | go:1156 | shipped | cloud/plugin/template/main.go:20 is the app binary and manifest/apps.go:219 the fleet row that routes /v1/template; its own router projection cloud/plugin/template/openapi.json publishes 5 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1156 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 123 | go:1160 | shipped | cloud/plugin/todo/main.go:20 is the app binary and manifest/apps.go:218 the fleet row that routes /v1/todo; its own router projection cloud/plugin/todo/openapi.json publishes 13 operations, and every route HIP-1160 names resolves in the composed fleet document cloud/private.yaml |
| 124 | go:1161 | shipped | cloud/plugin/wallet/main.go:27 is the app binary and manifest/apps.go:214 the fleet row that routes /v1/wallet; its own router projection cloud/plugin/wallet/openapi.json publishes 8 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1161 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 125 | go:1163 | shipped | cloud/plugin/x402/main.go:20 is the app binary and manifest/apps.go:215 the fleet row that routes /v1/x402; its own router projection cloud/plugin/x402/openapi.json publishes 1 operations, and every route HIP-1163 names resolves in the composed fleet document cloud/private.yaml |
| 126 | go:1164 | shipped | cloud/plugin/provisioning/main.go:20 is the app binary and manifest/apps.go:164 the fleet row that routes /v1/admin/provisioning, /v1/provisioning; its own router projection cloud/plugin/provisioning/openapi.json publishes 30 operations, and every route HIP-1164 names resolves in the composed fleet document cloud/private.yaml |
| 127 | go:1165 | shipped | cloud/plugin/s3/main.go:20 is the app binary and manifest/apps.go:150 the fleet row that routes /v1/s3/buckets, /v1/s3/health; its own router projection cloud/plugin/s3/openapi.json publishes 8 operations, and every route HIP-1165 names resolves in the composed fleet document cloud/private.yaml |
| 128 | go:1167 | shipped | cloud/plugin/dataset/main.go:30 is the app binary and manifest/apps.go:286 the fleet row that routes /v1/dataset; its own router projection cloud/plugin/dataset/openapi.json publishes 7 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1167 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 129 | go:1172 | shipped | cloud/plugin/visor/main.go:20 is the app binary and manifest/apps.go:342 the fleet row that routes /v1/visor; its own router projection cloud/plugin/visor/openapi.json publishes 34 operations, and every route HIP-1172 names resolves in the composed fleet document cloud/private.yaml |
| 130 | go:1173 | shipped | cloud/plugin/network/main.go:28 is the app binary and manifest/apps.go:370 the fleet row that routes /v1/network; its own router projection cloud/plugin/network/openapi.json publishes 8 operations, and every route HIP-1173 names resolves in the composed fleet document cloud/private.yaml |
| 131 | go:1180 | shipped | cloud/plugin/link/main.go:20 is the app binary and manifest/apps.go:213 the fleet row that routes /v1/link; its own router projection cloud/plugin/link/openapi.json publishes 11 operations, and every route HIP-1180 names resolves in the composed fleet document cloud/private.yaml |
| 132 | go:1181 | partial | the whole surface answers one letter off the address HIP-1181 fixes. The HIP names 15 operations under /v1/plans; manifest/apps.go:138 gives the app the prefix /v1/plan, and all 14 served routes (cloud/plugin/plan/openapi.json) sit there. cloud/plugin/skills/main.go:26 names this same defect in passing — 'apps/plan, whose name was one letter off its prefix'. /v1/plan/cloud, /v1/plan/entries and /v1/plan/seed have no route under either spelling |
| 133 | go:1189 | shipped | cloud/plugin/web3/main.go:24 is the app binary and manifest/apps.go:437 the fleet row that routes /v1/web3; its own router projection cloud/plugin/web3/openapi.json publishes 4 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1189 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 134 | go:1198 | shipped | cloud/plugin/graph/main.go:23 is the app binary and manifest/apps.go:227 the fleet row that routes /v1/graph; its own router projection cloud/plugin/graph/openapi.json publishes 7 operations, and every route HIP-1198 names resolves in the composed fleet document cloud/private.yaml |
| 135 | go:1200 | shipped | cloud/plugin/account/main.go:20 is the app binary and manifest/apps.go:76 the fleet row that routes /v1/account; its own router projection cloud/plugin/account/openapi.json publishes 10 operations, and every route HIP-1200 names resolves in the composed fleet document cloud/private.yaml |
| 136 | go:1201 | shipped | cloud/plugin/admission/main.go:21 is the app binary and manifest/apps.go:472 the fleet row that routes /v1/admission; its own router projection cloud/plugin/admission/openapi.json publishes 1 operations, and every route HIP-1201 names resolves in the composed fleet document cloud/private.yaml |
| 137 | go:1202 | shipped | cloud/plugin/entitlement/main.go:20 is the app binary and manifest/apps.go:412 the fleet row that routes /v1/entitlement; its own router projection cloud/plugin/entitlement/openapi.json publishes 3 operations, and every route HIP-1202 names resolves in the composed fleet document cloud/private.yaml |
| 138 | go:1203 | shipped | cloud/plugin/affiliate/main.go:20 serves 17 operations; every operator action HIP-1203 §1 lists — the board, approve, rate, suspend, payout, sweep and the referral-analytics read — resolves under the singular stem manifest/apps.go:457 declares, /v1/admin/affiliate, including /v1/admin/affiliate/referrals. The HIP writes the plural and says that last read is still misfiled at /v1/admin/referrals; the fold has happened and cloud/openapi/misfiled.txt now carries no entries |
| 139 | go:1210 | shipped | cloud/plugin/agents/main.go:26 is the app binary and manifest/apps.go:212 the fleet row that routes /v1/agents; its own router projection cloud/plugin/agents/openapi.json publishes 39 operations, and every route HIP-1210 names resolves in the composed fleet document cloud/private.yaml |
| 140 | go:1211 | shipped | cloud/plugin/ai/main.go:20 is the app binary and manifest/apps.go the fleet row for /v1/ai, whose projection publishes the largest surface in the fleet — 1741 paths in cloud/private.yaml, including the finetune, memory, rag and router subtrees. The six roots HIP-1211 §2 says are DELETED rather than moved — /v1/documents, /v1/query, /v1/query_multiple, /v1/dev-bridge, /v1/install-patch, /v1/wecom-bot — are absent, which is what the HIP requires |
| 141 | go:1212 | shipped | cloud/plugin/exec/main.go:20 serves 5 operations; /v1/exec/download/{wildcard1} in cloud/private.yaml is the byte-returning download the HIP writes as /v1/exec/download/{session_id}/{fileId} — one greedy segment rather than two named ones, same address space |
| 142 | go:1213 | shipped | cloud/plugin/tools/main.go:21 is the app binary and manifest/apps.go:503 the fleet row that routes /v1/tools; its own router projection cloud/plugin/tools/openapi.json publishes 19 operations, and every route HIP-1213 names resolves in the composed fleet document cloud/private.yaml |
| 143 | go:1214 | shipped | cloud/plugin/lsp/main.go:30 is the app binary and manifest/apps.go:353 the fleet row that routes /v1/lsp; its own router projection cloud/plugin/lsp/openapi.json publishes 5 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1214 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 144 | go:1220 | partial | cloud/plugin/commerce/main.go:20 serves 181 operations across cart, catalog, store, ledger, invoices and plans. /v1/commerce/payments, which the HIP lists as the typed payment endpoint folded in from /v1/payments, was retired as a second address onto the same card money move once /v1/billing/topup/card became a typed op (cloud/apps/commerce/risk_payments_test.go:64); the HIP still names it |
| 145 | go:1221 | shipped | cloud/plugin/treasury/main.go:21 is the app binary and manifest/apps.go:470 the fleet row that routes /v1/admin/treasury, /v1/treasury; its own router projection cloud/plugin/treasury/openapi.json publishes 8 operations, and every route HIP-1221 names resolves in the composed fleet document cloud/private.yaml |
| 146 | go:1222 | shipped | cloud/plugin/pricing/main.go:21 is the app binary and manifest/apps.go:139 the fleet row that routes /v1/admin/pricing, /v1/pricing; its own router projection cloud/plugin/pricing/openapi.json publishes 33 operations, and every route HIP-1222 names resolves in the composed fleet document cloud/private.yaml |
| 147 | go:1230 | shipped | cloud/plugin/platform/main.go:20 is the app binary and manifest/apps.go:196 the fleet row that routes /v1/platform; its own router projection cloud/plugin/platform/openapi.json publishes 37 operations, and every route HIP-1230 names resolves in the composed fleet document cloud/private.yaml |
| 148 | go:1231 | shipped | cloud/plugin/projects/main.go:21 is the app binary and manifest/apps.go:197 the fleet row that routes /v1/projects; its own router projection cloud/plugin/projects/openapi.json publishes 29 operations, and every route HIP-1231 names resolves in the composed fleet document cloud/private.yaml |
| 149 | go:1232 | shipped | cloud/plugin/git/main.go:20 is the app binary and manifest/apps.go:340 the fleet row that routes /v1/git; its own router projection cloud/plugin/git/openapi.json publishes 46 operations, and every route HIP-1232 names resolves in the composed fleet document cloud/private.yaml |
| 150 | go:1240 | shipped | cloud/plugin/o11y/main.go:None is the app binary and manifest/apps.go:98 the fleet row that routes /v1/o11y; its own router projection cloud/plugin/o11y/openapi.json publishes 381 operations, and every route HIP-1240 names resolves in the composed fleet document cloud/private.yaml |
| 151 | go:1241 | shipped | cloud/plugin/metrics/main.go:19 is the app binary and manifest/apps.go:74 the fleet row that routes /v1/metrics; its own router projection cloud/plugin/metrics/openapi.json publishes 11 operations, and every route HIP-1241 names resolves in the composed fleet document cloud/private.yaml |
| 152 | go:1242 | shipped | cloud/plugin/leaderboard/main.go:21 is the app binary and manifest/apps.go:292 the fleet row that routes /v1/admin/leaderboard, /v1/leaderboard; its own router projection cloud/plugin/leaderboard/openapi.json publishes 6 operations, and every route HIP-1242 names resolves in the composed fleet document cloud/private.yaml |
| 153 | go:1250 | shipped | cloud/plugin/integrations/main.go:21 is the app binary and manifest/apps.go:384 the fleet row that routes /v1/integrations; its own router projection cloud/plugin/integrations/openapi.json publishes 54 operations, and every route HIP-1250 names resolves in the composed fleet document cloud/private.yaml |
| 154 | go:1251 | shipped | cloud/plugin/websearch/main.go:29 is the app binary and manifest/apps.go:420 the fleet row that routes /v1/websearch; its own router projection cloud/plugin/websearch/openapi.json publishes 7 operations, and every route HIP-1251 names resolves in the composed fleet document cloud/private.yaml |
| 155 | go:1253 | shipped | cloud/plugin/explorer/main.go:20 is the app binary and manifest/apps.go:376 the fleet row that routes /v1/explorer; its own router projection cloud/plugin/explorer/openapi.json publishes 2 operations, and every route HIP-1253 names resolves in the composed fleet document cloud/private.yaml |
| 156 | go:1260 | shipped | cloud/plugin/knowledge/main.go:26 is the app binary and manifest/apps.go:223 the fleet row that routes /v1/knowledge; its own router projection cloud/plugin/knowledge/openapi.json publishes 10 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1260 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 157 | go:1261 | shipped | cloud/plugin/label/main.go:26 is the app binary and manifest/apps.go:261 the fleet row that routes /v1/label; its own router projection cloud/plugin/label/openapi.json publishes 7 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1261 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 158 | go:1262 | shipped | cloud/plugin/reference/main.go:20 is the app binary and manifest/apps.go:268 the fleet row that routes /v1/reference; its own router projection cloud/plugin/reference/openapi.json publishes 6 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1262 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 159 | go:1310 | shipped | cloud/plugin/webhook/main.go:20 is the app binary and manifest/apps.go:230 the fleet row that routes /v1/webhook; its own router projection cloud/plugin/webhook/openapi.json publishes 8 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1310 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 160 | go:1311 | shipped | cloud/plugin/experiment/main.go:20 is the app binary and manifest/apps.go:468 the fleet row that routes /v1/experiment; its own router projection cloud/plugin/experiment/openapi.json publishes 7 operations, and every route HIP-1311 names resolves in the composed fleet document cloud/private.yaml |
| 161 | go:1312 | shipped | cloud/plugin/company/main.go:26 is the app binary and manifest/apps.go:507 the fleet row that routes /v1/company; its own router projection cloud/plugin/company/openapi.json publishes 24 operations, and every route HIP-1312 names resolves in the composed fleet document cloud/private.yaml |
| 162 | go:1321 | shipped | cloud/plugin/dns/main.go:20 is the app binary and manifest/apps.go:198 the fleet row that routes /v1/dns; its own router projection cloud/plugin/dns/openapi.json publishes 12 operations, all of which resolve in the composed fleet document cloud/private.yaml. HIP-1321 fixes the capability rather than enumerating route literals, so the projection is the surface |
| 163 | go:1322 | shipped | cloud/plugin/skills/main.go:21 is the app binary and manifest/apps.go:66 the fleet row that routes /.well-known/agent-skills/:skill/SKILL.md, /.well-known/agent-skills/:product/index.json and 1 more; its own router projection cloud/plugin/skills/openapi.json publishes 3 operations, and every route HIP-1322 names resolves in the composed fleet document cloud/private.yaml |
| 164 | go:1323 | shipped | cloud/apps/kafka/kafka.go:1 — the app speaks the KAFKA wire protocol on :9092 and translates it onto the one JetStream bus apps/pubsub serves, so it registers no HTTP operation and cloud/plugin/kafka/openapi.json is empty by construction; manifest/apps.go:60 is the fleet row, Eager, and cloud/plugin/kafka/main.go:20 the binary |
| 165 | go:1324 | shipped | cloud/plugin/kv/main.go:26 is the app binary and manifest/apps.go:59 the fleet row that routes /v1/kv; its own router projection cloud/plugin/kv/openapi.json publishes 6 operations, and every route HIP-1324 names resolves in the composed fleet document cloud/private.yaml |
| 166 | go:1325 | shipped | cloud/plugin/node/main.go:30 is the app binary and manifest/apps.go:454 the fleet row that routes /v1/node; its own router projection cloud/plugin/node/openapi.json publishes 4 operations, and every route HIP-1325 names resolves in the composed fleet document cloud/private.yaml |
| 167 | go:1326 | shipped | cloud/apps/amqp/amqp.go:1 — the app speaks the AMQP wire protocol 0-9-1 on :5672 and translates it onto the one JetStream bus apps/pubsub serves, so it registers no HTTP operation and cloud/plugin/amqp/openapi.json is empty by construction; manifest/apps.go:64 is the fleet row, Eager, and cloud/plugin/amqp/main.go:25 the binary |
| 168 | cpp:0043 | shipped | engine/hanzo-quant/kernels holds a CUDA directory for every quantization format HIP-0043:22 enumerates — marlin, hqq, afq, scalar/vector/blockwise fp8, mmq_gguf, mxfp4 — and engine/hanzo-paged-attn/src/cuda/pagedattention.cuh:1 gives PagedAttention CUDA, Metal and ROCm backends, 46,261 lines in total. The C++ is inherited rather than authored: pagedattention.cuh credits vLLM and NVIDIA FasterTransformer, which is consistent with HIP-0043:20,26 declaring the engine to BE the mistral.rs fork, so the fork's kernels are the specified artifact |
| 169 | cpp:0120 | partial | datastore/src/Server/ZAP/ZAPHandler.cpp:1 makes the C++ datastore speak ZAP natively on :9655 (MSG_DATASTORE=302), started from programs/server/Server.cpp:2999 under CMake target datastore_server_zap. It is 372 lines of Hanzo-original C++ and the only non-Go application of the HIP's rule. It routes only /query and /exec to executeQuery, is single-threaded per connection with no auth, TLS or streaming, and HIP-0120:38's conformance check greps .go files only, so nothing holds this side to the rule |
| 170 | rust:0005 | partial | node/hanzo-libs/hanzo-pqc/src/lib.rs:1 implements FIPS 203/204/205 with the HIP's mandated defaults — config.rs:67-73 pins ML-KEM-768, ML-DSA-65 and hybrid ML-KEM-768+X25519 — across kem, signature, kdf, hybrid, wire_protocol and attestation, 3,928 lines. The separate crypto crate (2,157 lines) is not a second implementation: crypto/src/lib.rs:11-13 re-exports the ml_kem, ml_dsa and pqcrypto_hqc crates and adds symmetric, hash and error wrappers. The AI-specific layers the HIP adds on top — model-weight protection, PQ-signed model artifacts — are in neither crate |
| 171 | rust:0010 | shipped | mcp/rust/src/lib.rs:2 declares the Rust row of the HIP's implementation table; the Core Tools column is satisfied by src/tools/ — exec, fs, think, memory, plan, mode, computer, browser, git, code and lsp. JSON-RPC tools/list and tools/call are wired at src/server.rs:53 and :67. 28,265 lines |
| 172 | rust:0015 | partial | mcp/rust/src/tools/computer_tool/mod.rs:96 dispatches the HIP's InputControl and ScreenCapture verbs — click, doubleClick, rightClick, middleClick, move, moveRelative, drag, scroll, type, press, keyDown, keyUp, hotkey, screenshot, screenshotRegion, getScreens, screenSize, batch — over macos.rs, linux.rs and windows.rs, with Playwright browser automation at src/tools/browser_tool.rs. Missing: the recording session API (session, record, stop, SessionResult, activity detection) and the touch verbs tap, swipe and pinch |
| 173 | rust:0019 | partial | ml/hanzo-ml/src/device.rs:32 Device carries Cpu, Cuda, Metal, Rocm, Vulkan and Wgpu, dtype.rs:9 the DType set, and quantized/ has the k-quant, GGUF and imatrix kernels the HIP's quantization table names. The Hamiltonian Dynamics section — symplectic_euler_step, leapfrog_step, hamiltonian_energy — has no implementation: a case-insensitive grep for hamiltonian over the whole ml tree returns nothing |
| 174 | rust:0020 | partial | node is a 336,025-line Rust node, but three of the four subsystems the HIP's architecture names are different things. Networking: node/hanzo-libs/hanzo-libp2p/Cargo.toml:31 enables tcp, noise, yamux, identify, ping, relay, dcutr and request-response — no gossipsub, no kademlia, no mdns. Consensus: node/hanzo-libs/hanzo-consensus/src/lib.rs:1-10 is Quasar over lux-consensus, not PoAI, and grep for PoAI or proof_of_ai returns nothing. Storage: rusqlite and sqlite-vec (node/hanzo-libs/hanzo-db-sqlite/Cargo.toml:16), not RocksDB. As specified: Lux settlement at node/hanzo-libs/hanzo-l2/src/commitment.rs:1 and the compute inventory at node/hanzo-libs/hanzo-compute/src/peer.rs |
| 175 | rust:0040 | partial | rust-sdk/crates/hanzo-client is the Rust row of the HIP's SDK table: 119 modules under src/apis, 2,523 typed models, 217,187 lines, generated from cloud's openapi.yaml (src/apis/configuration.rs:1-8). Two deviations: the generator is openapi-generator driven by hanzoai/openapi rather than the Stainless the HIP names, and the uniform retry and backoff classification is absent — Configuration (configuration.rs:14-22) carries base_path, user_agent, client and credentials, with no max_retries or backoff anywhere in the crate |
| 176 | rust:0041 | shipped | cli/src/commands/product/generated.rs is the committed generated command tree (1.35 MB), produced by cli/src/bin/genproduct.rs from cli/spec/cloud.json, which cli/src/bin/genspec.rs emits from cloud's openapi.yaml. genspec, genproduct and driftgate sit behind cargo features (cli/Cargo.toml:14-44) and there is no build.rs, so the shipped binary parses no YAML — the four normative properties of §1 hold as written |
| 177 | rust:0043 | shipped | engine/hanzo-engine/src/lib.rs:513 `pub struct Hanzo` is the serving loop (the renamed mistral.rs MistralRs); the OpenAI surface is engine/hanzo-server-core/src/router.rs:315-331, where /v1/chat/completions, /v1/completions, /v1/embeddings and /v1/models resolve, plus /v1/messages for the Anthropic wire. PagedAttention (hanzo-paged-attn, cuda/metal/rocm/vulkan), the quantization matrix the HIP lists (hanzo-quant/src/{gguf,afq,fp8,blockwise_fp8,bitsandbytes,f8q8}), PyO3 bindings and MCP are all present crates |
| 178 | rust:0050 | partial | edge/edge-core/src/lib.rs:1 is a real GGUF-on-Candle on-device runtime — model, sampling, session and tokenizer — with edge-cli run/serve/bench/info and a 282-line edge-wasm crate, defaulting to zenlm/zen3-nano at Q4_K_M (edge-core/src/model.rs:74), 2,760 lines over 13 files. Missing against the HIP: the Swift and Kotlin SDKs, local MCP tool execution, the maxMemoryBytes budget and the cloud-fallback path; none of those strings occur in the crate |
| 179 | rust:0088 | none | the ZAP wire is implemented in Rust in four places — zap/rust, node/hanzo-libs/hanzo-zap, evm/crates/hanzo-zap and platform/pkg/zap — so the session KEM would live there, and it does not. evm/crates/hanzo-zap/src/handshake.rs:12 is the whole handshake: a 4-byte length, protocol version 42, an address and a 1-byte ACK. No ML-KEM-768 or -1024 encapsulation, no KMAC256-keyed HKDF-Extract, no AEAD derivation; grep for ml_kem or MlKem across all four crates returns nothing |
| 180 | rust:0111 | partial | cli/src/iam/paths.rs:14-20 pins the exact HIP-0111 paths, /v1/iam/oauth/{authorize,token,userinfo,revoke}, with a comment stating no discovery, no legacy /oauth/*, no /api/; cli/src/iam/{oauth,pkce,device,token}.rs implement authorization-code with PKCE-S256 and the device flow against them, 4,854 lines. This is the client half only: the provider is not Rust, and the SCIM 2.0 and RFC 7662 introspection surfaces have no Rust caller |
| 181 | rust:0113 | partial | engine/hanzo-engine-ffi/src/lib.rs:82 hanzo_ffi_infer and :120 hanzo_ffi_embed are the C ABI the HIP names for a bonded provider to load registered models through, 306 lines with a matching free. The rest has no Rust: no commit-reveal quorum, no Proof-of-Thought receipt type, and none of the Cognitive Sidecar artifacts (ProposalDraft, VoteRecommendation, ConfigPatch, RiskReport, OperatorAction, BridgeHealthAlert) appear in the tree |
| 182 | rust:0114 | partial | zap/rust/src/lib.rs:1 is the canonical Rust ZAP implementation — 16-byte little-endian header (wire.rs Header, read_frame, write_frame), offset-driven slot regions, schema bindings from the in-tree zapc compiler at zap/zapc-rs, byte-aligned with the Go and TypeScript references. The cognitive layer this HIP is about is missing: the inference-intent, settled-receipt and operator-message procedure set does not appear — src/msg.rs and src/schema.rs carry the generic service procedures only |
| 183 | rust:0120 | shipped | every Rust service in the tree serves or dials ZAP and none links gRPC. engine/hanzo-server/src/zap_server.rs:1 is the engine's native ZAP listener mapping ZAP methods onto the axum routes; cli/src/commands/host.rs:96 zap_socket() makes ZAP-over-unix the CLI's primary local wire with HTTP as the third-party view; operator/src/zapclient.rs, node/hanzo-libs/hanzo-zap, evm/crates/hanzo-zap and platform/pkg/zap are the others. A grep for tonic, prost or grpc across these crates' manifests returns nothing |
| 184 | rust:0132 | partial | cli/crates/event/src/lib.rs:106 posts to {api_base}/v1/event and flushes the buffer as one array (lib.rs:217 flush), which is §1's rule that batching is a shape and not a route. The other Rust telemetry client does not conform: insights-rs/src/endpoints.rs:29-30 still targets /i/v0/e/ and a separate /batch/ against us.i.insights.com — the second endpoint the HIP deletes |
| 185 | rust:0300 | partial | the Rust local server exists and the HIP names it, but the forwarding contract is not implemented: /v1/mcp appears nowhere in mcp/rust, and the hand-rolled cloud surface the HIP deletes is still present at the line count the HIP measured — mcp/rust/src/tools/hanzo_tool.rs is 1,017 lines routing to hanzo.id, kms.hanzo.ai, platform.hanzo.ai and api.hanzo.ai directly (hanzo_tool.rs:5-13), beside cloud_code.rs (510) and cloud_web.rs (203) |
| 186 | rust:0400 | shipped | operator/src/crd.rs:542 ServiceSpec carries the HIP's field table field for field — image, replicas, ports, env, envFrom, volumes, volumeMounts, resources, probes, ingress, autoscaling, pdb, networkPolicy, serviceMonitor, kmsSecrets, sidecars, imagePullSecrets, serviceAccountName, strategy — and the reconciler runs: controllers/service.rs:1064 run_service_controller, registered at operator/src/main.rs:298 |
| 187 | rust:0401 | shipped | operator/src/controllers/datastore.rs:523 run_datastore_controller is the file the HIP cites, registered at operator/src/main.rs:313 and watching the Datastore Kind |
| 188 | rust:0402 | shipped | operator/src/controllers/sql.rs:64 run_sql_controller (main.rs:327) watches the SQL Kind and delegates to datastore::reconcile_datastore_inner_pub with the Postgres engine forced (sql.rs:35), which is what the HIP specifies |
| 189 | rust:0403 | shipped | operator/src/controllers/kv.rs:63 run_kv_controller (main.rs:328) watches the KV Kind and delegates to the datastore reconciler with Valkey forced (kv.rs:35) |
| 190 | rust:0404 | partial | the Kind and its schema are Rust — operator/src/crd.rs:1752 DocDBSpec(pub SQLSpec), installed at operator/src/install.rs:66 — but nothing watches it. The only path that reaches a DocDB workload is an App CR with role: docdb (controllers/app.rs:122), so a `kind: DocDB` CR is never reconciled |
| 191 | rust:0405 | partial | operator/src/crd.rs:1808 S3Spec(pub DBSpec) is declared and installed (install.rs:70). The HIP points at controllers/datastore.rs, but that controller builds Api<DatastoreCR> only (datastore.rs:524) and watches the Datastore Kind. An S3 CR is reachable only via App role: s3 |
| 192 | rust:0408 | partial | operator/src/crd.rs:1769 IAMSpec(pub ServiceSpec) is declared and installed (install.rs:67). The HIP says it reconciles through service.rs, but service.rs:1071 builds Api<ServiceCR> only, so an IAM CR has no watcher |
| 193 | rust:0410 | partial | operator/src/crd.rs:1795 LLMSpec(pub ServiceSpec) is declared and installed (install.rs:69). No controller watches the LLM Kind, and role: llm resolves to the generic Service profile (controllers/app.rs:112) |
| 194 | rust:0411 | shipped | operator/src/controllers/ingress.rs:332 run_ingress_controller is the cited file, registered at operator/src/main.rs:318, and it exposes reconcile_ingress_inner_pub (ingress.rs:47) that the App role dispatch also calls |
| 195 | rust:0418 | partial | operator/src/crd.rs:1858 IndexerKindSpec(pub ServiceSpec) is declared and installed (install.rs:73). The HIP routes it through service.rs, which watches only ServiceCR, so the Indexer Kind is unwatched |
| 196 | rust:0419 | partial | operator/src/crd.rs:1871 ExplorerKindSpec(pub ServiceSpec) is declared and installed (install.rs:74), unwatched for the same reason as HIP-0418 |
| 197 | rust:0510 | shipped | engine/enso/src/lib.rs:25-31 declares the HIP's pieces as modules — guard, learner, linalg, policy, profile, selector, synth — with the featurizer re-exported from hanzo-router so the offline fit and the serving path share one implementation (lib.rs:33-34). profile.rs carries PROFILE_DIM and parse_jsonl, policy.rs the bilinear x-transpose-W-p, selector.rs:113 Selector::select the SLO-feasible constrained argmax, learner.rs fit_base ridge and Bandit LinUCB. 3,035 lines against the RoutePolicy interface hanzo-router owns. The gateway-side pieces — the X-Routed-Model header, POST /v1/add-routing-reward, metering — are not in this crate; the policy is |
| 198 | rust:0901 | partial | engine/hanzo-engine/src/poi.rs:155 freivalds_verify and :168 freivalds_verify_multi are the Freivalds core over F_p with p = 2^61-1, on the exact int8 accumulator, with derive_challenges seeded after the commitment; the activation-trace commitment and challenge binding are poi_transcript.rs (405 lines, keccak MMR, per-opening seed at :190), poi_forward.rs and poi_graph.rs, 1,793 lines in total. Two gaps: the workloadType binding that selects PoE, PoI, PoT or PoC does not exist anywhere in the engine, and poi.rs carries 7 #[test] functions rather than the 14 the HIP claims. The canonical contract and DeltaSoup are Solidity and Python by the HIP's own text |