RunExecution Details
NOT CONNECTED
Awaiting connection
NOT CONNECTED No verification has been requested from this browser yet.

No execution loaded

Execution ID:

Agent
Target
Started
Duration
Cost (observed)
DSG verifies conformance of evidence to the approved plan and policy. It does not certify real-world outcomes beyond the observed evidence. This page shows NOT CONNECTED or PENDING until the API returns a computed result — it never renders a verdict of its own.

Verification summary

Execution timeline

    Nothing has run yet. Connect to a DSG deployment, then start the flow.

    Conformance receipt

    Decision
    Policy version
    Proof generated
    Receipt hash recomputed

    Evidence

    Artifacts
    Content verified
    Hash only
    Coverage

    Hash-only attestations are recorded but never counted as independently verified evidence.

    Cost (observed)

    Recorded on execution
    Metered by DSG

    DSG reports the cost the caller recorded, and the amount its own ledger metered. It does not estimate a breakdown it cannot observe.

    Run definition

    Raw material only: the plan to approve, the actions the agent took, and the evidence it produced. There is nowhere here to assert plan_aligned or verified — the API refuses those fields, and this page has no way to fake them.

    Executions in this session

    This prototype holds no execution list of its own. Rows appear only for runs this browser started against the connected deployment.

      No executions recorded from this browser.

      Look up a proof

      The receipt is returned with DSG's own recomputation of its hash, so an edited receipt is detectable on read.

      Universal MCP Connect

      One endpoint, JSON-RPC 2.0 over POST. The tools mirror the REST flow and enforce the same rule: raw material in, computed verdicts out.

      Endpoint
      Protocol version
      Server
      Tools are listed only after a live tools/list call.

      API contract

      The authoritative contract is openapi/dsg-one-v1.yaml (OpenAPI 3.1) in the repository. The flow below is the order the console drives it in.

        Connect to load the flow the deployment reports.

        Connection

        Served from the same origin as the API, the base URL can stay empty. Served from anywhere else, the deployment's CORS policy has to allow this origin. The key is kept in this browser only and is sent just to the base URL above.

        Service status
        NOT CONNECTED
        Verification backend
        Record store
        Engine
        Verdicts accepted from agent