1DSG ONE
DSG ONE / SUPPORT

Governed systems deserve traceable support.

Support for DSG Spacetime, governed execution, MCP connectivity, proposal-only agent repair, evidence verification, and production access. We troubleshoot from verifiable run context rather than asking you to expose secrets.

UPDATED · 15 SEP 2026PUBLIC SUPPORTNO SECRETS IN TICKETS
WHAT TO INCLUDE

Useful diagnostic context

  • Approximate request time and timezone.
  • Tool, route, or workflow name.
  • Decision such as ALLOW, BLOCK, or WAITING_PERMISSION.
  • Non-secret plan, execution, evidence, or receipt identifier when available.
  • Expected outcome versus observed outcome.
DO NOT SEND

Keep credentials out of support

Do not email passwords, API keys, bearer tokens, private keys, MFA codes, passkeys, recovery codes, or full secret values. DSG ONE is designed to use bounded references and evidence identifiers instead.

Security issue? Put “Security” in the subject and provide a reproducible description without live credentials.
FAST CHECKS

Before opening a ticket

  1. Confirm the production MCP endpoint is reachable over HTTPS.
  2. Confirm OAuth targets the declared DSG Spacetime resource.
  3. Check whether the action is inside the approved plan and route.
  4. For a BLOCK, inspect the explicit remediation or missing capability instead of retrying blindly.
  5. For repair.synthesize, remember that the Agent returns a proposal only; Repair Kernel verification and Spacetime authorization still control execution.
PRODUCT BOUNDARY

Support does not override governance

Support can explain a failure or help repair configuration. It does not convert missing authority, unsupported claims, repair proposals, or out-of-plan actions into an ALLOW decision. DSG-Agent-v0 repair synthesis is proposal-only; deterministic Repair Kernel checks and Spacetime production gates remain authoritative.