Getting Support

What to include

1. What you were doing — the task or command.
2. What you expected vs. what happened.
3. Evidence — any on-screen output, error text, or receipt path (the platform writes receipts for actions, e.g. under 06_SESSION_EVIDENCE/logs/...).
4. When it happened.

Self-serve first

• Troubleshooting covers the common cases.
• Restarting a service fixes most "stale/stuck" symptoms safely.

Good to know

• The platform is audit-first: almost everything leaves a receipt, so issues are usually reproducible and explainable.
• Your approvals matter — if something was refused, it likely hit a safety gate (credentials, identity, destructive, or billing actions) that needs your explicit yes.
• Build/support closeout requires the documentation set: SBOM, runbook, developer docs, and end-user docs.

Escalation

For platform-owner escalation, route through the operator/admin with the evidence above. Operators: see the Developer Portal and the runbooks for resolution procedures.