> 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/cinema-proof-agent/readme.md).

# DSG Cinema Proof Agent

Current Cinema/BrowserOS production role, AWS runtime evidence, customer flow, and evidence-first operating model.

* **Canonical product domain:** <https://www.dsg.pics>
* **Customer Workroom entry:** <https://dsg.pics/dsg/workroom>
* **Production MCP edge:** <https://aws.dsg.pics/mcp>

DSG Cinema is the verification, evidence, replay, and BrowserOS execution surface used under DSG Spacetime governance. It is not an independent approval authority.

Authentication proves who is calling. Exact plan/payload binding, permission, required approval, provider capability, execution evidence, and verification determine what may proceed.

### Current AWS runtime — 2 October 2026

| Item            | Verified state                                                            |
| --------------- | ------------------------------------------------------------------------- |
| Host            | EC2 `i-01a2ee90890a558c3`                                                 |
| Container       | `aws-cinema-1` running / healthy                                          |
| Registry image  | `sha256:b876f7bb86a8eb86a4c732a07a706c217993092da4054bc1fac205c4ca78b3c3` |
| Internal health | `GET http://127.0.0.1:8000/health` → HTTP 200                             |
| Health body     | `{"status":"ready","backend":"ready"}`                                    |

The old Azure Container Apps dashboard and Z3 URLs are historical evidence. They must not be presented as the current production base.

### Customer flow

```
Open DSG Workroom
      ↓
Authenticate
      ↓
Select workspace / connect governed Agent
      ↓
Agent proposes exact action/plan
      ↓
Spacetime checks route + plan + payload + permission + approval
      ↓
Cinema / BrowserOS executes or verifies authorized work
      ↓
Evidence + replay + audit
      ↓
Result returns to DSG ONE / Core Spin
```

### Operator views

The user should be able to answer:

1. **ACTION** — what is being attempted?
2. **PLAN ALIGNMENT** — does it match the approved plan?
3. **PERMISSION** — is authority/capability available?
4. **EVIDENCE** — what proves the result?
5. **EXECUTION / AUDIT** — what actually happened and what was recorded?

The UI must not manufacture a green state. Unknown runtime state remains open, pending, blocked, failed, or unverified.

### Decision semantics

| State                | Meaning                                                                                |
| -------------------- | -------------------------------------------------------------------------------------- |
| `ALLOW`              | Exact governed action is authorized and required capability is ready.                  |
| `WAITING_PERMISSION` | Action remains within the plan but a required capability/credential/tool is not ready. |
| `BLOCK`              | Action is outside the approved boundary or binding does not match.                     |

### Current acceptance boundary

* Cinema runtime health: PASS.
* Cinema↔Spacetime governed integration has historical and current scoped proofs.
* BrowserOS/remote execution remains governed by Spacetime.
* Governed RDC production acceptance is PASS in run `36991572295`.
* Authenticated BrowserOS/Cinema user E2E remains OPEN.
* Promoted-source XR state smoke remains OPEN.
* Whole-system release remains `PENDING_REVERIFY` until the outstanding promoted-source closeout gates pass.

### Historical Azure evidence

Earlier Azure rolling-revision pairing, native Z3, replay, and MCP proofs remain valid for their dated source/revision only. They are retained for audit history and must not be used as present-tense production URLs.