Examples overview

These examples come from the framework’s verification matrix: 11 independent scenarios, each proving one concrete behaviour. The scenario scripts are not published with the framework, so the sub-pages below give the key checks and copyable snippets for reproducing the same properties in your own project.

Shared setup

• Test token: scenarios that pass auth need a JWT. Sign one with your project’s auth — see Getting a dev token.
• Ports: the snippets target :18080 (start your server with GORTEXA_SERVER__ADDR=:18080, or change the port in them); poll /readyz before probing.
• Cleanup: tear down each server you start (trap cleanup EXIT, or docker compose stop for NATS) so every check can be re-run.
• Dependencies: only the two NATS-family scenarios (core and JetStream) need docker; the rest are pure local binaries.

Sub-pages

• Developer flow: the full scaffold loop, one entity across three protocols.
• Security & boundaries: auth rejections leak nothing, secret startup safety, the header allowlist, the reflection gate.
• Contract & resilience: the buf breaking gate, graceful drain on SIGTERM.
• AI & messaging: export tool schemas, NATS/JetStream integration.
• Full example: after go get, wire the public packages into a service with a complete, annotated main.go.

Suggested path

1. Developer flow — walk the full development loop once.
2. See one proto become three protocols.
3. Security & boundaries — the error model and interceptor chain under adversarial input.