01 Runtime
Go
Direct HTTP, explicit concurrency, one deployable binary.
Server rendered / selectively alive
Nothing
to hide.
Go runs the server. templ renders the HTML. Tailwind shapes the surface. HTMX adds interaction only where it earns its keep.
The mechanism
Four tools.
One straight line.
A request comes in. Go decides. templ writes HTML. Tailwind styles the result. HTMX can replace one fragment. There is no client-side state empire hiding between the click and the response.
02 Markup
templ
Typed components that compile into ordinary Go.
03 Surface
Tailwind
A build-time styling system, not a runtime dependency.
04 Motion
HTMX
Server-owned interaction without a JavaScript application shell.
The other GOTTH Stack
Deployment without permission theater.
Controller statusAlpha / Active
The plan kernel validates secret-free manifests. The durable journal binds approval and recovery state.
There is deliberately no apply command yet. Platform adapters must prove preflight, verification, rollback, and crash recovery before the controller earns that authority.
Truth before theater
Operational doctrine
Choose the failure you can explain.
Trust 02 / 03
Secrets do not become configuration confetti.
Manifests name secret slots, never secret values. Components receive narrow grants instead of a universal bag of credentials.
Named slots -> revision binding -> least privilege
A smaller stack / a clearer machine