docs: record bounded verified-profile rotation observations

Separate positive A/B/replay/A field observations from missing full native and rotation fault acceptance. Retain evidence provenance, cleanup limits and the next old-policy rollback/prepared-repair gate.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 11:09:49 +03:00
1 parent 8d43dd9363
commit 2149a4abc8
1 file changed
+69 -4
+69 -4
View File
@@ -245,7 +245,7 @@ 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)
### Explicit startup selection (implemented; bounded positive field observations)
Set `ZAPRET_AUTOTUNE_RESOURCE_STRATEGY_IDS=s1,s2` with
`ZAPRET_AUTOTUNE_RESOURCE_CONFIG` and `ZAPRET_AUTOTUNE_RESOURCE_APPLY=1` on a
@@ -275,8 +275,72 @@ 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,
prepared repair and the per-PID-1 failure latch; they do not authorize live rollout.
The earlier bounded baseline gates below cover guarded apply/replay, strict rollback,
prepared repair and the per-PID-1 failure latch; they do not establish rotation fault
acceptance or authorize live rollout.
### Verified-profile rotation observations — source `8d43dd9`
**Positive field observations only; partial native acceptance, not full rotation
safety acceptance or READY.** Saved-artifact privileged audits observed default A
generation 1 → selected multisplit B generation 2 → identical B replay generation 2
→ A return generation 3. No repeat positive sequence is required for the next gate.
- A config SHA-256 was `27f9a8ffd56a4c19d4bd522dd9f5a5e8b49b18b0ae48d41431ef9b22975ea772`;
B was `51faacf53e76fa0ce95fead1f02da3846c1706ecb9edc8ddaba095c089ea2c82`.
Replay retained transaction `09dfd03e9741abdf8e6b9f3bd44b2118`; A return used
`49a29d560f086a11f9de770913777e07` and restored the exact original A bytes.
Historical prepared snapshots held actual old-A backup before B and actual old-B
backup before A. Sampled old-committed → prepared → new-committed transitions
demonstrate these observations, not crash safety or failed-rotation rollback.
- Fourteen saved registry/matrix snapshots passed exact-payload HMAC and byte
invariance checks; source fingerprint was unchanged. The two original runs,
16 M=3 cells and 48 prior both-TLS qualification transfers were reused, about
12 hours old at startup, **not requalified**. Native A/B argument hashes differed;
A return matched original A, with native queue 300 socket-inode/PID linkage
observed. Early A-return process inventory is missing; full phase-path native
argv acceptance is not established.
- Six authenticated monitor snapshots each showed four HEALTHY resources and zero
failures. Saved fixture records showed 64 successful GETs, TLS 32/32, matching
SNI/Host and expected-header presence; A return contributed 32, TLS 16/16.
This proves fixture compatibility, **not causal DPI benefit** or continuously live
change. Original A-return official stop exited 0; fixture stop exited 2, not an
observed product failure in this run.
- Evidence base: `/home/agent/rotation-8d43dd9/field-private/` (root-private).
`report.safe.json` covers only generations 1/2/2, not final completion. Generation
3 is supported separately by `a-return-timeline.private.json`, retained state and
`final-passive-evidence/{before,stopped}/` snapshots. The initial harness ended
with KeyboardInterrupt; two continuation-construction bugs and observer filename
alias corrections are disclosed in `harness-path-alias.safe.json`. Corrections
affected host observer artifacts only, not proof inputs.
- Final saved cleanup verification is
`final-passive-evidence/final-cleanup-verification.safe.json`, timestamp
`1792051407108`: both exact owned stage containers and the owned network absent,
eight recorded PID paths absent, both known network namespaces without PIDs,
and three foreign full-inspect hashes unchanged. Owned containers/network were
explicitly removed with orchestrator approval; private state/evidence/keys were
retained. Foreign SS remained running and the two older containers unchanged.
Xray was not mutated; no fresh Xray inventory or exhaustive process audit is claimed.
- The first independent forensic audit passed the bounded 14-HMAC positive evidence,
but the automated grader rejected missing independently refreshed dated evidence
and exact native argv phase paths. Do not upgrade this to full native/safety
acceptance. Unknown-ID remote rejection was **NOT RUN** (unit coverage exists);
full rotation fault/crash/old-profile rollback was **NOT RUN**. Natural 24-hour
expiry remains unit-only, without a 24-hour wait.
- Prior local verification recorded 17 EUID-0 fixtures in one race/parallel pass
with 57 subrecords; namespace UID 0 mapped to host UID 100000, not host-initial
root. Full producer Go/race and four Python checks passed serially after parallel
resource-contention failures; this does not establish a contention-free baseline.
These are prior checks, not tests rerun for this documentation-only update.
**Next critical P0 gate:** remote rotation health failure must restore the OLD
generic policy/ref and bytes; failed rollback health must retain prepared state,
then repair-only reconciliation must recover the old profile, never promote pending.
Also run unknown-ID rejection against a fresh required baseline. Do not substitute
another positive generation sequence for these missing gates. Startup remains
one-shot per PID 1, without automatic apply retry. New-batch/versioned stores,
uninterrupted rotation, broader bounded strategy collection and Prometheus remain
future work, in that roadmap order.
## Bounded generic apply/replay and failure-latch acceptance
@@ -344,7 +408,8 @@ Root-private evidence references (no private payloads reproduced here):
Earlier scan EACCES nonrecurrence does not establish its cause.
- No production READY, causal DPI benefit, active-profile maintenance, plan or
snapshot rotation, automatic recovery or monitor autotuning is accepted here.
Next roadmap work is dynamic profile/plan rotation and compatible selectors,
Next roadmap work is the missing rotation fault/repair gate above, then dynamic
profile/plan rotation and compatible selectors,
generic resource tuning and bounded strategy-DB collections; bounded-ID
Prometheus remains a separate planned function. No new framework, probes or
native/live upgrade was introduced. Legacy YouTube exit 78 and unfinished