> For the complete documentation index, see [llms.txt](https://dsg-3.gitbook.io/dsg-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dsg-3.gitbook.io/dsg-docs/dsg-one-v1/dsg-one-v1-runtime-and-aimo.md). # DSG ONE V1 — Runtime and AIMO This space documents the governed runtime and deterministic solver path as an evidence-first system. **AWS is the only production authority.** Status claims below are scoped by dated execution evidence. ## Current verified checkpoint — 11 October 2026 | Area | Status | Proof boundary | | ------------------------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Public DSG ONE website | **DEPLOYED / SHA VERIFIED** | [Ship #38154753831](https://github.com/tdealer01-crypto/dsg-one-v1/actions/runs/38154753831) reported `RELEASE_PREFLIGHT=PASS`, `DSG_ONE_ON_HOST_RELEASE=PASS`, and `DSG_ONE_PUBLIC_SERVING=VERIFIED_COMPLETED` for source `81e8bf83caf71d5a6a83990c00414e3e73b8f5b7` | | Public landing, 3D Architecture and Closure Dashboard | **Source merged, production image serving SHA verified** | [PR #202](https://github.com/tdealer01-crypto/dsg-one-v1/pull/202) corrected scope-limited signed read-only acceptance; deploying source alone does not prove every interactive button or browser works | | AWS Spacetime signed read-only Provider v2 | **PASS, scoped** | Real OAuth user principal → governed GitHub public metadata read-only provider → signed Ed25519 execution/evidence. Canonical provider proof and independent verification recorded in [Control Plane Current AWS State](https://dsg-3.gitbook.io/dsg-docs/control-plane/) | | Production Evidence Chain | **VALID, 140 records observed** | Authenticated Spacetime MCP readback on 11 October. A dated count, not continuous telemetry and not new Cinema E2E | | Cinema high-risk signed approval, remote Connect/Execute | **NOT VERIFIED** | Requires separate human Signed Approval, real browser provider readback and signed fresh evidence | | Unity / Quest / software XR governed E2E | **NOT VERIFIED** | Historical Unity build is not integrated Quest/on-device execution proof | | Whole-system DSG ONE autonomous production | **NOT VERIFIED** | Cannot promote the scoped GitHub read-only PASS to full-system PASS | | Public tools authentication and App Builder workspace binding | **DEPLOYED / EXACT SERVING SHA VERIFIED** | [PR #203](https://github.com/tdealer01-crypto/dsg-one-v1/pull/203) source `84f9bebc25f6b4a42c528f9394afa34aeeec09dc` passed source CI, ECR scan and [Ship #38156145497](https://github.com/tdealer01-crypto/dsg-one-v1/actions/runs/38156145497); host release and public serving SHA confirmed at 16:36:42 UTC, 11 October 2026. No cross-user negative live E2E claim. | | Autonomous Level 9/9 claim | **STATIC AUTO-PASS REMOVED / FULL E2E NOT VERIFIED** | PR #203 is deployed and now reports incomplete capabilities instead of 100% from local-only summary. This is a source-based gate verified on an exact production release, not Cinema/Quest E2E completion. | | Access Console scoped OAuth status and HTTP Execute UI | **PR #205 IN REVIEW, NOT DEPLOYED** | [PR #205](https://github.com/tdealer01-crypto/dsg-one-v1/pull/205) separates verified dated signed read-only acceptance from fresh website-session OAuth, disables misleading HTTP Execute/Approve actions and links to real user-bound OAuth; requires CI, merge and new serving SHA before current status changes. | | Auth0 Google connection, user enrollment/allowlist policy | **NOT INDEPENDENTLY VERIFIED** | Code and a real OAuth principal prove authenticated read-only execution, not who may sign up or receive access in the Auth0 tenant. Tenant-side verification still required | | Public Thai landing, login and Adapter Builder improvements | **DRAFT, NOT DEPLOYED** | [PR #201](https://github.com/tdealer01-crypto/dsg-one-v1/pull/201) remains a distinct draft. Do not confuse its UI preview with the currently serving home page | ### Execution authority Authenticated user → exact Plan and approval policy → governed Provider → execution receipt → signed evidence → independent verifier. A browser-supplied `approved=true`, workspace header, or a metadata/health probe is **not** authorization. The low-risk GitHub read-only proof is already completed; do not repeat it merely to test unrelated Cinema/Quest gaps. ## Historical checkpoint — 2 October 2026 (superseded) The following values are retained **only as dated historical source and image identities**; they must not be presented as currently serving: * AWS host: EC2 `i-01a2ee90890a558c3`. * DSG ONE source/image then: `ea70fbecdde020b0a4d4e44180798418af209f27` / `sha256:2b79455abf1a4d8b29abccb384e55fe83f82d8b44a117fe86133a7024dfa06ad`. * Then-observed endpoint: `GET /api/agent/status` HTTP 200; Microsoft Agent Framework `1.18.0`. * Historical Spacetime image: `sha256:5087dcc08956e0618036aa7889f9dbb875f74dfcca661b1b354249b153099e35`. * Historical Cinema image: `sha256:b876f7bb86a8eb86a4c732a07a706c217993092da4054bc1fac205c4ca78b3c3`. * The historical `PENDING_REVERIFY` entry preceded the separately completed signed read-only OAuth→GitHub proof. ## Start here 1. Read [DSG ONE Canonical Architecture — Separation of Authority](/dsg-docs/dsg-one-v1/dsg-one-canonical-architecture-separation-of-authority.md) for the cross-system trust model. 2. Read [Current AWS State](https://dsg-3.gitbook.io/dsg-docs/control-plane/) for source-bound production and scope-limited provider acceptance. 3. Use the AIMO Harness page for deterministic solver verification obligations, and the Runtime Build Plan for responsibility boundaries. 4. Treat older non-AWS deployment pages as historical only unless tied to newer serving evidence. ## Canonical execution rule An exact, immutable plan proceeds only with verified user authority, applicable policy and required approvals. Missing capabilities or credentials must stay `WAITING_PERMISSION` or `BLOCKED`, not silently pass. Different actions require a fresh policy decision. Privileged API handlers verify session and workspace membership **server-side**; the frontend and middleware shape checks are not substitutes. ## Truth boundary * Build/CI PASS and public serving SHA PASS do not establish per-feature, browser, paid transaction, or whole-system E2E acceptance. * Historical evidence, source constants and local summaries are not live signed execution receipts. * AIMO solver output remains candidate evidence until the downstream verifier establishes proof obligations. * The signed GitHub **read-only** route can be marked scoped PASS, but Cinema Connect/Execute and Quest remain separate gates. * A receipt is not an independent certification or regulatory approval.