coulomb/rail-knative
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rail-knative/SCOPE.md
tegwick 9bad6e7e1f Adopt staged WORK-RECORDS generation and catch the index up. 
The generated index had drifted from the workplan files. The opt-in lets
the pre-commit hook rebuild WORK-RECORDS.md in the same commit as the
workplan it indexes.

Assistant: grok
Assistant-Session: 01a17f9d-fe9d-7d72-9a22-6304f1a2a790
2026-10-28 00:31:10 +01:00

1 KiB
Raw Blame History

SCOPE

In scope:

  • Knative Service, revision, traffic, autoscaling, activation, and rollback contracts
  • derived-rail compatibility and conformance
  • generic Knative workload templates and probes

Out of scope:

  • Kubernetes or Knative operator installation
  • cluster ingress, DNS, certificates, or generic network ownership
  • workload-specific policy and packaging

Generated work-record index

This repository opts into staged-source WORK-RECORDS.md generation through .generated-work-records.json and the isolated .generated-work-records.mk recipe. make generated-work-records reuses the State Hub renderer through the Custodian adapter; make generated-work-records-check verifies byte-exact agreement with staged Markdown. The pre-commit hook uses the isolated recipe, preserves unstaged index edits by refusing them, and retains the generated-only commit guard. It does not contact the hub, alter workplan statuses, or grant deployment authority. This consumes shared tooling; it does not make this repository the provider of the generator capability.