The railiance operations rail for dynamic knative workloads.
Find a file
custodian-sync 69892bed5f chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-07-27:
  - update .custodian-brief.md for rail-knative
2026-07-27 00:52:18 +02:00
declarations Promote derived rail to verified 2026-07-26 20:16:31 +02:00
docs Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
examples Add generic Knative service contract 2026-07-26 14:14:26 +02:00
tests Ignore generated Python test artifacts 2026-07-26 14:15:01 +02:00
workplans Promote derived rail to verified 2026-07-26 20:16:31 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-27 00:52:18 +02:00
.gitignore Ignore generated Python test artifacts 2026-07-26 14:15:01 +02:00
.repo-classification.yaml Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
AGENTS.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
CLAUDE.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
INTENT.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
LICENSE Initial commit 2026-07-26 08:58:28 +00:00
README.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
SCOPE.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
WORK-RECORDS.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00

rail-knative

Derived Railiance execution rail for Knative Serving workloads.

This rail inherits the versioned rail-kubernetes common workload contract and owns only Knative-specific activation, scale-to-zero, revision, traffic, cold-start, and rollback semantics.

The repo is currently at declared readiness. It does not claim that Knative is installed or production-approved on any reef.