When You're Stuck — Operator training

Some problems survive every table in this section. When yours does, what decides how fast it gets fixed is the evidence you arrive with:

The exact refusal, not a paraphrase — the full error envelope, including the stable GOCA-E… id and code.
The request id — X-Request-Id correlates your report with the server's own log line about that exact request.
The version and shape — goca version, and whether you run all-in-one, distributed, or standalone.
The error stream — GET /v1/logs?level=error, and full stdout from docker compose logs for the affected service.
Board state — what Status → Components shows, and the current audit/verify verdict. These two rule out whole categories before anyone asks.

Roadmap. The manual describes a redacted, signed support-bundle command; that tooling is designed and not built today. Until it lands, the list above is the bundle — gathered by hand.

Then bring it to us: the support page has the AI assistant, which has read this entire manual — and will say so when the honest answer is "that isn't built yet" — plus the ticket form for everything the assistant cannot resolve.

Now I can arrive at support with the evidence that shortens the fix.