rail-knative/docs/runtime-contract.md

597 B

Knative Runtime Contract

The rail owns:

  • authenticated-entry integration points
  • request activation and bounded buffering
  • scale-to-zero and optional temporary minimum scale
  • revisions, concurrency, autoscaling, and traffic splitting
  • cold-start readiness and revision rollback

It inherits workload identity, criticality, dependencies, health, evidence, promotion vocabulary, and recovery requirements from rail-kubernetes 1.0.0.

Production values for timeouts, concurrency, and scaling are workload bindings backed by measured evidence; the rail must not invent one universal value.