feat: rotate generic profiles across verified alternatives

Select bounded canonical strategy allowlists at explicit PID1 startup within the same immutable authenticated registry, matrix and source. Reconstruct stored policies independently for historical replay, reconciliation and rollback; preserve freshness for new policies even when rendered bytes match. Retain legacy refusal and one-shot startup guards.

Local fixtures and independent local review passed; live native rotation acceptance remains pending. No uninterrupted rotation, new qualification or proof-store overwrite.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 10:18:14 +03:00
1 parent 5d0be0288f
commit 8d43dd9363
10 files changed
+473 -31

No files matched your search

+37 -3
View File
@@ -195,9 +195,11 @@ The command refuses standalone/docker-exec callers: actual PID 1 environment,
entrypoint, namespace, direct-child executable/argv and held launch ACK are
required, plus the existing controller singleton and no pre-existing NFQ worker.
First apply supports **disabled baseline → generic only**. Active legacy profiles
and different generic plan rotation are refused; no maintenance interruption is
implemented. Every configured resource must require `both` TLS protocols and
First apply supports **disabled baseline → generic**. Explicit PID 1 startup
selection also permits generic → generic rotation among already verified
alternatives in the **same immutable authenticated registry/matrix/source**.
Active legacy profiles, changed source/catalogue/proofs and uninterrupted live
rotation remain unsupported. Every configured resource must require `both` TLS protocols and
every assigned exact host must have complete, candidate-bound passing proof for
all its resources across all input labels. New apply requires completion within
24 hours, never in the future. Negative/unknown/unassigned hosts cannot authorize
@@ -219,6 +221,10 @@ The **existing** journal gains v4 independently tagged committed/pending refs
(`baseline`, `legacy`, `generic`). Generic refs exclude legacy IDs/scopes and bind
exact authenticated registry/matrix envelope hashes, source fingerprint,
internally derived canonical assignment digest and complete config hash.
Optional scalar `strategy_ids` retains the canonical selection policy on each
generic ref; missing/empty means the original default greedy policy. No policy
is permitted on baseline/legacy refs. This remains v4: older strict-decoding
engines reject the new field, so downgrade is blocked, not silently reinterpreted.
Unknown versions/tags, mixed refs and unresolved historical reconstruction block
without adopting or erasing foreign state; v1–v3 legacy behavior remains.
Staging/backup/prepared/replace/fixed restart/health/commit reuse the same engine.
@@ -239,6 +245,34 @@ checks before rollback; PID 1 bounds the owned session and retains prepared stat
on unsafe/unfinished cleanup. `ActiveCandidates` refuses generic deployments;
managed/resource status validates generic refs without inventing legacy groups.
### Explicit startup selection (local implementation, remote acceptance pending)
Set `ZAPRET_AUTOTUNE_RESOURCE_STRATEGY_IDS=s1,s2` with
`ZAPRET_AUTOTUNE_RESOURCE_CONFIG` and `ZAPRET_AUTOTUNE_RESOURCE_APPLY=1` on a
fresh container PID 1. Empty retains default greedy selection. The bounded list
accepts at most 32 unique registry IDs, canonicalized in lexical order; malformed,
duplicate, unknown or incomplete-coverage requests cannot authorize a transaction.
Eligibility is filtered **before** equal-args/selectors coverage merging; excluded
candidates cannot lend proof to a selected profile. Compatibility evidence and
all alternatives remain visible; the policy is not proof or a new qualification.
No registry/matrix files are written by rotation. Exact hosts, both TLS versions,
all required cells/M=3, native/source integrity and the 24-hour freshness gate
remain required for every new selection. Identical committed selection replays
without reload even after expiry. Distinct redundant allowlists are distinct
policies and may create a transaction even if rendered bytes coincide.
PID 1 forwards the setting in environment only; the apply child authenticates it
against PID 1's original environment, not CLI arguments. Syntax is validated
even with APPLY=0; nonempty policy requires generic resource config. With APPLY=0
selection is ignored for reconciliation/monitoring (registry membership is not
resolved): committed and pending refs reconstruct independently from their own
stored policies and historical completion horizon, never the requested setting.
Prepared recovery restores the old generic bytes **and policy**, never promotes
the pending side; failed rollback health retains prepared state for repair.
Startup still allows just one attempt per PID 1; external restart policies reset
that authorization. There is no monitor autotuning, new qualification, proof
import, snapshot overwrite or uninterrupted maintenance in this slice.
Local root fixture tests cover the production snapshot factory and shared engine;
independent local review and deterministic 180-second retry-window fixtures passed.
The bounded remote gates below now cover guarded apply/replay, strict rollback,