1DSG ONE
START HERE · VERIFIED 31 OCT 2026

เริ่มงานจากหน้าเดียว แล้วปล่อย Safe Autonomy เดินงานที่อนุญาต

เริ่มที่ Access Hub หรือ Control Hub: Sign in → ตรวจ Operator/Bridge → ส่ง Goal → Agent v0 เสนอ action → Spacetime ตรวจ policy → อนุมัติเฉพาะเมื่อจำเป็น → Provider ทำงาน → Evidence ยืนยันผล. ไม่ต้องเลือก Provider เอง

Fresh production verification วันที่ 31 ต.ค. 2026 พิสูจน์ route.agent.dsg-v0.plan = ALLOW ด้วย nvidia/nemotron-3.5-lightning-30b-a3b, proposal-only authority, Action Kernel Z3 → Ising/QUBO → Z3 และ evidence chain valid หลัง append. ระดับ Full Autonomy ยังไม่ผ่าน: runtime รายงาน PARTIAL 1/9; Safe Autonomy จึงทำต่อเองเฉพาะ low-risk/read-only และหยุดเมื่อเจอ Approval/MFA/signed permit/ค่าใช้จ่าย/mutation.

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.

CLOUD COMPUTER · START HERE

เริ่มจากหน้าเดียว ลดการสลับระบบ

เปิด DSG ONE Cloud Computer แล้วทำตามลำดับ Continue with Google → เชื่อม DSG ครั้งแรก → ตรวจ Native machine 2. ถ้าเคยเชื่อมแล้ว ให้กดตรวจ Native ได้ทันที

Machine 1Cinema Browser
Machine 2Linux Native + Chrome Remote Desktop
Agent commandPlan + Signed Permit + Approval
ผลลัพธ์Job timeline + Evidence

งาน low-risk/read-only ที่อยู่ในแผนสามารถทำต่ออัตโนมัติด้วย Safe Autonomy; ถ้าเป็น WAITING_APPROVAL ให้เปิดคำขอเดิม อนุมัติ แล้วทำต่อจาก job เดิม ห้ามสร้างงานซ้ำเมื่อ OUTCOME_UNKNOWN และห้าม bypass Gate

AWS PUBLIC MCP · VERIFIED 29 SEP 2026 · ASIA/BANGKOK

Private Runtime is the production source-of-truth.

The canonical continuity docs now record the AWS public governed MCP checkpoint. Repository documentation, serving backend identity, and the installed ChatGPT client binding are tracked separately so a client session failure cannot be misreported as a backend failure.

Production repositorytdealer01-crypto/DSG-Private-Production-Runtime
Repository main07ad14724f0a8ca33dc1979a9f2913e7d004da63
Main CI36534873806 · SUCCESS
AWS serving repair source5c8f75c167af9f019f31611597eea0b425fd7900
DSG ONE runtime sourceea70fbecdde020b0a4d4e44180798418af209f27
DSG ONE image digestsha256:2b79455abf1a4d8b29abccb384e55fe83f82d8b44a117fe86133a7024dfa06ad
AWS governed activation36529273403 · SUCCESS
Public governed MCP E2E36529526202 · SUCCESS
Proof boundary: public MCP E2E proves OAuth metadata, fail-closed unauthenticated MCP, protocol/tool discovery, a read-only Cinema status ALLOW with valid evidence, and an unapproved Cinema connect BLOCK. It does not prove an approved browser mutation, the separate candidate.select/Agent-v0 lane, certification, or the installed ChatGPT connector session. The public DSG-Spacetime-Source repository remains a fixed public verification target, not production source.
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

AWS-native governed operator workspace.

Workroom is served from DSG ONE on AWS. Website authentication and a verified workspace are required before Chat or Command Center surfaces become available.

Start

Open the AWS Workroom, sign in, then select the governed workspace. Legacy AppDeploy bridge pairing remains a separate compatibility path.

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 Spacetime governance → BrowserOS + Cinema → Evidence. The current AWS acceptance proves read-only status and the no-approval connect BLOCK; approved connect/execute remains separately gated. 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 · CHATGPT WORK / PERSONAL PLUGIN

Run the real DSG Spacetime plugin in chat.

Use a ChatGPT Work conversation with the installed personal plugin. A terminal run alone does not show the reviewer experience.

Connect and test

  1. In ChatGPT web, enable Developer mode under Settings → Security and login.
  2. In Plugins, add the personal MCP endpoint https://aws.dsg.pics/mcp, complete OAuth, and enable DSG Spacetime.
  3. Switch to Work, start a new chat, and select the plugin with @DSG Spacetime.
  4. Ask: Read public repository metadata for tdealer01-crypto/DSG-Spacetime-Source using repo.metadata.read. Discover, compose a bound plan, execute, verify evidence, and report the returned full_name.
  5. Ask for a different repository under the same plan. Treat a mismatched full_name as a failed task even when governance reports ALLOW. Then ask which actions passed, which were blocked, and where the evidence is.
Current scope (29 Sep 2026): the AWS backend at https://aws.dsg.pics/mcp is externally verified, but the already-installed ChatGPT DSG Spacetime connector still returns UNAVAILABLE until OAuth/session binding is refreshed. After re-link, repeat discover → compose → read-only execute → verify evidence → negative approval BLOCK from ChatGPT itself. Never treat backend PASS as proof that the current ChatGPT client session is connected.

ChatGPT plugin quickstart · Submission requirements

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: continuity main 07ad1472… has exact-main CI 36534873806 SUCCESS. The serving AWS backend repair source 5c8f75c… passed governed activation 36529273403 and public MCP E2E 36529526202. That verifier proved protocol 2025-06-18, 8 required tools, route.cinema-remote.status → ALLOW, evidence valid=true with records 9→10, and route.cinema-remote.connect → BLOCK / APPROVAL_REQUIRED without an evidence increment. Installed ChatGPT connector binding remains separate and currently requires re-link.

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.