Vadyl
Operate & govern

Project scaling

Manual scale, autoscale, load balancing, per-surface topology, vertical resources, and PCG-backed measures as one Runtime Fabric capability.

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

  • Project scaling owns the canonical product-facing contract described here; provider-specific machinery stays behind capability declarations.
  • Manual scale, autoscale, load balancing, per-surface topology, vertical resources, and PCG-backed measures as one Runtime Fabric capability.
  • 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
ProjectRuntimeDescriptorPins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
SnapshotManifestCanonical owner for Project scaling; downstream surfaces derive from this rather than inventing their own truth.
Branching CASCanonical owner for Project scaling; downstream surfaces derive from this rather than inventing their own truth.
EffectiveGovernanceEnvelopeCanonical owner for Project scaling; downstream surfaces derive from this rather than inventing their own truth.
Usage ledgerCanonical owner for Project scaling; downstream surfaces derive from this rather than inventing their own truth.
RuntimeScalingPolicyPins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
RuntimeAutoscalePolicyPins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
RuntimeVerticalResourcePolicyPins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
RuntimeLoadBalancingPolicyPins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
RuntimeGovernanceEnvelopePins Project scaling to a publication, runtime descriptor, worker, or substrate realization.
PlaneCapabilityGraphPlaces Project scaling inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.

Projection coverage

Surface kindsGovernancePolicySurface, BillingMeterSurface, IdentityProviderSurface, AuthSchemeSurface, ObservabilitySurface, ExplainabilitySurface, RuntimeSubstrate
Projection facetsBranches, Publications, Observability, Explainability, Installations, ExposureBindings, PlaneCapabilityGraph, Measures
ProtocolsRest, OpenApi, Sdk, Cli, Dashboard, Mcp
Public projectionsproject APIs; branch APIs; version APIs; identity/auth APIs; usage APIs; explainability APIs; scaling APIs; dashboard scaling controls; CLI runtime-fabric commands; SDK platform.runtimeFabric namespace; automation actions; explainability

Project-scope parity

    Publish, install, consume

      Consumption evidence

        Runtime behavior

        • branch-aware descriptor compilation
        • publication pinning
        • hierarchy inheritance
        • quota reservation
        • observability relay
        • Runtime Fabric compiler
        • capability satisfaction checker
        • runtime-enforced autoscale controller
        • substrate native autoscaler
        • PCG measure resolver

        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
        Projects/api/projects14
        POST create
        GET resolve
        POST {parentProjectId}/children
        GET {projectId}/provider-bindings
        Branch/api/Branch64
        GET branches
        POST branches
        GET branches/{id}
        DELETE branches/{id}
        VersionGovernance/api/version13
        GET /
        GET projects/{projectId}
        GET projects/{projectId}/publication/{publicationVersion:long}
        GET platform-baseline
        IdentityManagement/api/IdentityManagement7
        GET subjects
        GET subjects/{id}
        POST subjects/{id}/deactivate
        GET memberships
        Usage/api/Usage7
        GET {projectId}/events
        GET {projectId}/rollups
        GET {projectId}/quotas
        POST {projectId}/quotas
        Observability/api/Observability8
        GET Entries
        GET Entries/{id}
        GET Trail/{entityName}
        GET Trails
        Explainability/api/Explainability15
        GET surface
        GET project-runtime
        GET publication/latest
        GET publication/{publicationVersion:long}
        RuntimeFabric/api/RuntimeFabric and /api/PlatformRuntimeFabric35
        GET {projectId}/fabric
        GET {projectId}/realization/{projectEnvironmentId}
        GET {projectId}/health/{projectEnvironmentId}
        GET {projectId}/topology
        PlaneCapabilityGraph/api/PlaneCapabilityGraph2
        GET descriptor
        GET nodes/{kind}
        Measure/api/Measure3
        GET descriptors
        GET descriptors/{nodeIdEncoded}
        POST query

        SDK and CLI surface

        ProjectionNamespace / groupCoverage
        SDKbranchingbranches, commits, workspaces, sandboxes, proposals, environments, deploy, rollback. Rendered methods: 5.
        SDKobservabilityaudit, operational, debug, metrics, traces, diagnostics, reason-code correlation. Rendered methods: 4.
        SDKexplainabilityaccess, read-plan, surface, publication, analytics, automation, PCG, measure explanations. Rendered methods: 3.
        SDKplatformprovider health/capabilities, runtime fabric scaling, distribution, version governance, data portability. Rendered methods: 12.
        CLIvadyl projectCreate, suspend, archive, traverse the project hierarchy. Rendered commands: 7.
        CLIvadyl branchManage branches and workspaces for the canonical contract. Rendered commands: 6.
        CLIvadyl publicationProject runtime publications. Rendered commands: 5.
        CLIvadyl deployPlan, apply, ramp, and roll back deployments. Rendered commands: 5.
        CLIvadyl auditTail / search the canonical audit log. Rendered commands: 2.
        CLIvadyl explainProject canonical decision reasoning. Rendered commands: 4.
        CLIvadyl runtime-fabricTopology, scaling, resources, ingress, realization, health, binding, deployment plans, reconcile, drain. Rendered commands: 15.
        CLIvadyl graphInspect PCG descriptors, nodes, edges, actions, triggers, measures, effects, policies, and transforms. Rendered commands: 6.
        CLIvadyl measureMeasure descriptors, units, instruments, freshness, grants, query, and explanation. Rendered commands: 4.

        Input request and output

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

{
  "surface": "project-scaling",
  "publicationVersion": 412,
  "explain": true
}

        Limits and quotas

        • Runtime budgets apply per project, environment, surface, scale group, and cumulative project topology.
        • Autoscale decisions respect cooldown, hysteresis, drain, rollout suspension, and governance ceilings.
        • Manual desired-count changes require runtime.scale grants and idempotency keys for safe retries.

        Error model

        ErrorMeaning
        CAPABILITY_UNSATISFIEDwhen the substrate lacks the requested autoscale strategy, metric, partition mode, load-balancing mode, protocol, or resource class.
        GOVERNANCE_DENIEDwhen ancestor envelopes cap instances, CPU, memory, accelerators, public ingress, sticky sessions, protocols, or custom measure autoscale.
        MEASURE_UNAVAILABLEwhen a custom PCG measure has no compatible live sample source for the target.
        QUOTA_EXCEEDEDwhen cumulative runtime resource budgets or hard usage reservations are exhausted.

        Observability and explainability

        • Scale mutations, autoscale decisions, skipped decisions, cooldowns, stale measures, and governance denials emit typed lifecycle records.
        • PCG measures carry project, environment, surface, scale group, connector, and target dimensions.
        • Explainability reads capability satisfaction reports and autoscale decision records directly from canonical authorities.

        Related references

        Previous
        Full surface atlas
        Next
        Exposure bindings