1DSG ONE
DSG ONE / OPERATOR GUIDE

One place to use Dashboard, Desktop, CLI and Remote.

Start from the surface that matches the job. Every path keeps proposal, authority, execution and evidence separate. This guide names only commands and capabilities verified in the current source.

DashboardDesktop / WorkroomCLIRemote BrowserRemote DesktopMCPEvidence
PRODUCTION RELEASE · VERIFIED 24 SEP 2026 · ASIA/BANGKOK

Spacetime production E2E passed.

The current governed route release completed CI, signed build submission, immutable image resolution, Azure deployment, repair, canonical state and local production E2E proof.

Source8170d032c45b8092df16634c21b56d90c5d0e9fa
Image digestsha256:cbbf2a237ac8056f12eb88be1c655ec83c24a894c87155c06e82f8254059908f
Serving revisiondsg-spacetime-prod--0000062
Exact-main CI35894442670 · SUCCESS
Route build35895388763 · SUCCESS · ACR ds4t
Production E2E35895881862 · attempt 2 · SUCCESS
Proof line: repair → canonical → done, followed by DSG_SPACETIME_AGENT_ROUTE_GATED_DEPLOY=PASS and LOCAL_PRODUCTION_E2E_PROOF=PASS. This is production execution evidence for this exact release, not a SOC 2/ISO or independent-audit claim.
01 · DASHBOARD / ACCESS HUB

Use this first when you want the system to do the work.

Best for owner/operator use without memorizing commands.

How to use

  1. Open Unified Access Hub.
  2. Sign in, then verify operator access.
  3. Use Pair & open Workroom when Workroom needs a short-lived pairing.
  4. Type one bounded goal into DSG-Agent-v0 Chat.
  5. If the runtime returns WAITING_APPROVAL, review the exact staged action and approve only that request.
  6. Read the final execution state and evidence panel; BLOCK and WAITING_PERMISSION stay visible instead of becoming success.
Look here: Execution state → Plan → Permission → Execution → Evidence.
02 · DESKTOP / WORKROOM

Persistent operator workspace.

Workroom is the native AI operator surface. Access Hub can issue a five-minute, single-use pairing code without exposing the master access key.

What you get

Durable job state, planning, exact-request approval, resumable WAITING_PERMISSION checkpoints, execution and evidence without reading server logs.

Boundary

Desktop visibility is not execution authority. Provider actions remain bound to the approved Spacetime plan, route, permission and evidence contract.

03 · CLI / DSG SPACETIME

The installed runtime command is dsg-spacetime.

The current private runtime registers dsg-spacetime as its CLI entry point. The older public “dsgctl” label is not used here as a command because it is not the registered executable in the verified source.

Readiness first

dsg-spacetime doctor --config <config.json> --entitlement <entitlement.json> --evidence <evidence-dir>

Doctor verifies installed runtime readiness without executing external adapter actions. A successful human-readable result ends with DSG Spacetime: READY.

Serve MCP over stdio

dsg-spacetime serve-mcp --config <config.json> --entitlement <entitlement.json> --evidence <evidence-dir>

Serve MCP over HTTP

dsg-spacetime serve-mcp-http --config <config.json> --entitlement <entitlement.json> --evidence <evidence-dir> --host 127.0.0.1 --port 8787

Open the local console

dsg-spacetime serve-console --config <config.json> --entitlement <entitlement.json> --evidence <evidence-dir> --host 127.0.0.1 --port 8765
Secrets: keep API keys, private keys, OTP/MFA, passwords and recovery data out of command history, prompts and evidence. Use environment variables or the approved secret store.
04 · REMOTE BROWSER / DSG CINEMA

Canonical shared-browser path.

Human / Agent / CLI → DSG Cinema governance → account-scoped Azure Chromium → Evidence. The official interactive CLI is dsg-browser.

Install and inspect

bash scripts/install_dsg_browser.sh dsg-browser --help dsg-browser status dsg-browser view --open

Connect under an approved plan

dsg-browser connect --plan-id plan_... --step-id browser-step --agent-identity agent-name

Common bounded actions

dsg-browser extract dsg-browser navigate 'https://example.com' dsg-browser click 'button[type=submit]' dsg-browser type 'input[name=name]' 'value' dsg-browser select 'select[name=role]' 'developer' dsg-browser screenshot dsg-browser disconnect

Uploads use approved artifact:// references. Downloads are quarantined and never auto-executed. Payment, destructive deletion, credential/permission changes and expanded high-risk scope require re-approval.

05 · REMOTE DESKTOP COMMANDER

Device execution is a provider under Spacetime, not a second policy engine.

The caller cannot override the bound device identity. Write and shell routes are high risk and retain the Spacetime approval requirement.

CapabilityRouteUse
device.remote.statusroute.rdc-remote.statusVerify the live device/session.
device.fs.readroute.rdc-remote.fs-readRead bounded files.
device.fs.writeroute.rdc-remote.fs-writeHigh risk · approval required.
device.process.listroute.rdc-remote.process-listInspect processes.
device.shell.execroute.rdc-remote.shell-execHigh risk · approval required.

The Spacetime RDC node is executable only when its production provider bindings exist and a live device/session is verified. A direct ChatGPT RDC connection does not automatically prove the production Spacetime RDC route is bound.

06 · MCP / CONTROLLER

Discover → compose → execute → evidence.

Spacetime exposes capability routes while preserving plan, entitlement, approval, payload binding and evidence gates.

1 · Discover

Resolve available nodes/routes and read whether a route requires exact payload binding at compose time.

2 · Compose

Bind the exact target route and, for bind_payload=true, the same payload that execution will later use.

3 · Execute + verify

Execute only after policy/approval gates pass; successful provider results continue into the evidence hash chain.

Optional browser MCP providers

npx @playwright/mcp@latest --port 8931 export DSG_PLAYWRIGHT_MCP_URL=http://127.0.0.1:8931/mcp
mcp-proxy --transport streamablehttp --port 8080 -- npx -y chrome-devtools-mcp@latest export DSG_CHROME_DEVTOOLS_MCP_URL=http://127.0.0.1:8080/mcp

These are optional executor routes. Source integration alone does not prove a live provider; bind a real endpoint and pass live status/read/execute smoke before claiming readiness.

07 · RESULT / EVIDENCE

Know where to look and what the status means.

StatusMeaningNext action
ALLOW / COMPLETEDThe exact governed path has the required authority and execution result for its scope.Inspect evidence/receipt and preserve bound hashes.
WAITING_APPROVALAn exact staged action needs human approval.Review, then approve or cancel that request.
WAITING_PERMISSIONThe work remains in plan, but a permission/capability is missing.Bind the permission, then resume from checkpoint.
BLOCKPolicy, scope, proof, authority or safety condition is not satisfied.Read the named cause; do not retry blindly.

Current production proof: exact-main CI → signed route build → ACR digest → revision 0000062 → repair → canonical → done → LOCAL_PRODUCTION_E2E_PROOF=PASS.

TRUTH BOUNDARY

Verified execution is not certification.

DSG ONE reports what its exact source, provider readback and execution evidence prove. It does not convert CI, deployment, a mathematical Z3 proof or a production E2E run into SOC 2, ISO, legal certification, marketplace approval or an independent audit.

Open Access HubArchitectureSupport