Prepare authenticated lifecycle runtime and production release candidate
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
parent
f3b71b1521
commit
4f546ae3b1
41 changed files with 2598 additions and 52 deletions
12
SCOPE.md
12
SCOPE.md
|
|
@ -308,3 +308,15 @@ implementation, not a deployed intake listener. Attribute contracts, forwarding,
|
|||
workload custody, private listener composition and live acceptance are tracked
|
||||
as blocked tasks in INFD-WP-0005, with acceptance requirements in
|
||||
`docs/intake-dependency-requirements.md`.
|
||||
|
||||
## Initial lifecycle production candidate — 2026-10-04
|
||||
|
||||
The private workload listener is now composed and tested with CA-verified
|
||||
Kubernetes TokenReview, rotating projections and a shared single-writer runtime.
|
||||
Initial audience is net-kingdom-admins humans plus the exact State Hub service
|
||||
account. Attribute review now verifies native requester/human-control and receipt
|
||||
pins before policy evaluation. FLEX-WP-0033 supplies separately pinned lifecycle
|
||||
and v12 review policy candidates. Published immutable artifacts, security scans,
|
||||
server dry-runs and recovery steps are retained in `deploy/lifecycle/README.md`.
|
||||
These changes are not deployed. Requester custody, production State Hub forwarding
|
||||
and native acceptance remain live tasks in INFD-WP-0005/0007 and RPF-WP-0051.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue