Vadyl
Product logic

Authored runtime

Seven canonical execution surfaces. Language-neutral runtime bridge. Capability-bounded by construction.

This page is the documentation contract for the Authored runtime surface in Vadyl's final form. It is not a marketing summary: it names the authorities, projections, runtime behavior, examples, limits, errors, and observability expectations that every product implementation must honor.

What this surface owns

  • Authored runtime owns the canonical product-facing contract described here; provider-specific machinery stays behind capability declarations.
  • Seven canonical execution surfaces. Language-neutral runtime bridge. Capability-bounded by construction.
  • The final docs treat this as complete: REST, GraphQL, gRPC, SDK, CLI, MCP, dashboard, observability, limits, errors, and explainability are all covered as projections of one authority.

Canonical authorities

AuthorityRole
ExecutionSurfaceKindCanonical owner for Authored runtime; downstream surfaces derive from this rather than inventing their own truth.
AuthoredPublicationServiceCanonical owner for Authored runtime; downstream surfaces derive from this rather than inventing their own truth.
IAuthoredExecutionCoordinatorCanonical owner for Authored runtime; downstream surfaces derive from this rather than inventing their own truth.
RuntimeBridgePins Authored runtime to a publication, runtime descriptor, worker, or substrate realization.

Projection coverage

Surface kindsAuthoredRuntimeSurface, WorkflowSurface, SchedulingHandlerSurface, SourceAssetSurface, GovernedConnectionAdapter
Projection facetsHandlers, Workflows, RuntimeUnits, SourceAssets, Connections, ExposureBindings
ProtocolsRest, Sdk, Cli, Mcp, Event
Public projectionsauthored runtime APIs; workflow APIs; source asset APIs; runtime SDK; workspace IDE; CLI build/source/connection/workflow

Project-scope parity

    Publish, install, consume

      Consumption evidence

        Runtime behavior

        • TypeScript worker
        • durable workflow orchestrator
        • bridge capability enforcer
        • publication-pinned invocation

        REST and controller surface

        Code-backed controllers are listed here so the docs menu does not hide the real endpoint surface. The complete route-by-route table remains in the REST controller atlas.

        ControllerBase routeEndpoint countExamples
        AuthoredRuntime/api/AuthoredRuntime5
        POST validate
        POST preview-build
        POST publish
        POST sandbox/{sandboxId}/publish
        AuthoredWorkflow/api/AuthoredWorkflow6
        POST {workflowName}/start
        POST {instanceId}/signal/{signalName}
        GET {instanceId}
        POST {instanceId}/cancel
        RuntimeUnit/api/RuntimeUnit8
        GET /
        GET {id}
        POST /
        PUT {id}
        SourceAsset/api/SourceAsset16
        GET folder
        POST folder
        PUT folder/{id}/rename
        DELETE folder/{id}
        Connection/api/Connection6
        POST /
        GET /
        GET {id}
        GET by-name/{name}
        AuthoredRuntimeAdmin/api/AuthoredRuntime1
        POST workers/reset
        AuthoredManagement/api/AuthoredManagement1
        POST {handlerName}
        ExecutionCapabilityMatrix/api/ExecutionCapabilityMatrix1
        GET matrix

        SDK and CLI surface

        ProjectionNamespace / groupCoverage
        SDKauthoredRuntimevalidate, previewBuild, publish, invoke, runtime units, workflows, execution sessions. Rendered methods: 6.
        SDKconnectionsgoverned connection CRUD, operation invocation, diagnostics, secrets, egress. Rendered methods: 1.
        SDKeventsemit, list, get, tail, replay, consumer offsets, ordered stream helpers. Rendered methods: 2.
        CLIvadyl buildHermetic builds for authored runtime artifacts. Rendered commands: 3.
        CLIvadyl sourceFolders, files, blobs, trees, upload/download, and scope shape. Rendered commands: 11.
        CLIvadyl connectionManage governed connections. Rendered commands: 7.
        CLIvadyl workflowStart, signal, query, replay durable workflows. Rendered commands: 7.

        Input request and output

        POST /api/AuthoredRuntime/validate HTTP/1.1
Host: api.vadyl.app
Authorization: Bearer $VADYL_TOKEN
X-Vadyl-Tenant: acme
X-Vadyl-Project: billing
Content-Type: application/json

{
  "surface": "authored-runtime",
  "publicationVersion": 412,
  "explain": true
}

        Limits and quotas

          Error model

          ErrorMeaning

          Observability and explainability

            Related references

            Previous
            Full surface atlas
            Next
            Exposure bindings