Universe is hanzo-inc/universe

The private fleet declarations moved from hanzoai to hanzo-inc; name the
repository where it lives.

Dockerfile

@@ -9,7 +9,7 @@
 #
 # The siblings still reach Cloudflare Pages through their own workflows in
 # .hanzo/workflows/. This is the path they move onto, one host at a time, as each
-# gets a verified App CR in hanzoai/universe (see LLM.md).
+# gets a verified App CR in hanzo-inc/universe (see LLM.md).
 #
 # Built by the platform-native fabric (POST /v1/runner → buildkit Job with this
 # repo as the git context) and deployed as the docs-landing Service CR at

LLM.md

@@ -14,7 +14,7 @@ Fork of [Hanzo Docs](https://github.com/hanzoai/docs) with all packages renamed
       ->  s3://hanzo-sites/hanzo/docs            what docs.hanzo.ai serves
 
 The host is a route, not a workload: `Host(docs.hanzo.ai)` -> Middleware
-`docs-static` -> that S3 prefix, declared in hanzoai/universe
+`docs-static` -> that S3 prefix, declared in hanzo-inc/universe
 `charts/app/values/hanzo/static-sites.yaml`. Nothing is pinned and nothing rolls;
 the publish IS the deploy.
 

RELEASE.md

@@ -12,7 +12,7 @@ serves a second later. There is no image to tag and no pin to move.
       -> hanzoai/ci bin/site                POST /v1/projects/docs-hanzo-ai/deployments
       -> s3://hanzo-sites/hanzo/docs-hanzo-ai   the prefix the docs.hanzo.ai route serves
 
-The route is an `IngressRoute` + `Middleware` pair in hanzoai/universe
+The route is an `IngressRoute` + `Middleware` pair in hanzo-inc/universe
 (`charts/app/values/hanzo/static-sites.yaml`): `Host(docs.hanzo.ai)` ->
 `docs-static` -> `root: s3://hanzo-sites/hanzo/docs-hanzo-ai`. No pod, no
 replicas, no image. A site is files and a route.
@@ -31,7 +31,7 @@ The publish job logs in to KMS with the forge `hanzoai` org's
 `KMS_CLIENT_ID`/`KMS_CLIENT_SECRET` (org-level Actions secrets on git.hanzo.ai,
 holder `hanzo-admin-agent`) and reads `HANZO_DEPLOY_TOKEN` at `/deploy`, env
 `prod`, in KMS org `hanzo`. KMS opens a value only to a holder that
-hanzoai/universe `charts/app/values/hanzo/kms-grants.yaml` grants it, and that
+hanzo-inc/universe `charts/app/values/hanzo/kms-grants.yaml` grants it, and that
 holder is granted `/deploy` only: a read of the flat `/HANZO_DEPLOY_TOKEN`, which
 is what hanzoai/ci `.github/actions/site` does, answers 403 "may not read". No
 secret lives in this repo.
@@ -100,7 +100,7 @@ object store serves it.
 ## The image lane is cold
 
 `ghcr.io/hanzoai/docs`, the root `Dockerfile` and the `docs` app in
-hanzoai/universe are the previous way: an image wrapping the
+hanzo-inc/universe are the previous way: an image wrapping the
 same export, served by hanzoai/static in a pod. The pod still runs and **nothing
 routes to it** — the `docs.hanzo.ai` router names the Sites middleware. Do not
 build or pin it to publish; hanzo.yml no longer declares the image, so no lane

apps/insights-docs/content/docs/getting-started/index.mdx

@@ -38,5 +38,5 @@ Open `http://localhost:8000` to complete setup.
 Deploy to Kubernetes using the Hanzo Universe manifests:
 
 ```bash
-kubectl apply -k github.com/hanzoai/universe/infra/k8s/insights
+kubectl apply -k github.com/hanzo-inc/universe/infra/k8s/insights
 ```

apps/insights-docs/content/docs/self-hosting/index.mdx

@@ -33,7 +33,7 @@ Deploy to Kubernetes using manifests from the Hanzo Universe repo:
 
 ```yaml
 # Apply the full insights stack
-kubectl apply -k https://github.com/hanzoai/universe/infra/k8s/insights
+kubectl apply -k https://github.com/hanzo-inc/universe/infra/k8s/insights
 ```
 
 ## Resource Requirements