From 3743cdbd3ed00fccbc8210065e67505f470a9276 Mon Sep 17 00:00:00 2001 From: Zeusina Date: Wed, 14 Oct 2026 19:23:40 +0300 Subject: [PATCH] docs: record bounded qualification and planner acceptance Co-authored-by: GPT-6 --- RESOURCE_PLAN.md | 75 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) diff --git a/RESOURCE_PLAN.md b/RESOURCE_PLAN.md index 4179228..4b339fe 100644 --- a/RESOURCE_PLAN.md +++ b/RESOURCE_PLAN.md @@ -154,3 +154,78 @@ with exit 78. Ordinary legacy/generic monitor exit 78 remains a safety veto. No unsupported `--filter-mark` or blockcheck embedded/stream/progress/deadline flags are used. Background noninterrupting search and generic apply migration remain deferred, as does immutable snapshot rotation for repeated runs. + +## Bounded remote acceptance — source `5cdc0cd` + +The isolated producer/registry/matrix/planner slice is **bounded-qualified**. +Independent privileged evidence audits passed the observed positive, fault and +active-state refusal gates. **Full remote concurrency acceptance is PARTIAL**; +this is not generic apply, active-profile maintenance or service READY. + +Root-private proof references (retained reports, not logs copied into this doc): + +- `/home/agent/zapret2-autotune-matrix-5cdc0cd/execution-free-private/execution-free-report.md` +- `/home/agent/zapret2-autotune-matrix-5cdc0cd/fault-final-private/qualification-fault-report.md` +- `/home/agent/zapret2-autotune-matrix-5cdc0cd/refusal-gap-private/remaining-refusal-reports.md` + +### Observed positive and fault gates + +- The execution-free private batch made 60 actual transfers: two candidates, + five resources, both TLS protocols, three attempts per cell. Its 20 aggregated + cells contain 16 PASS and four `expectation_failed`: mandatory resource d's + HTTP 500 fails for both candidates/protocols, leaving d unassigned. Exact + hosts a/b/c receive the greedy multidisorder proposal with authentic multisplit + alternatives. Input groups remain metadata, not assignment boundaries; + there is no generic suffix coverage or automatic apply. +- Independent verification authenticated the exact stored payload HMAC, not a + reserialized JSON equivalent. Distinct native arguments/worker-argv hashes, + executable/Lua/rules evidence, queue 200 and NFQ 1.0.2 attestations bind the + two joined/restored runs. Disabled baseline bytes stayed unchanged; sampled + workers, queue and temporary NFT rules were gone. Official PID 1 shutdown + exited 0 in 1.31s; foreign inspect hashes stayed unchanged. +- Mid-batch cancellation and effective semantic config drift each stopped + after two requests, published no matrix and preserved the native baseline. + Official PID 1 exits were 0 in 2.46s and 0.44s respectively; the deliberately + changed config source was retained, not silently rolled back. +- Unsafe Lua/queue/fwmark/user/file definitions and evidence/schema imports + were rejected without transfers. Oversized capacity was rejected before + worker launch; unauthorized isolated startup was refused. Corrupt MAC blocked + planning while preserving payload bytes; changed effective config produced + unknown/unassigned output without changing the original authenticated matrix. + Immutable catalogue replacement and completed-matrix retest were refused + without transfers or overwriting original state. +- A genuine archived v3 committed journal with two candidates passed official + `reconcile`/`ActiveCandidates` validation before qualification refused active + profile state. Profile/config, journal, last-good and target identity remained + byte-identical; zero transfers/workers and no matrix. Actual PID 1 exit 78 was + an expected early preflight refusal, **not** an exit-0 cleanup ACK. This did + not activate or maintain a running active-profile NFQ daemon; that remains + unsupported. Whole-DB byte preservation is not claimed. + +### Explicit limits and testing lesson + +- Remote qualifier singleton conflict is **NOT RUN**. The earlier planted-lock + fixture failed initialization before that branch and does not count. The + shared-lock unit second-acquire `EWOULDBLOCK` check passed, but is not remote + qualifier concurrency acceptance. No deterministic official lifecycle seam + exists for this bounded test; no test framework or racy injection was added. +- Natural 24-hour remote expiry is **NOT RUN**. The existing unit check rejects + a structurally valid 25-hour-old proof; this is not observed remote expiry. +- Privacy sentinel absence was checked in tested logs/state and sampled fault/ + refusal argv. Positive active argv and exhaustive DNS packet-level privacy + were not proved. Configured/observed encrypted DNS is not exhaustive proof + against transient fallback. +- Compatibility on this baseline is not causal DPI-desync benefit. Historical + worker-scan EACCES origin remains unknown; nonrecurrence in the execution-free + batch does not identify its cause. Earlier harness failures remain recorded + in the referenced reports, not erased or relabeled as product acceptance. +- Stage all inputs before target startup. From startup through qualification + completion, prohibit target `exec`, `cp` and `nsenter` (even passive exec starts + a process). Observe host `/proc` metadata and Docker logs/inspect only; inspect + runtime and run `plan` after finalization/cleanup. The explicit official stop + used for cancellation is the documented exception, not an observer exec. +- Owned test containers/network were removed and private evidence retained. + 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.