rail-knative/workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md

74 lines
2.1 KiB
Markdown

---
id: RAIL-KNATIVE-WP-0001
type: workplan
title: "Bootstrap the derived Knative rail"
domain: financials
repo: rail-knative
status: finished
owner: codex
topic_slug: railiance
created: "2026-07-26"
updated: "2026-07-26"
state_hub_workstream_id: "b939eaac-c16a-4434-b4ba-3d4995f141a9"
---
# RAIL-KNATIVE-WP-0001 - Bootstrap the derived Knative rail
## T01 - Establish the derived declaration
```task
id: RAIL-KNATIVE-WP-0001-T01
status: done
priority: high
state_hub_task_id: "3692f7e9-3fc2-434e-8176-0ae8d63ac850"
```
The baseline and versioned derived-rail declaration are present.
## T02 - Add derived-rail conformance
```task
id: RAIL-KNATIVE-WP-0001-T02
status: done
priority: high
state_hub_task_id: "095b9796-e274-4822-8559-d6f7ca9423eb"
```
Validate against `rail-kubernetes/schemas/derived-rail-v1.schema.json`.
2026-07-26: The declared rail passes the base-rail conformance validator.
## T03 - Add generic Knative templates and lifecycle tests
```task
id: RAIL-KNATIVE-WP-0001-T03
status: done
priority: high
state_hub_task_id: "ffad44ca-394b-4092-90d7-fb9a070374c6"
```
Add generic Service, revision, traffic, scale, cold-start, and rollback
artifacts without Qonto-specific content.
2026-07-26: Added a cluster-local, digest-pinned generic Service example with
bounded concurrency, scale-to-zero, maximum scale, health, resources, traffic,
and offline tests. Live revision rollback remains an admission evidence gate.
## T04 - Register and reconcile
```task
id: RAIL-KNATIVE-WP-0001-T04
status: done
priority: medium
state_hub_task_id: "e3ca4415-f1c7-4839-bc13-b17f6497f71c"
```
Register in State Hub and Fabric, publish the base-rail relation, then create
and push the remote repository through an autonomous sanctioned lane.
2026-07-26: Registered and reconciled the repository, published its base-rail
relation through Fabric, and pushed the Forgejo remote.
2026-07-26: Serving and Kourier v1.22.0 are installed on reef-railiance and
passed scale-to-zero, cold activation, revision, private-routing, and rollback
verification. The declaration is now `verified`, not production-approved.