Close Knative CPU request handoff with installer evidence

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e396-d089-7653-b0a1-734cac532913
This commit is contained in:
tegwick 2026-09-27 18:01:25 +02:00
parent 8caf491854
commit cd38dba365
4 changed files with 43 additions and 21 deletions

View file

@ -6,5 +6,9 @@ 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.
The [declaration](declarations/rail.yaml) records `verified` readiness, backed by
the [2026-07-26 lifecycle evidence](../reef-railiance/evidence/verification/rail-knative-v1.22.0-2026-07-26.json)
on reef-railiance. This is not production approval.
The [substrate runbook](docs/substrate-runbook.md) describes the declared CPU
requests consumed by the railiance-cluster installer.