docs: record guarded generic apply fault acceptance

Record independently verified bounded replay, rollback, prepared repair and cancellation gates; retain conservative TERM78, per-PID1 authorization and coverage limits.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 08:21:57 +03:00
1 parent 643d0c6220
commit 5d0be0288f
1 file changed
+80 -10
+80 -10
View File
@@ -1,9 +1,9 @@
# Resource compatibility planner and isolated qualifier
`plan` remains **proposal-only** and never changes runtime or config.
Explicit generic startup apply is implemented and independently reviewed locally;
remote acceptance is pending. This is not automatic recovery or production READY.
The per-PID-1 one-shot latch correction passed independent local review only.
Explicit generic startup apply/replay and the per-PID-1 failure latch have passed
bounded remote acceptance with independent privileged verification (see below).
This is not automatic recovery, full concurrency acceptance or production READY.
Explicit isolated qualification temporarily installs an owned NFQ worker and
queue rules, but never changes legacy SQL groups, renderer or apply journals.
Monitor HEALTHY, old SQL measurements and public check JSON are not proof.
@@ -240,12 +240,81 @@ on unsafe/unfinished cleanup. `ActiveCandidates` refuses generic deployments;
managed/resource status validates generic refs without inventing legacy groups.
Local root fixture tests cover the production snapshot factory and shared engine;
independent local review passed. Actual native/network/PID 1 apply acceptance is
**not run**. The next gate is isolated bounded remote acceptance, not live rollout.
The per-PID-1 latch correction passed independent local review and deterministic
180-second simulated retry-window fixtures; no remote PASS is claimed for it.
Roadmap: authorized isolated acceptance; no remote deployment is authorized by
local fixtures.
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.
## Bounded generic apply/replay and failure-latch acceptance
**DONE within the stated bounds**, not full generic autotuning or service READY.
Fault acceptance used source `643d0c6`; the earlier healthy committed replay used
`36aace0` after the atomic launch-ACK correction. Independent privileged audit
returned `PASS_BOUNDED_GENERIC_APPLY_FAULTS` for the observed A/B/C safety gates.
Root-private evidence references (no private payloads reproduced here):
- `/home/agent/generic-latch-643d0c6/field-private/field-report.md`
- `/home/agent/generic-latch-643d0c6/field-private/independent-audit.safe.json`
- `/home/agent/ack-recreate-36aace0/field-private/field-report.md`
### Observed acceptance
- Real apply health reused authentic, still-fresh qualification: 16 M=3 cells,
48 prior TLS transfers, two strategies and four resources. No new qualification,
timestamp rewrite, fake ACK or imported proof was used. Pinned native 1.0.2/Lua
stayed unchanged. The earlier healthy start/recreate each made eight TLS checks
with four authenticated HEALTHY resources; v4 committed generation 1, refs,
config and proof bytes remained unchanged. Both official stops exited 0.
- **A — one HTTP 500:** eight apply plus eight rollback requests, one 500 total.
Rollback committed prior baseline generation 1 and cleared pending. Request
count, journal and config stayed frozen at 45.096/90.084/135.124 seconds;
one apply only, no automatic retry. PID 1 stayed alive/BLOCKED with SS/DNS and
other owned runtime stopped. Official stop exited 0.
- **B — persistent HTTP 500:** 24 requests and three 500s: eight apply, eight
rollback and eight cleanup-reconcile checks, not a second apply. Prior baseline
bytes were physically restored, but failed health retained PREPARED committed
baseline/pending generic refs. State stayed unchanged for 80.097 seconds with
no reapply; official stop exited 78. After repairing only fixture behavior and
changing startup APPLY=1 to APPLY=0, the same state/source/environment completed
eight reconcile and eight monitor checks. Baseline became committed, pending
cleared, and generic was never promoted; official stop exited 0.
- **C — TERM during a real slow request:** one canceled request plus eight passing
rollback checks. The canceled curl was joined before the first rollback request;
baseline generation 1 committed and pending cleared, with no false generic
commit. Actual PID 1 exit was **78**, with `monitor cleanup status 78`, not 0.
Apply health cancellation is collapsed into `errPlan`/CLI 78; outside the
qualification-specific completion path, the supervisor accepts only 0/143 and
retains a sticky failure even after verified rollback. This is conservative
**outcome conflation**, not an observed rollback-health failure or cleanup
defect. Do not blanket-allow 78 or manufacture a completion ACK. A normal-0
path would require authenticated completion plus fresh guards; that optional
future refinement is not a blocker for this bounded P0 safety slice.
### Bounds and remaining work
- A/B/repair/C totalled 65 actual HTTPS requests. All 171 observed owned PID/start
identities disappeared, owned netns were empty, and owned targets/network were
removed. Foreign SS/container full-inspect hashes stayed unchanged. Passive
100ms inventories do not cover every shorter-lived helper; no exhaustive argv
or packet-level privacy audit is claimed. Same-root HMAC-key mutation is outside
the trust boundary.
- The latch is one RAM authorization per PID 1, **not durable manual intent**.
Fresh startup/external restart policy reauthorizes ENV=1; keep unattended
external restart/recreation disabled. ENV=0 repairs/reconciles only. Historical
committed replay/repair allows proof expiry; a new apply still requires fresh,
complete source-bound qualification within 24 hours. Natural remote 24-hour
expiry remains unit-covered only; remote qualifier singleton conflict is still
untested.
- Use an execution-free remote harness: stage inputs before startup; no target
`exec`, `cp` or `nsenter` during active guards. Observe host metadata/private
files and Docker logs/inspect; official stop is the cancellation operation.
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,
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
images/avatars remain NOT READY.
## Bounded remote acceptance — source `5cdc0cd`
@@ -320,4 +389,5 @@ Root-private proof references (retained reports, not logs copied into this doc):
Foreign SS1080 stayed running and legacy11082 stayed stopped with exit 78.
No live upgrade or push occurred; unresolved legacy exit 78, YouTube/image
readiness, transactional generic apply/profile-journal migration, immutable
rotation and noninterrupting search remain outside this acceptance.
rotation and noninterrupting search remain outside this producer acceptance;
the later bounded apply/replay gates are recorded separately above.