Go Quick Start
The shared School verification
is WORKSPACE PASS — RELEASE PENDING for Go. The verified runtime source
implements the two internal-ID methods missing from selected public v0.3.1.
Its generated application passes SQLite and restart checks; the published-only
build failure remains recorded until the release is aligned.
The Go runtime is published as a module.
Its newest tag and the deployed generator's selection can differ; see
Latest Versions. Use the generated go.mod
for the first published-consumer verification. For the pending-release source
check, use the School runner's explicit
--go-runtime option,
which records the selected checkout separately from the published dependency.
Before you start
Complete Prepare the Client and Starter Model
first. You need the Cargo-based TeaQL client, your language toolchain, and the
school model saved as models/main.xml. Run the commands below from that
project root. The shared setup explains why cargo teaql is used for every
language.
Generate the library and application
go version
cargo teaql services
cargo teaql evaluate --input models/
cargo teaql golang-lib-core --input models/ --output generated/golang-lib-core
cargo teaql golang-app-console --input models/ --output generated/golang-app-console
Read the generated application AGENTS.md, then run go test ./... and
the executable from the generated workspace. The current service catalog uses
golang as the CLI key, not go. For exact Q, E, mutation and field methods,
use scoped Assist rather than reading generated library source:
cargo teaql golang-assist-query/school --input models/
cargo teaql golang-assist-query/school.name --input models/
cargo teaql golang-assist-ensure-schema --input models/
Install the generated Runtime Module and explicitly ensure schema through the
trusted, context-aware module entry point. Verify root and constant rows on
first and repeated startup, then create a child with audit intent, query it
with non-empty comment and purpose, evaluate a loaded E path, and test
Checker/Fix plus an audited update. Do not substitute a descriptor-array schema
call or hand-written SQL seed for this path.
For runtime development, the owning Go example should use local repository source. To claim a published package works, repeat the model in a clean consumer workspace using an exact released version. See Go First Verification.
Learn through an Order
Follow the Order tutorial for the retained SQLite example: startup, complete reads, an audited quantity/total edit, bounded pages and expected results. Use the Order API usage guide for result shapes and the native troubleshooting table for recovery. The coverage matrix keeps remaining writing and clean-machine packaging gaps visible. Existing runtime pending-release and generator-deployment qualifications remain in place.