.custodian-brief.md

@@ -1,23 +0,0 @@
-<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief — rail-knative
-
-**Domain:** financials  
-**Last synced:** 2026-07-26 11:24 UTC  
-**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
-
-## Active Workstreams
-
-### Bootstrap the derived Knative rail
-Progress: 2/4 done  |  workplan_id: `b939eaac-c16a-4434-b4ba-3d4995f141a9`
-
-**Open tasks:**
-- · T03 - Add generic Knative templates and lifecycle tests  `ffad44ca`
-- · T04 - Register and reconcile  `e3ca4415`
-
----
-## MCP Orientation (when available)
-
-If the state-hub MCP server is reachable, call:
-`get_domain_summary("financials")`
-This provides richer cross-domain context.
-If the MCP call fails, use this file as your orientation source.

.repo-classification.yaml

@@ -1,19 +0,0 @@
-repo_classification:
-  standard: Repo Classification Standard
-  version: "1.0"
-  classified_at: "2026-07-26"
-  classified_by: agent
-  category: project
-  domain: financials
-  secondary_domains:
-    - infotech
-  capability_tags:
-    - platform
-    - operations
-    - configuration
-  business_stake:
-    - technology
-    - operations
-  business_mechanics:
-    - coordination
-    - operation

AGENTS.md

@@ -1,12 +0,0 @@
-# rail-knative — Agent Instructions
-
-Keep this repo a derived rail.
-
-- Inherit the versioned common contract from `rail-kubernetes`.
-- Do not copy generic lifecycle semantics.
-- Keep cluster-scoped installation in `railiance-cluster`.
-- Keep Qonto packaging in `rapp-qonto`.
-- Never promote readiness without source-linked evidence.
-- Route credentials with `warden plan`; never expose values in output.
-
-After workplan changes, run `statehub fix-consistency`.

CLAUDE.md

@@ -1,3 +0,0 @@
-# CLAUDE
-
-Follow `AGENTS.md`.

INTENT.md

@@ -1,7 +0,0 @@
-# INTENT
-
-Provide an automation-ready Knative specialization without weakening
-`rail-kubernetes` as the default platform workload path.
-
-This repo must never become a second Kubernetes substrate owner or a home for
-Qonto-specific packaging.

README.md

@@ -1,10 +1,3 @@
 # rail-knative
 
-Derived Railiance execution rail for Knative Serving workloads.
+The railiance operations rail for dynamic knative 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.

SCOPE.md

@@ -1,13 +0,0 @@
-# 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

WORK-RECORDS.md

@@ -1,15 +0,0 @@
-# Work Records — rail-knative
-
-> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
-> stage 3). Do not edit by hand — edit the source file/block listed for
-> each record and re-run fix-consistency to refresh this index. Archived
-> workplans are omitted; closed decisions/intakes/engagements stay listed
-> so recently-resolved work is still visible. [auto]
-
-| Kind | ID | Status | Lane | Source |
-| --- | --- | --- | --- | --- |
-| workplan | RAIL-KNATIVE-WP-0001 | active | — | workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md |
-| task | RAIL-KNATIVE-WP-0001-T01 | done | — | workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md |
-| task | RAIL-KNATIVE-WP-0001-T02 | done | — | workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md |
-| task | RAIL-KNATIVE-WP-0001-T03 | todo | — | workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md |
-| task | RAIL-KNATIVE-WP-0001-T04 | todo | — | workplans/RAIL-KNATIVE-WP-0001-bootstrap-derived-rail.md |

declarations/rail.yaml

@@ -1,45 +0,0 @@
-kind: execution-rail
-rail_id: rail-knative
-repo: rail-knative
-ownership_repo: railiance-cluster
-contract_version: 1.0.0
-composition_kind: derived
-base_rail: rail-kubernetes
-base_rail_contract: 1.0.0
-execution_architecture: knative-serving-on-kubernetes
-readiness_state: declared
-required_substrate_capabilities:
-  - kubernetes-api
-  - knative-serving
-  - knative-networking
-  - dns-and-tls
-  - workload-identity
-  - restricted-egress-enforcement
-inherited_semantics:
-  - workload-identity
-  - criticality
-  - dependency-declaration
-  - health-and-smoke
-  - promotion-vocabulary
-  - audit-and-evidence
-  - recovery-requirements
-overridden_semantics:
-  - request-activation
-  - scale-to-zero
-  - concurrency-and-autoscaling
-  - revision-traffic
-  - cold-start-readiness
-  - revision-rollback
-compatibility_constraints:
-  - rail-kubernetes contract must equal 1.0.0
-  - substrate must publish Knative Serving and networking versions
-  - unrestricted HTTPS egress is not production-approved for critical workloads
-supported_rollout_modes:
-  - revision-canary
-  - revision-traffic-split
-  - previous-revision-rollback
-source_documents:
-  - repo: railiance-master
-    path: docs/rail-composition-contract.md
-  - repo: railiance-master
-    path: docs/qonto-knative-runtime-contract.md

docs/runtime-contract.md

@@ -1,15 +0,0 @@
-# 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.

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

@@ -1,63 +0,0 @@
----
-id: RAIL-KNATIVE-WP-0001
-type: workplan
-title: "Bootstrap the derived Knative rail"
-domain: financials
-repo: rail-knative
-status: active
-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: todo
-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.
-
-## T04 - Register and reconcile
-
-```task
-id: RAIL-KNATIVE-WP-0001-T04
-status: todo
-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.