mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-24 20:09:02 +00:00
zeekay
699b060a04
The data products are Hanzo SQL, Hanzo SQLite, Hanzo DocDB and Hanzo Datastore. Customer-facing prose named the upstream engine instead, which reads as a resale rather than a product — and reads that way beside pages that already say Datastore for the columnar store. Fifteen lines of prose across base, insights, tasks and platform, plus the three repo descriptions the project pages are generated from, so the next sync of orm and sql-vector is a no-op rather than a revert. Measured over the hand-authored surface: 77 lines matched `postgres`, now 63. Every one of the 63 is a literal that breaks if renamed, and each was read before it was left — connection-string schemes, POSTGRES_* names, mount paths, Temporal's postgres12 driver value, image references, a compose service name and the k8s Service DNS that must agree with it, the postgresConnectionRef CRD field, the mcp-server-postgres package, the pg_isready role, and an integration catalog of third-party software. The rendered export shows both halves: platform prints `sql-prod-data` and still prints `postgres://`, `postgres:17-alpine` and `pg_isready -U postgres` byte for byte. openapi-specs/public.yaml holds five more and is not editable here. It is a sha256-pinned snapshot of cloud's contract, and that prose has one home — the handler doc comment that also becomes the SDK docstring, the MCP tool description and the CLI help.