Files
zeekayandHanzo Dev 30c22bcbd9 voice is a library, not a second service
I gave it a Dockerfile and an image, which mints another thing to build, deploy,
route and operate for one package. api.hanzo.ai is the AI surface and already
serves /v1/audio/*; the realtime socket belongs beside them, reached the one way
everything else is.

The gate stays. This repo had none, its suite opens no database, and a finished
service that nothing compiles on push is how it came to be complete and
unreachable at the same time.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-15 09:30:30 -07:00

20 lines
804 B
YAML

# hanzoai/voice — a spoken conversation over one socket.
#
# A library, not a service. `cmd/voice` runs it alone for development; in
# production hanzoai/ai imports this and mounts /v1/voice, because that is where
# the AI surface already lives and one API host is the whole point of api.hanzo.ai.
# An image here would be a second thing to build, deploy, route and operate for
# one package.
#
# `go test ./...` is the real gate here, unlike the sibling services whose suites
# need a database. Nothing in this tree opens one — the seams (Turn, Mind, Meter)
# are interfaces, and talk_test.go drives them with stand-ins, so the suite is
# hermetic and fast and belongs on every push.
test:
- name: build-vet-test
run: |
set -e
go build ./...
go vet ./...
go test ./...