Vadyl
Capability surfaces (UCSA)

Storage

Multi-provider. Signed URLs. Multi-part upload. Capability declaration in 14 sub-interfaces.

This page is the documentation contract for the Storage 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

  • Storage owns the canonical product-facing contract described here; provider-specific machinery stays behind capability declarations.
  • Multi-provider. Signed URLs. Multi-part upload. Capability declaration in 14 sub-interfaces.
  • 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
CapabilitySurfaceKindPlaces Storage inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.
CapabilityImplementationDescriptorPlaces Storage inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.
CapabilityDeclarationPlaces Storage inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.
CapabilityBindingRegistryPlaces Storage inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.

Projection coverage

Surface kindsGovernedConnectionAdapter, DatabaseInfrastructure, RuntimeSubstrate, Distribution, AnalyticsSubstrate, StorageInfrastructure, CacheInfrastructure
Projection facetsExposureBindings, Analytics, Storage, Connections, RuntimeUnits
ProtocolsRest, OpenApi, Sdk, Cli, Dashboard
Public projectionsprovider binding APIs; connector APIs; SDK platform namespace; CLI connector/runtime/distribution/storage commands

Project-scope parity

    Publish, install, consume

      Consumption evidence

        Runtime behavior

        • capability router
        • implementation registry
        • binding compiler
        • conformance runner
        • consumption emitter

        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
        Connector/api/Connector9
        GET contracts
        GET contracts/{kind}/{majorVersion:int}
        GET implementations
        GET implementations/{implementationId}
        DatabaseConnector/api/DatabaseConnector9
        GET /
        GET {alias}
        POST /
        PUT {alias}
        RuntimeFabric/api/RuntimeFabric and /api/PlatformRuntimeFabric35
        GET {projectId}/fabric
        GET {projectId}/realization/{projectEnvironmentId}
        GET {projectId}/health/{projectEnvironmentId}
        GET {projectId}/topology
        Distribution/api/Distribution17
        GET projects/{projectId}/bindings
        POST projects/{projectId}/bindings
        DELETE projects/{projectId}/bindings/{bindingId}
        GET projects/{projectId}/policy
        Analytics/api/Analytics45
        GET catalog
        GET catalog/subjects/{subjectId}
        GET catalog/dimensions
        GET catalog/measures
        Storage/api/Storage7
        POST upload
        GET download/{**storagePath}
        HEAD exists/{**storagePath}
        DELETE {**storagePath}
        CacheProviderBinding/api/CacheProviderBinding6
        GET /
        GET {id}
        POST /
        PUT {id}

        SDK and CLI surface

        ProjectionNamespace / groupCoverage
        SDKplatformprovider health/capabilities, runtime fabric scaling, distribution, version governance, data portability. Rendered methods: 12.
        SDKstorageupload, download, stream, exists, delete, list, presign, copy, move, metadata. Rendered methods: 6.
        SDKanalyticscatalog, query validate/explain/execute, models, metrics, reports, dashboards, materializations. Rendered methods: 6.
        SDKconnectionsgoverned connection CRUD, operation invocation, diagnostics, secrets, egress. Rendered methods: 1.
        CLIvadyl connectorContracts, implementations, bindings, builds, conformance, invocation. Rendered commands: 6.
        CLIvadyl runtime-fabricTopology, scaling, resources, ingress, realization, health, binding, deployment plans, reconcile, drain. Rendered commands: 15.
        CLIvadyl distributionCDN bindings, policy, realization, delivery, invalidation, replica policies. Rendered commands: 6.
        CLIvadyl storageObject upload, download, list, metadata, presign, delete. Rendered commands: 7.
        CLIvadyl analyticsCatalog, query, models, metrics, reports, dashboards, materializations. Rendered commands: 10.

        Input request and output

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

{
  "surface": "storage",
  "publicationVersion": 412,
  "explain": true
}

        Limits and quotas

          Error model

          ErrorMeaning

          Observability and explainability

            Related references

            Previous
            Full surface atlas
            Next
            Exposure bindings