docs: record autonomous three-CDN qualification acceptance
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
3fc8563995
commit
ea886e5bc8
3 files changed
+90
-18
No files matched your search
+35
-7
@@ -1,6 +1,35 @@
|
||||
# Fresh managed-test target contract (isolated acceptance, not production approval)
|
||||
|
||||
## Autonomous three-CDN source candidate (2026-10-13): field acceptance pending
|
||||
## Autonomous three-CDN acceptance (2026-10-13): media qualified, NOT READY
|
||||
|
||||
Supplied field results bind source `3fc8563995e890310580ba8f78850b92fea42136`
|
||||
to managed image `sha256:a902e4efd949a7ffce4414fd99ab4a815a643b40cf9b9e30e2bd2db7b452817a`,
|
||||
container `4c6b34…`, Compose project `rc0398e6f…`, SOCKS `127.0.0.1:11082`.
|
||||
Native post-cooldown recovery at 08:07–08:09 automatically discovered three actual
|
||||
ordinary signed-media hosts without manual domains and promoted Adaptive candidate10
|
||||
through fresh version-1 `owned-nfq-media-range-v1` proof and deployed checks.
|
||||
Generation9→10, IDs `[1,3,9]`→`[1,9,10]`, scope
|
||||
`experimental_googlevideo_suffix`→`suffix`; frontend1, thumbnail9 and common
|
||||
`googlevideo.com` hostlist were preserved (config hash prefix `dc997ac91…`).
|
||||
|
||||
Measured hosts were `rr16---sn-n8v7znsz.googlevideo.com`,
|
||||
`rr18---sn-n8v7zns6.googlevideo.com`, and `rr5---sn-n8v7kn76.googlevideo.com`:
|
||||
each passed post-warmup 3/3 on TLS1.2 and TLS1.3, all18 HTTP206/65536-byte
|
||||
MP4 `ftyp` transfers with Range `0..65535` and valid SSL verification.
|
||||
Separate warm attempts/failures were 2/0, 3/1, 3/1 respectively, not cold evidence.
|
||||
Fresh owned proof checked at `2026-10-13T08:08:28.752Z` retains actual endpoints,
|
||||
source IDs and native-owner Lua binding; three roots/prefixes were measured.
|
||||
Native request statistics were not persisted; manual request count is unknown.
|
||||
|
||||
At 08:21:48 the reported container and monitor were alive, but whole-service
|
||||
health remained false / DEGRADED. Probe failures405 at 08:20:37 do not independently
|
||||
establish an avatar-specific cause; yesterday's avatar timeouts are separate.
|
||||
The orchestrator's fresh owned-SOCKS greeting was `0500`; native `socks5h` uses
|
||||
SS DNS `8.8.8.8`. The passive SSH watch vanished after about ten minutes;
|
||||
no normally completed 18-minute watch is claimed. No cooldown was reset.
|
||||
Private supplied proof: `/home/agent/zapret2-autotune-rc-3fc8563/field-private/proof/final.safe.json`
|
||||
(not independently reread by this docs update). No new deployment/probes here.
|
||||
See [PROGRESS.md](PROGRESS.md) for the measured snapshot and remaining gates.
|
||||
|
||||
The user's three-CDN requirement is retained; the proposed single-CDN relaxation
|
||||
was withdrawn. Service-mode discovery needs no manual domains: missing/empty
|
||||
@@ -24,12 +53,11 @@ still waits at least two hours. Qualified frontend is required; avatar success
|
||||
does not block this media stage, but whole-service health remains DEGRADED until
|
||||
actual avatar checks pass. Legacy service-off/exact-host behavior is unchanged.
|
||||
|
||||
This source candidate has only offline unit/fixture verification, not a newly
|
||||
deployed image or field-qualified autonomous promotion. The 2026-10-12 measured
|
||||
results below remain historical exact-endpoint evidence. Build from the committed
|
||||
source archive and field-test the owned factory, three actual CDNs, deployed
|
||||
relearning/apply, rollback and whole-service health before acceptance. Maximum
|
||||
strategy collection and PID1 global-failure stay-alive remain unfinished future
|
||||
The representative three-CDN Adaptive promotion is field-qualified above;
|
||||
whole-service/avatar acceptance remains open. The 2026-10-12 measured results
|
||||
below are historical, not the new factory evidence. New images still require
|
||||
their own source/image binding and guarded apply/rollback acceptance. Maximum
|
||||
strategy collection/search diversity and PID1 global-failure stay-alive remain unfinished future
|
||||
increments. Arbitrary declarative service configuration is future work; no new
|
||||
generic policy framework is supplied. See [GOOGLEVIDEO_DISCOVERY.md](GOOGLEVIDEO_DISCOVERY.md).
|
||||
|
||||
|
||||
Reference in new issue
Block a user