[OSDI '27] Submission-readiness epic and evidence gate

当前主线：真实 MOD 组合（2026-10-19）

H2/#63优先真实接口、隐式依赖、冲突和适配成本。PR258保留首轮实际证据与H2重设计；旧24是冻结子群。扩展49个声明扩展/provider仓边界（33public/16restricted，28在旧24外），不是49个独立实测算法；新增5深审。

r6修复后五组已完成：10次真实HTTP200、15份原Profiler drained shards。 Host-only、KV单独、Profiler单独和两种逐进程实际组合顺序，Qwen2.5-7B TP2，4/1201输入各32输出。KV原Scheduler/双TP提交与真实NPU prefix10→9（8目标+1decode）和Host回收对应；Profiler canonical bytes/hash/count/seq、12条scheduler事件逐RID/clock对应，有限窗口drop/error/loss=0。独立198原epoch全消失、原端口无监听、NPU0/3空。最终manifest fbda64a2…6573ce，完整原件在management/real-mod-H2-native-20261018/independent-reader/r6-final/。r1–r5失败/unknown仍保留，不追改、不当MOD冲突；r6不冒充原legacy正式H2或性能/质量。

新native repeat1五组已完成、10次HTTP200：actual-three-method-native-repeat1-20261019-r7，固定四源及Manager c86e48d官方wheel，新env5134安装文件启动前重hash。独立640次neutral双TP真读回与Host7/kernel/RID/RAW/hashchain对应，三KV组prefix10→9；15原Profiler shards原drained/hash/count/clock及12Host事件严格一一关联。193原epoch全gone，原30101..05无LISTEN，两次fresh NPU0/3空。final manifest 52d5e666…b9c0a7。源guard不绕过，无Plan不伪造ACK；reader事后实现/heldout=false。共同显式order adapter计三法成本；三方法×3重复最多45启动仍仅1family，余40尚未执行。每组清理推理进程显存，不改平台配额。

结果已同步inference-engine-project研究报告与campaign原件索引；PR258新增r6稿0fe8e6f，Tectonic实际rc0/body12,total14，仍Draft/open/NO-GO。

PR259源约束PP≥2/KV PP=1经显式adapter进入真实compiler，两顺序拒绝，stock漏检保留；这是source-level反例，不是native干扰。完整三方法/heldout/正式H2/性能/质量仍未完成；旧n4/31modeled/H1负结果不改，整体NO-GO。论文仅Tectonic，当前body12/total14，本次状态更新未改TeX。

ECPA → OSDI ’27 Research Track execution ledger. NO-GO: original #59–#65 acceptance incomplete. This current header supersedes historical entries below. Preflight, simulation, historical evidence, source CI and admission failures are never promoted to formal native/performance results.

Original scope	Current actual status
H1/#59	Closed/falsified; clean-wheel TP2 trials remain functional preflight.
H2/#63	r6 five groups/10HTTP/15 drained shards complete, bounded support only. Native repeat1 five groups complete, finite scope; three-method/heldout/formal comparison incomplete.
H3/#61	Original25cells/225starts incomplete. Current observer nine: 4 admitted real faults, all objective failures; fifth start rejected before fault. Original9 incomplete, 0 complete formal results.
H4/#62	Clean comparative performance 0/36. Historical lifecycle9/9/2448HTTP200 is not clean native/performance qualification. Last automatic H4 attempt failed source-byte binding before Host; device window released to current H2.
#60/#64/#65	Traffic authority, novelty/baselines, and submission artifact incomplete. Tectonic only.

Closed failed H3 cohort: selectedSDK b83bb52/tree df3712c1f59a0a6da1218c9a7e5cd29fd6ce08f6; ordered merged PR250/5bcbd16f CI540 then PR251/05d664c0 CI544 all3SUCCESS, no invented combined CI. Host731d8bcd/Ascend153535b3/KVd4090a88/profiler23caefea, official8wheels in environments/h3-r2, actual44source/core42 equivalence. NPU0,3 suffice TP2. Fresh base receipt29316B SHA6b52724b4d61b4624a40d36a1ac2630d41d58e79b0d8c87467225a46881e17c5 and live14578B SHAbfa36de518f9d28ad0f69ee15b1ddfad63930b3dfc6390768a18ccc161a2e0e5 actually issued rc0. Issuer623.803s/646.353s are management diagnostics only.

Actual controller1692643/start803939199, original run-nine1708316/start804091589; runroot /run/h3o7. Work management/h3-client-binding-fixed-original-nine-20261018-r1/actual-r1. Three management reference-prefix errors corrected before these issuers; old errors retained. Current receipts belong only to this fixed cohort.

Original slot	Actual evidence	Result
1 vanilla	Real TP2 Host1725806 health200; collector1727921 SIGKILL8042009829770533 after first real request.start.	Admitted; objective=false/formal_result=false;60lost/5dispatchslips/operator1.
2 manual	Real TP2 Host1752605 health200; collector1754785 SIGKILL8043467515738698.	Admitted; objective=false/formal_result=false;60lost/operator1; actual ownership exit error retained.
3 ECPA	Manager/launcher1779404, actual native Host/API1779570; collector1781479 SIGKILL8044974571662452; actual successor1781644 created fault+10.848s.	Admitted; objective=false/formal_result=false;60lost/6dispatchslips/operator0. Producer rejection before prepare ACK, no commit/recovery.
4 manual r2	Host1808749; collector1811027 SIGKILL8046446746749612.	Admitted; objective=false/formal_result=false;60lost/operator1; operator timeout26.951s.
5 ECPA r2	Real Host1835066 health200, collector1837033; prepare_native_epoch timed out before fault.	Rejected before fault; not an admitted start. Original controller terminal incomplete/reordered; no retry.
6–9	Not executed.	No completion claim.

All four admitted failures retain original unverified obligations. Four independent source-intake cleanup fields true/errors[]; raw carrier flags unchanged. Actual runner continues after admitted objective failures only with original cleanup gates. Original .5s is dispatch slack, not fault delay; fault follows actual first request.start. No timing, retry or objective threshold changed. Common authority exposure gate is not bare-vLLM safety evidence.

Complete failed-start archives: management/h3-b83-first-real-fault-operator-timeout-full-archive-20261018-r1/manifest.json:193files/68,247,061B+4nonregular, SHA9cff7d122f21609908bf58037ba8d6248be58c0c01befb8e1e672236c5f55227. Second management/h3-b83-second-real-fault-operator-timeout-ownership-race-archive-20261018-r1/manifest.json:91files/4,941,925B+4nonregular, SHA173695f7ab557eca96a54c42087b65a3337fe3e1925a153e887164fabbde6211. Third management/h3-b83-third-ECPA-real-fault-producer-rejection-full-archive-20261018-r1/manifest.json:103files/5,020,530B+5nonregular, SHAc0ef0453a8be6076c86706ad2e51f66a38ea2ab23f18114ca200f846ac051c92. Last two independently reverify102 unchanged frozen inputs from first without duplicating68MB. Every copied/source SHA and before/after/final stat verified; originals untouched. Not a whole-nine terminal archive.

Concrete fixes, independently progressing: baseline operators exhausted original remaining27.074s/26.956s on fresh remote/source qualification. PR255 c7e60b8 prearms the same real explicit operator through source-owned pipe/nonce/kernel proof, then repairs only after genuine fault under unchanged30s.13new+64affected tests pass; CI553/run39128869310 all3SUCCESS. PR256 a95f084 handles only proven original-Popen exit at optional ownership polls; initial strict ownership and full cleanup unchanged.12real-child+62affected tests pass; CI554/run39129885429 all3SUCCESS. Both remote bytes/tree/parent/core42 verified, current runtime untouched.

ECPA real failure exposed a necessary ABI blocker: generic installed Host probe requires native-semantic status/v1, while real H3 collector returns H3-concurrent status/v1. Host PR66 exact0a11b22e2e5949de834e2cf188c151b3754c2ed1 adds strict H3-specific authenticated probe; generic collector unchanged. Manager PR257 exact490af909d111b77347a9df9c824b7f751c328009 preserves actual bounded canonical producer rejection evidence. Both source drafts fully remote-readback verified. Real-UDS tests and original-collector/three-producer integration pass, not native qualification. Old rejected wire.reason was not logged and is not retrospectively asserted. Official new Host wheel build actually started PID1802872/start804609730, isolated source and official empty-wheel recipe; no current install. New h3-r3 runtime/precise source-wheel tuple/fresh dual receipts required. Old all-eight-wheel-reuse next-observer packet is unarmed and insufficient.

PR253 bac359d CI550 all3SUCCESS reduces repeated same-invocation source proofs while retaining original probes/fences; no measured performance claim. PR254 6d75e89 CI552 all3SUCCESS is distinct Manager-after-launch domain; exact officialr51 SHA5c2d6e9337aa1d582ba18749fb166abaa9c1ed381a8a4a829ec6d62666e6969c verified44source/42core/46RECORD, uninstalled/unarmed. Six baseline Manager-domain slots unsupported; original25/225 scope remains.

Actual automatic H4 handoff: passive1695600/start803973260 waits genuine controller1692643/whole original queue terminal, never one slot or management error. Packet management/h3-combined-nine-to-H4-cache252-handoff-20261018-r1 passed24meaningful tests and complete source bindings. Then retained-epoch drain plus two full idle inventories, exactgreen PR252 bb93d28 CI543, actualcombined44/core42 verification, fresh original H4 calibration/freeze/registration/nine /run/h4s3q and /run/h4s3f. Prior H4 replayed1195tokenIDs but tokenizer Triton import created exclusive product dir before Host; PR252 isolates only tokenizer cache. Original released:false and later independent56-epoch release separate; full prior failure archive retained. The original H3 queue is now genuinely terminal with a failed prefix5/admitted4, not9. H4 successor independently drained3470 retained kernels plus two full idle inventories, selected exact PR252 merge05357d6a9c84399785cb47d1d2a1ac5cda10f181/treecfd37d21177970fabf7e3053f5baacbeb47eb2e4, verified44source/42core, and started H4 observe1847925. No new H4 native/performance result. New main05357d6a; original H3 cohort bytes retained.

Ascend PR50 open/unmerged, latest verified54d31aaf. Official OSDI27 CFP: abstract2026-12-01 22:59UTC, full paper2026-12-08 22:59UTC; body12pages including figures/tables, references extra. Tectonic sole compiler.

Full previous header saved management/h3-live-producer-H3-status-source-candidate-20261018-r1/issue66-before-producer-update.json. Historical original ledger below retained verbatim.

Actual next H3 execution

PR #238 fixes a proved prospective attach ABI mismatch: native sender10 was compared directly with original Host7. It now strictly joins untouched Host7 to independent current kernel4, requires typed exact sender10/member identity5 and three unique complete native slots, and preserves the original four-role guard roster. Actual r12 data proof: management/h3-r12-downstream-attach-exact-ABI-proof-20261017.json. This was not r12's observed failure, which occurred earlier at directory admission.

Official main now e6069bd298e22ee21c1af8e49c515e3be896614b / tree ae108fd10e05c2c72ea507b49d4f715fe6fb1fd5, actual exact-CI501 green merge and main/tree/parents verified. PR238 current exact head 6672b6a19c0b180a7850151e79978037ec7bf510, tree ae108fd10e05c2c72ea507b49d4f715fe6fb1fd5: CI501/run39023185321 all3 SUCCESS; main merge e6069bd; proof management/pr238-CI501-root-exact-promotion.json. Prior CI500 Python312:1990PASS/1FAIL/36skip/6subtests; the new negative fixture changed a Host event without recomputing its event_id, so the existing digest guard correctly rejected it before the intended identity predicate. Test-only fixture fix; production blob unchanged 43bca9f644780ecc7571c19682d0e5081a078610. Full failed log and original source retained.

PR238 promotion and r13 preparation actually completed fresh five-source PASS and fresh installed42 matching; original issuer had not issued a native receipt. A subsequent source audit proved Host47 observer globally caps materializations at64 without deletion; original60 requests×28 layers needs1680 per worker. This is a prospective installed-source defect, not an observed r13 workload failure. Root interrupted only pinned preparer process group827662 before any registered start/Host/fault/client window. Original terminals contain error:null from KeyboardInterrupt finalizers; this is not success. Actual frontend exit130 retained, rows[], formal0.

Root independent terminal tracking proved88 retained epochs gone, all three ports closed, allocated NPU0,3 empty and exact H4 runner stopped without children; no H4fifth automatically resumed. Full r13 archive165members/7,334,686B SHA256 1b63f0f04c2f12a81a2702b9a1b186c76763943cf3e5daec0abc7c8da544c2f9; original144 files and original directory metadata unchanged. Exact e606 selected314 protocol/source files captured explicitly POSTRUN. Root independent whole-archive verification follows.

Actual Host fix, isolated runtime, and current r16 execution

Host PR62 is merged as 0df6b96208d9dd31024d16df171e0e30fddcfb80. Exact selected SUT commit 4a468c86735bb23549fad4300efddddaa12860c2 / tree 540d3d15cb85f8457ddb95ddf9b6f801194659fd is a direct merge parent and adds only the capacity patch to Host47. CI145/run39026200689 pre-run-check117377560622 and pre-commit117377580431 both SUCCESS. Earlier143/144 type/style/test-registration failures and full logs retained; final23 regression tests passed1.87s. Test now belongs to actual Buildkite Plugins job; remote pre-commit is not a device test.

The actual private bootstrap derives1680 retained materializations per worker from exact60×28 registered phase/layer inventory, validates ACK phase/rank/layers, preserves all history/uniqueness and legacy64. Real three-arm/two-phase argv independently confirmed max-num-seqs1: clientc8 does not mean Hostbatch8; batch expansion is forward-only and does not block this frozen tuple.

Actual new empty-device Host wheel version 0.31.1.post1.dev8+g4a468c867.empty, SHA4cb418dfa2d685eb76819f5fb72eee49c30b5b6a1ca7e7abba0c6082acdcfa14; 2698 trackedPython +1 source-generated version, full Git bytes/RECORD verified,0ELF. Source-owned SCM uses the actual existing shallow history and explicit setup fallback; no invented full-history version claim. Two failed management build setups retained before the successful build.

The actual r14 owner846162/start795001383 staged environments/ecpa-h3-r14 with private new Host payload and read-only hardlinked exact dependencies. Old H4 installed Host47 bytes/mode/mtime/inode retained; hardlink ctime/nlink changes disclosed. Mandatory PYTHONDONTWRITEBYTECODE=1, no shared-inode pip/chmod/write. Fresh isolated Manager42 and all five source policies passed.

Before any receipt/Host/fault/window, root found the new management ownership helper redundantly hashing the same immutable wheel bytes once per member: 2.126TB of repeated memory input (central-directory arithmetic, not measured SUT cost or extra disk IO). Root pinned and interrupted only actual preparer847211/start795014625 with pidfd SIGINT; original empty preparation, errors, rows[] and all logs retained. Independent root tracker terminal released=true/noH4resume/allocatedNPU0,3empty/portsclosed. This is administrative setup interruption, not an experiment outcome. No qualification was discarded.

The next helper computes each whole-wheel digest once within the same invocation; every current installed member read, wheel bytes comparison and member digest remains. No cross-invocation filesystem cache or weakened predicate.

Actual r15 new seven-wheel ownership passed, but the original input audit rejected inherited tokenizer Host47 metadata/paths. Original failure packet and cleanup retained, receipt/Host/fault/window absent. A comprehensive update now rebinds all22 tokenizer Host sources and the actual Transformers implementation, exact Host metadata/revision, consumer contract source hashes, and baseline KV activation profile paths. The raw-text1195 token IDs/options remain unchanged; no claim of passing the separate1201 chat-tokenization gate. Old artifacts are preserved.

Actual new Plan/base/contract/pluginmap/binding/launch spec generated by the original compiler and validator under selectedHost4a. Exact public Host version is dev8 (the first wrapper compile correctly rejected a local version label and is retained). New executionPlanID plan:sha256:2a1c766c34b312635e2e56e055d2a0b9c369a86018aa6294e72f5fbfa6a7913c, all original worker0/1 native obligations/grants/resources retained; not a qualification result.

Actual r16 owner852953/start795127795/session852953 and independent tracker852954 reuse the verified isolated runtime without rebuilding/reinstalling/copying binary dependencies. Fresh Manager42 match and all five source policies passed. Original shared actual-input audit2,322,479B completed; status missing=[]/publication_gate_ready=true/shared_actual_input_audit_completed=true/native_full_KV_obligations_preserved=true. The ORIGINAL native issuer is now running and independently reobserving canonical sources and actual inputs; original nine start immediately when it issues the receipt. Native receipt27567B/SHAcda0c22c4869dcbb2bf41d4d3195ee416462ea9618fc7cb7c1edcffe2bc832fb ACTUALLY issued and first original runner860769/start795235757/session860769 invoked immediately, independently observed at management/h3-r16-original-nine-registered-root-observation-start-01. No fault or qualified formal result claimed yet. H4 continuation858475/start795186643 is actually armed to resume the original remaining5 ONLY after all9 H3 starts are source-admitted and independently reclaimed; fresh exactH4owner/ports/NPU0,3/oldHostbyte recheck and restore exactHost47/clean precede a single pidfdSIGCONT. Any H3 admission/cleanup failure leaves H4 paused.

Actual r12 failed attempt, unchanged

Native receipt27567B SHAd1e677cca1d2873fb9fddd2c02542f0888fa02ee3d97343aeb1d11824793506f issued; original first vanilla invoked immediately. Real authority772602/peerACK, carrier775668, Host778509/TP2workers778893,778894 reached health and native preparation; collector780293 then rejected inherited directory02700 under original exact0700 private guard. No fault/client window; source intake launched-unverified, formal_start_validated=false, measurements/objective=null. Original nine stopped on admission failure. Do not promote Popen, health, receipt or failed replay to a formal trial.

All364 original regular files and original directory modes/inodes remained unchanged. Complete failure archive398members/8,149,501B SHA6dbdc8b7b07ff1d7d0ee3dbb25d66ebfd751e8f3427e7265c1a2328b64d9b1eb; exact4856 selected protocol314files explicitly POSTRUN, no wheel/model duplication; root whole-SHA/count verified. Root independently proved297 tracked epochs gone/three ports closed/NPU0,3empty before H4 continuation. The directory fix clears SGID only on a new empty pinned root; no old directory chmod and no private/native guard relaxation.

Actual H4 original order

Baseline r1, manual r1, ECPA r1 and manual r2 are source-owned COMPLETE, each272/272HTTP200, failure=null, all3cleanuptrue. Fourth original record SHA60d7ba5468a630dfe6aa5220a018cc66d7e57338a1bd903b060c4b16a21783c7; fourth payload95members SHA43dbb1f1c3f3c504cf865077c917a97626997742e41adfcb8282376936dc5a65, root whole-SHA/count verified. Old572 full-source capture is explicitly reused with its true05:17UTC capture time; not a new source capture. Fourth root handoff released=true/exactrunner572436/start792789591 T/nochildren/threeportsclosed/no later starts. Fresh10:07UTC independent NPU table also proves0,3empty. Original fifth start remains deferred for H3 priority.

Preserve baseline35.35backgroundCPU seconds, manual small measured0.106773CPU+initialunmeasured format check, controlled-mixed caches and interleaved H3 work; no clean matched performance claim. Six internal bins remain null. H4 original scope36 unchanged: remaining5 starts in first lifecycle cell plus27 sampled/conditional starts not yet prepared. H4 request-ID transport4file draftPR239 head94b83657b2a78ba83749b48662458a0fc4bc3b3b now published/fullremotebytesverified, CI502 all3SUCCESS, HOLDunmerged. Its18focused transport tests passed1.81s after fourthH4record cleanup in idlewindow (includesreal localHTTPpeer); notNPU orformal evidence and notfullKV/sample readiness; current short H4 request does not trigger budget1024 compression.

Original scope and decision

H3 remains25cells×3arms×3repetitions=225, first cell nine uses60requests/c8/.2interval/10stimeout/.5slack/zero client retries/original Latin square. Qualified objective failures retain full evidence and continue; admission or cleanup failure stops, partial windows never become complete60. H1 original9 completed but falsified; H2 historicaln4 TP2/TN2 is classification only, genuine threeMOD/common tuple unverified; PR234 remains held because it changes42→44core. No new science score. Paper builds Tectonic only; no submission-ready claim.

Current authoritative local index: management/h3-h4-active-root-checkpoint-20261017.json. Fresh original #59–#66 acceptance mapping55criteria: management/original-goal-acceptance-readonly-20261017/acceptance-matrix.json. Historical states below are retained as history and do not override these live observations.

当前执行总账（2026-10-17；Manager `c7d873ee6224d93a95f95b5824f1ee6e69d551b7`）

整体 NO-GO。H1 正式九次启动已完成但 falsified；H2 不完整；正式 H3/H4 仍 0，原225/36启动计划未改。 最新 live semantic TP2 r12 为真实失败，不能当正式资格或性能结果。

此前完整64,199字符正文原样归档，UTF-8 SHA256 49b48bfcffb33267e5e25e3349e6a241c777931f35747c8335d293edcbf4c93d。归档评论已从GitHub重新读取，正文逐字节匹配。包含此前所有原始成功/失败、版本、gate、归档SHA与历史“进行中”记录；历史状态不能当当前状态。原始本地证据目录不改。本正文收敛为当前结论和全部验收项，避免触及65,536字符上限。

当前真实执行队列（2026-10-17 10:58 CST / 02:58 UTC）

固定SDK仍为 c7d873ee6224d93a95f95b5824f1ee6e69d551b7 / tree 0955710b084ad178096fd50f8ae205656bb94db2。Manager r25仅构建，与真实已安装r23 wheel逐字节一致，活动源码/安装未改。原H1 falsified、H2 incomplete、正式H3/H4仍0，不能把资格、实际尝试、CI或功能结果互相替换。

H3 r5第一项已实际调用registered runner，但最终是原source-owned preflight-rejection，正式仍0/225。 原九次native签发恢复attempt2真实exit0；receipt27548B、SHA256 1f6d4969e86ea27e52ba64a67b5bd2703427e8fedb6dc1fe3d354d22e141b312。实际authority491421/start_ticks792081293在原900s内约203.83s完成ready+真实SO_PEERCRED/argv ACK；carrier494388亦实际Popen。这验证了此前authority超时/ACK点已通过，但carrier随后在Host Popen前按record.schema拒绝：生成recipe identity缺provider_versions、warm_state、container_digest。原preflight-rejection/runner observations明确host_launches=[]/fault=null；原native intake start_validation=preflight-rejection、formal_result=false、objective_met=null。root观察70epochs全退出，29611/29612关闭。wrapper rc0只表示完成拒绝分类，不是正式PASS；没有Host/NPU故障运行。新管理builder正在补全identity与全部下游schema检查，昂贵audit前先校验静态配置；旧packet/receipt/拒绝证据不改。原225/9/60请求/并发8/.2s/10s/.5s/无请求重试不变，目标失败亦不可挑选丢弃。

H4 r7正在真实运行，尚未有正式terminal record，仍0/36。 r6已实际执行16warmup+256measured共272请求全部200，devices/ports/processes清理true；随后record.identity读取缺失host_version时KeyError，record.json/records.jsonl未生成、verify_start未运行。117原输入不改，122regular归档189551740B、SHA256 f3d769accd6d0125bc33651f1e45998318112e3c49b961b80415f2ab93162a02，root独立wholeSHA/成员数PASS；不回填身份倒造record。

r7通过新builder补入真实installed Host 0.31.1.post1.dev5+g47c8aa1ca.empty / Ascend 0.25.1rc2.dev869+hust.20260903.4.g153535b32，全部直接下游identity键静态核完；原9/36/16+256/64与阈值不改。真实注册exit0/admissible=true，receipt6727B、SHA256 dfff614efcb8f478fb4d7f9d46a5328ea9916ea55f1375142bd374eb3d0559c9。H3清理后原队列64771已自动实际Popen runner499854/start_ticks792132037；首项Host500114与双worker已有原始四角色activation-ready，HTTP200开始。证据 evidence/h4-first-lifecycle-20261017-r7 / root Popen management/h4-r7-real-nine-Popen.json。原三臂三轮九次继续；在source-owned terminal/intake前不增加正式计数，不提前声称overhead或native KV完成。产品测量期间不并行模型审计、CPU测试或安装；六内部phase bins仍null/unobserved，完整H4依旧incomplete。

H2 source-only新候选已实际接线registrar→原provider factory→原SDK status/plan→derived专用计分，但只在management保存，未测试/执行预测/发布；测试因产品窗口推迟。新独立oracle由隔离agent只看固定原始source/config冻结，freeze SHA256 9425fa56a794d3642db53360b6352c127f48f1ca26a93708bcd82c6816380ec4；结论限于desired replica writer静态冲突，不是当前cluster或runtime事实，新prediction仍不存在，旧n4计分不变。

当前完整索引 management/h3-h4-active-root-checkpoint-20261017.json。此前r3观察不等、r4父目录遗漏、r5首issuer TLS失败及H4r6首注册Git pack错误全部保留；r3/首注册归档SHA256 4e46e420d0a5025ea41f7aa5a27cea529296ef1c2d87b36c5c1270267410bbb3，不得将历史/模拟/预检升格为当前正式资格。

H3 完整identity修复与后续实际队列（2026-10-17 11:14 CST / 03:14 UTC）

新管理builder build-first-h3-native-full-identity-r4.py（SHA256 07da66658e3e9e53b6f830c055d07af8071ec3ea9bc7a10559f179a5710ed826）补全record.schema全部11项：provider_versions取真实runtime wheel声明，warm_state controlled-mixed以18个独立初始空Tritoncache/sharedmodelcache为依据，container_digest沿用H4对4个实际容器身份文件canonical SHA，明确不是OCI镜像摘要。record identity、原campaign与9模板/18phase/实际carrier投影全部在昂贵audit前校验；schema-only检查通过，未运行新model audit，不改旧packet/SDK或原请求协议。root会话36023已实际等待H4r7原九次终态/清理/端口关闭，然后fresh五仓报告r7+fresh当前安装字节证明r2+新H3r6 prep/签发/原九项真实执行。不是人工review等待，不将此静态修复算实验结果。

旧H3r5拒绝原件保持不变；bulk封存队列PID525883实际等待H4测量终态，新H3启动则推迟，复用旧C7源码tar时明确旧POSTRUN时间范围。H2候选最短27+9代码验证队列PID525508也实际等待窗口，未stage/import/test/predict；结果写management/h2-external-writer-verification-20261017-r1/queue-summary.json。三active MOD原始source输入Pipeline/BidKV/DiffSpec已保存（raw SHA 01ac63f52fcff789a6c43b7cd127ddce87d8396b6827e334823c2df879cef865），但未证明共同精确Host/Ascend/model/topology，严格UNVERIFIED，不赋admit/currentTP2资格，原H2 n4不变。当前H4r7实际产品测量继续，尚未正式record，H3/H4计数仍0/225和0/36。

H2 证据范围复核（2026-10-17）

重新核对#59–#65：H2=#63，n4/TP=2/TN=2为静态分类结果，不是四个TP2硬件cell。#60为authority/exposure安全，H3=#61/H4=#62。静态原n4计分本轮不变。

只读原件审计 management/h2-scope-and-preregistration-readonly-audit-20261017.json（SHA256 bc9838516336c05829f3135110dc59f961b069632d9fdde0e6ca7f267b5c1a2f）确认旧r2 consumer不只是planner标签：它重核真实请求200/非空、EngineCore PID/start、profiler同进程事件、KV日志和清理。但旧runner未独立验证admission先于Popen的时钟顺序；声明freeze16:45Z与首API日志16:42:30/16:44:43存在表面矛盾，日志本身未打印时区，不能当绝对时钟反证。因此旧r2仅保留其原tuple历史源码/实际执行关联范围，不晋升当前tuple正式资格或性能；这也不自动推翻静态oracle/n4。当前H4实测不自动成为H2样本。

剩余H2 source surfaces包括外部authority独立writer推导（移除caller诊断后目前unknown）、真实CLI/config双owner、通信/worker carrier可运行事实与三MOD composition等。PP2×TP2个别既定composition需四卡仅是该cell原拓扑，不能写成当前双卡H3/H4阻塞。外部writer推导修复只在独立候选目录准备，未修改正在实测的源码/安装环境，未新增分数/资格声明。

新进展：真实双MOD TP2功能已跑通；H3 native接线已合并，注册实跑定位剩余缺口（2026-10-17 03:12 CST）

真实双MOD运行 ecpa-two-mod-functional-tp2-20261017-r1 已结束：Manager278682、API/engine与worker279049/279050，物理NPU0/3；KV和profiler均有各角色原始激活记录，实际请求200/64tokens，同epoch窗口有原始profiler request_finished回调。没有内部request-ID join，故只认功能共观测，不认逐请求native完成或性能。root独立复核73epochs退出、29562端口关闭、两卡空闲。4527个文件全部SHA/size/mode归档核验，原4491文件未改；archive SHA256 da2384773e8b276cc06213b58800cadd797e918b6f13c18637fda471f7c6a00a，10,368,012B。H4正式仍0/36。

PR #226 已公开41文件，head 4439bcf2c23ef42065760439018f735bdf7a17a8、tree 0a98786fc8e10654fa1650e6134a72aba5c855da；首CI469两Python均1871PASS/1FAIL，保留日志；CPU测试唯一失败为固定假定恢复必在窗口内。已按原actual请求/fault/recovery时钟修正断言并加outside反例，生产协议不改。finalhead 2bc896804af918e84924881767ef777d2744b287 的CI470/38950267434三项全部PASS，已exact-head合并为 b73dbacf5e21351378a2cc914ac7dfca5fb7be8e，tree f4b6876b1fda9afc6d0495c77e8a017fe224ab78。接通native guard、实际Host/worker epoch、真实worker故障、原60/8/.2/10/.5窗口及独立public proof全native验证。formal_start_validated与hypothesis PASS分开；source-admitted实际故障与partial failed traffic可保留正式失败start，未知指标null，不拿schema/无真实worker的启动失败冒充正式。当前尚未执行正式H3，0/225。

首worker-crash workload此前没有历史冻结payload；本次明确新注册 /v1/completions workload-r2，SHA256 3568b5315ae1519c6f3d40415b68b5ebfef13b7fc4587494b29cc5ba8e159acb，prompt1195tokens、add_special_tokens=false，max128，原协议窗口不变。r12只复用原Plan/contract意图，不复用旧nonce、receipt或运行证据。不增加“先两请求资格通过”才允许正式H3的gate。

真实issuer尝试r1已退出失败（非正式启动、未NPU）：source remote不是canonical GitHub。配置误选Host构建checkout/origin本地路径；现改选实际Host47干净worktree并为Host/Ascend加canonical remote，保留原origin与失败。最终inputaudit已PASS；其中Torch-NPU真实native依赖必须保留，正在补issuer四source tuple与原七wheel实际payload归属之间缺失接线；输入artifact清单与published源码清单分开，全部原319输入检查仍保留。另native authority独立预启动审计不能放进硬编码10s control socket等待，拟使用已注册900s启动预算，客户端原10s截止不变。修复发布前不伪发receipt，正式H3仍0/225。

H3/H4 接线的最新实跑状态（2026-10-17 03:57 CST）

PR227 finalhead c16b8f0 的CI472/38953458272三项全部PASS，exact-head已合并main58fea242；tree a4747e4f611a50c43f6098564338085c8c56f6e7。保留四组件source/AscendELF proof，并独立接入原七wheel实际payload归属；native authority启动使用原注册900s预算，原请求10s不变。官方r22 wheel已构建安装，42core原bytes一致；当前main五仓canonical实取报告h3-five-source-20261017-r2全PASS，不是历史source观察重命名。

真实注册issuer r1–r5均保留，尚无receipt/NPU/formal H3：r1配置引用本地remote/错误Host checkout（已改准确Host47与canonical alias）；r2/r4 Git获取失败，r4原stderr明确curl28 lowSpeed45/bad pack header；root定位冻结runtime环境遗漏8个标准proxykeys，而成功五仓probe保留这些，现native-r4配置已精确保留原容器transport/TLStrue，代理值不外发。r3诊断包装器runpy模块名问题已修，未构成实验启动。r5已真正越过canonical获取和installed/runtime审计，拒在contract hash ABI：SDK bareSHA与H3 sha256:引用不匹配，原18份合同bytes全部正确。两轮collector输出父目录亦已按真实authority接口修为共同startout，Unix路径仍在原108B限制内。

最小PR229 head206e529cedbd6dd06ece3ca7adf6b90e80f000fd/tree7ddf713a537fd3d89abe51c85b15b37c33aed041已公开，CI476/38958427328进行中，仅native contract边界加prefix+mutation反例。对真实冻结native-r4全部18份launch/contract只读验证转换后严格校验通过、原文件未改；诊断report SHA22f11edc1cce2d81fd8f1b8e3fb44df3e73d005915809afa85ac52842db894c0。没有为签发失败伪造正式启动，H3仍0/225。

H4 PR228 已公开原lifecycle-only独立scope：两真实MOD/4角色各原invoked、Managerhandoff/ACK、跨session真实资源采样与pidfd收尾/独立raw复验。原完整KV Plan不删不冒fulfilled。首9真实schema/API配置与完整36矩阵已准备；其余27未ready明确保留。首CI474 Py312 1894PASS/9FAIL为legacy raw缺environment同一兼容错误，原日志保留；head05a131b055a083cfa8db1b5dcce6b049b0ad0113已最小修兼容，CI475/38958201871进行中，新opt-in binding仍严格。独立审计还定位新增共享source资格C混入worker_loading/manual分母，正在修实际产品Popen/ready计时，未独立观测phase不得填0当已测。尚无正式H4/性能结果，0/36。整体仍NO-GO。

当前纠错终态与下一运行（2026-10-16 21:58 UTC）

H3r2的27,548B receipt已实际签发，但baseline冻结配置缺少Host47真实loader evidence sink；canonical Host源码无SINK直接return None，无法产生原invoked journal。root确认authority/Host/worker尚未启动后，按确切owner epoch向session361841发送SIGTERM，62观察epochs全退。原件标administrative predevice configuration abort，不是注入故障/协议结果，不计正式，也不伪造objective。新管理builder明确12baseline phase补SINK=runtime_evidence:record_event与STRICT=1，ECPA仍由Manager设置；原Plan/contract/60请求窗口不改。

H4r5独立registration确实admissible=true；实际first1随后在CLI入口报bytes/Path AttributeError（run_h483→analyze215），未启动Host，root1epoch全退、29611/29612/29712关闭、没有性能样本。保留原traceback；不得把入口失败写成H4性能反例。整轮7a共266原文件前后SHA/size/mode不变，270成员193,028,913B archive SHA 64a4ab44815785316d9472be0d8c783d965e79c46e875644f3fd4d1d0b525867；完整7a官方1045tracked源码POSTRUN侧档，逐blob核验。sealer全payload与root整档SHA/270headers/266original独立复核均PASS；原件未删。

PR231 head287475573bd2d67488310b4b4c80bef8b58da280/tree0a461c44789ce9bfcdd8030553d67575cb415599 的CI482/38970248403三job全PASS（两版1933PASS/36skip），已exact-head合并为当前main dec3982d563bf8b8387010fe35c835c48ab9190e，tree 0a461c44789ce9bfcdd8030553d67575cb415599。原完整issuer/fullvalidator仍全9；每实际runner/authority/carrier/intake新增显式不可换start的scope，仍核完整9静态Plan/recipe/command/slot/receipt/protocol/全部sourceowner，仅昂贵动态fresh检查限本次2epoch。每次原完整内容哈希，无cache/stat替代；未宣称真实性能改善或资格结果。

PR232 基于已合并231，仅run_h4+target2文件，head d26410fb9728e02ff4e88735bc10f24731b1f5e6/tree 0955710b084ad178096fd50f8ae205656bb94db2。按原rawbytes直接SHA，不canonicalize、不改Pathhelper其余调用。真实main --validate-only精确bytes通过/同JSON异bytes与arm篡改拒绝，原6+新3targets/Ruff通过。CI484/38972682007正在运行，wheelPASS、两Pythonpytest进行；root已核2文件远端fullbytes，未提前合并。全绿后统一最终main/fresh五仓+build-only实际匹配proof再冻结H3r3/H4r6并直接运行。正式H3/H4仍0/225、0/36；无历史/CPU/功能预检晋升，整体NO-GO。

当前现场：旧超时已封存；新H3已注册并启动runner，H4已注册（2026-10-16 21:25 UTC）

当前main 7a958ce9848062762a133dfb18b1f8f1521d4395、tree f0993c03a1aa823799719d58ccb2922d18d9d542：230完整哈希并行实现和228 H4 source-owned runner均按全绿exact-head合并；合并后准确main的CI481/38966535773也三job全SUCCESS，Python3.10/3.12各1922PASS/36skip。源码没有在原运行中改动。

旧H3r1/start1 authority340243超出原900s预算，未控制socket/Host/worker/fault。完整intake现已exit0，仅表示观察写入成功：source-owned结果 start_validation=preflight-rejection、error=GateError: authority readiness deadline、objective_met=null、formal_result=false。root独立191epochs全退、29611/29612关闭；没有计正式。640原文件逐SHA/size/mode不变，完整old2bb官方1035tracked源作为POSTRUN sidecar；644成员archive192,170,438B，SHA bb770743bcce1196f10d7d12d4d2a9988ed0963962f4aec12764fbf959d95db8。sealer全payload核验，root独立整档SHA/644headers/640original复核通过。原件及oldSDK仍保留。

新隔离worktree ecpa-manager-formal-runtime-next 精确7a，canonical五仓fresh report h3-h4-five-source-20261017-r4全PASS。官方44source snapshot SHA c69183132239003654c3314e467554b58e605dab413c269cb254ebb108647f66。r24为真实build-only，未安装；wheel SHA84a250f...976e与原r23实际安装来源完全相同，fresh42core及其余payload逐byte匹配proof SHA b3ec12539c6692d85f363af4dae7720532fba5f3426bbb09c611b03e0596c797。原安装未改，不伪填newinstalled；source-owned issuer另独立重查。

新H3 evidence/h3-20261017-r2/preparation/native-r2 全inputaudit PASS，campaign SHA621e25a63399cf20e381a44ff63628e93edfc583af9ddeeb598e6e78f21737fc。真实issuer63653已exit0，27,548B native receipt SHA 52c599f9bb9a36035bc0c863c89059543a7a8fb0b1910bf14cec4ebe39054ddc。root立即启动原LatinSquare start1 runner：session89246、selectedPID361861、outer361841/start790152630；独立原件 management/h3-r2-first-registered-root-observation-r1。当前仍启动前独立复核，未Host/worker/fault，不提前计正式；原60/8/.2/10/.5与225计划不改，不加双成功预检。

H4 management/h4-first36-preparation-20261017-r5 实际五组件source/wheel closure PASS，首9配置/全36矩阵保留；source-owned registration15085已exit0，receipt6,727B/SHA 106eda618f4f10e98d2bc5954aff1fa78e7951345ae5a43a1c81c4fe3329a862，明确admissible=true/registered/formal-real（仅资格，不是实验）。r3 loader env拒绝、r4 profiler打包树非Git(rc128)原件保留；r5使用冻结loader env与canonical profiler exact23ca Gitcheckout，未初始化6gitlinks。builder旧advisory publication_pending保守字段原样保留，真正的published source资格由独立成功registration核定，没有绕过校验。H4内部6phase仍null/不可作完整性能结论。两卡实际运行排队，H3首个故障优先、随后H4，避免同时TP2负载/重审计污染H4。正式H3/H4仍0/225、0/36，整体NO-GO。

首个冻结runner当前现场（2026-10-16 20:50 UTC）

start1 runner已独立复核原receipt并在20:44:28UTC实际Popen native authority PID340243（新session340243、boot/start_ticks原件在runner-authority-observation.json）。其原900s启动预算正在计时；当前仍独立完整模型/源码审计、未有控制socket/Host/worker/fault/traffic，不提前计正式。root持续rawNPU与epoch观察；两卡当前无worker。

PR230 head81536fbff6e730c2e6f56876e9e57b7c31226d4d/tree505b7b8c9e308485541297fa9e1b4edb084d033c，CI479/38963201448三job全SUCCESS，两版1889PASS/36skip；仅2files，root远端fullbytes+blob核对通过。每轮保留所有原19/21次完整内容审计，只在单轮模型inventory内最多4线程原hash；无内容/跨phase缓存，无实际速度收益结论。oncefresh+stat旧候选因metadata-preserving反例已明确拒绝、不发布。230与H4全绿228均未合并，保持当前H3源码冻结，等待真实运行终态；正式H3/H4仍0/225、0/36。

H3 native注册成功，首个真实故障runner已启动（2026-10-16 20:27 UTC）

真实issuer r6已exit0，完整native receipt已实际生成并解析：27,548B，SHA256 b06b41464548c3f5f3d214ee0ed7326f830d33968c9ec4bd5bc373da58224466；未更改原冻结campaign/Plan/请求窗口。root立即启动原LatinSquare start1 worker-crash-r1-vanilla-vllm-entry-points，outerPopen330937/selectedrunner330954，root统一exec session24432。独立观察原件在 management/h3-first-registered-root-observation-r1，每2s保留实际进程epoch、每10s rawNPU、前后端口/清理证据。当前仍是runner独立启动前审计，尚无实际Host/worker/fault/traffic，不能提前增加正式数。后续真实故障/部分失败流量由原native intake判断qualification与hypothesis结果，失败不删。

H3真实签发与H4全绿进展（2026-10-16 20:22 UTC）

PR229的CI476三项全部PASS并已exact-head合并为main 2bb04030e8a0550ac044a58a3d763dd5a447fec3，tree 7ddf713a537fd3d89abe51c85b15b37c33aed041。官方44源文件/42core逐bytes复核，r23 wheel实际构建安装；五仓canonical独立实取新报告 h3-five-source-20261017-r3.json 全PASS。

原协议九次启动冻结为 evidence/h3-20261017-r1/preparation/native-r5，campaign SHA256 96a7de4ff0e0d2a395aec292b439a71d89332621bb89d4e731970c04a7483f70。真实issuer r6（PID323719）20:10:05UTC启动，20:22仍在独立native/model/Plan输入审计，尚未签发receipt、尚无实际NPU启动；不把审计进程算正式实验。通过后root直接运行原worker-crash第一组并保留真实失败，原60请求/8并发/.2间隔/10s截止/.5slack不改，不增加双成功预检gate。

H4 PR228最终head 5abdc5d037950b6fecd7f6976aa7fa52574d8567，tree e8c20c14bffc9a73defe33b4f4443b6c07491dbf 的CI478/38960194121三job全部SUCCESS；Python3.10/3.12各1915PASS/36skip/6subtests，Ruff/mypy/release/conformance/failurematrix通过。已修真实product Popen到独立health200计时，资格审计原始耗时另存，产品资源按真实subtree采样；6个未独立观测的phase bin保持null，不能当0或完整H4结论。为保留当前H3冻结source窗口暂不修改main/SDK，H4 builder适配并行核对；H3/H4正式仍0/225、0/36，整体NO-GO。

最新真实运行终态：r12 第一次公开200，第二次503，整体仍FAIL（2026-10-16 16:49 UTC）

r12 outer47189已exit1，独立现场observer29454 captured=true/exit0。实际Manager229765/API229815/TP workers230176–230177，物理0/3现场证据已保存。phase0原fullglobalprefix277，完整semantic与base consume后实际public200，77生成tokens，响应SHA964f22b49221fa3293ec6b4d0e1ee1b086b6bda36ea387512d6927c32aff8ba6；原30s expiry前2.147190445s完成。phase1全局prefix530保留前一请求完整历史，semanticconsume在expiry内完成，但下一次deployment RETURN晚1.096457911s，原wire503晚1.114863425s；不存在base consume1。原失败completion expired after consume指semantic消费阶段，不能写成已双consume。整体FAIL、两请求资格未过，不是正式H3/H4或性能结果。

原sys.monitoring诊断consumer6.532051241/12.066617606s、verify_request_completion14.299022206/21.070213204s，只属本轮阶段诊断。root独立终态117epochs全部退出、5端口关闭、NPU0/3为空。原742 regular/3,065,382,689B已清点；全部162 frozen/current源码逐bytes一致，fresh official91/core44/staticpub59亦捕获，postrun source capture manifest SHA969028048b8358341ef8388cda2a69cf9f80c79d46093684140168eb37cb2f2c。完整原source双phase独立重放已exit0，报告SHA a5a3e35d48a89551440293b3315ef3b450e9d81d239c0c263f4e6b3424b91558。原742regular保持，193明确postrun copies+2manifest后937regular封存，archive1,742,664,248B SHA c476eb396f9a1b6a3c2769257d1e499ea643d76daa973893eea63dbe57a48de3；archiver全member payload SHA/size/mode通过，root独立整档SHA与937headers全部通过。原失败与局部200均保留，不改overallFAIL。

H3原失败实验无需额外两请求正向资格门；实际source/Plan/native producer仍须接好。继续补原60并发窗口的新native适配、实际启动解释器与source/wheel闭包、真实双MOD义务/epoch绑定。正式H3/H4仍0，225/36计划不变，整体NO-GO。

真实双 MOD 输入与 H3 接线当前状态（2026-10-16 17:13 UTC）

官方profiler wheel59a076...7f99已由root --no-deps安装到实际selected runtime。两个真实installed distributions/snapshots生成2个PluginIdentity，pair Plan plan:sha256:fc18a56459f2cab4211683040ecd4ee0d9c04b860b3587346cdebcd3596f6f31保留原KV全部native义务；原validate_semantic_launch_spec全重算通过。actual2wheel code/ELF+staticmanifest/entrypoints原bytes audit通过，input报告SHA7db4d539b55841e20172b2ca46dfaa1aa753467ef92e72b779bec380bcbec968仅为其当时sourcepins，不复用成最终current gate。root随后最终guard源码actual-installed-pair-plan-r2再编译通过；实际installed Manager双MOD run --dry-run成功，activation确有ascend_kvcompress与request_lifecycle_profiler及Ascend平台依赖，native_manifests确为两bundle。尚非真实paired Host/请求执行、非正式H2/H4或性能。

PR225 仅6新文件；root独立source审查与16targettests通过。原d58e head后补固定Host47 API0+engine-core-scheduler0角色、guard参数deepcopy，最终head6fc77f9241f851de8536a2ccdbe734c85c015c6f treecb541cdf77824754c342d583f4d439aa320c888e；最终head CI38936631181 wheel117093665206、3.10/3.12 jobs117093665197/117093664952全部SUCCESS。root freshhead/base核对后exact-head合并为76d273e55d3708a0609064964f3f83fa478a02a4，独立MCP merge treecb541cdf77824754c342d583f4d439aa320c888e与最终PR相同；旧head CI不作final验证。当前installed Manager core仍为r19经核验字节，不把新main元数据倒填进原r12证据；下一正式carrier须按新已发布source再审计/冻结。

H3新runtimeclosure f237574实际singleton source/wheel检查通过（Manager42/Host2699Py/Ascend751Py+165原ELFs/KV23Py，Manager显式复用root fresh224 Git bytes+MCP anchor；三次TLS fetch失败原件保留），尚待final源码正式source checkout。新native collector/client/bootstrap/verifier/HTTP与fullPlan guard接线中。真实60RID最坏spec声明65179B已能在旧64KiB内，需最终实际campaign paths预检；Host batchlen1/materialized64既有能力边界不假装8并发semantic通过，未证明请求应503并原样记录正式失败。selected-kv-native-arguments-completed是fullconsumer证据履约的Plan义务，不是不存在的Host raw callback；不添加虚构必要门或伪造回调。正式H3/H4仍0。

已再次读取USENIX官方OSDI27 CFP：Research track，摘要2026-12-01 22:59 UTC、全文2026-12-08 22:59 UTC，正文最多12页、references另计，匿名要求保持。该日期已官方核验，不代表submission readiness；未对外投稿。

当前终态与新运行（2026-10-16 15:34 UTC）

PR224 exacthead0cf36ecf76ca18685834451433098b03ca6e15e7 的CI38922761487全部SUCCESS（wheel117046573884、Python3.10 117046574019、Python3.12 117046574146），fresh head/base复核后已合并为eb8bfee29d727cfda714fb17e28bfeefee52769e，独立MCP tree7f4ddb4e70955bab6bb8b62373da201247ca3fb7与最终PR相等。fresh canonical source admission PASS；fresh空canonical HTTPS Git重新核验91 blobs/core44/publication59，实际runtime39范围保持。首次采集误用系统Python无Manager包而在设备启动前拒绝，失败日志保留；改为实际runtime解释器后新prefix manager224-r2通过，没有加入SDK/src。

r19官方Manager重建、42 core全bytes核验后安装；core未改，wheel SHA仍84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e。新组 ecpa-request-semantic-tp2-20261016-r12 两份独立原input audits、162 frozen sources、71 native peer refs、新Plan/book/nonce已通过；config SHA b776d0c0b6de704c56624027f36b99b8baa4ead47a8bdc6cb4607602bab71d05。root outer session47189和独立只读observer29454已实际启动，等待真实Manager/Host/TP2进程及原响应。保留30s、完整历史、真实原epoch/fresh source检查；尚无终态或PASS，不计正式H3/H4。

profiler PR34 exactheadd013a7f68354006ef87b1c119deb1abd133f5a12全部3 workflows SUCCESS（38922791851/38922791771/38922791734），独立七文件审查无阻塞，已合并为23caefeaf2e61f3f0f9f8d3599314b6732eb2a8f，MCP treeb846c55b03ccf079c27d4d41ac25eeec7baf61b9相等。fresh canonical Git官方wheel构建完成，24 package payload逐bytes等于合并source，wheel59a076511a5141e0d3c193b3747c56dc75daa12f9382e3ecf9c9774628937f99。源码仓库6 gitlinks明确未初始化、不当成实际runtime；r1采集未识别gitlink而拒绝，保留后r2显式记录其非wheel构建范围。当前未安装profiler，未声称实际双MOD或H4结果。

H3/H4新实现正在补实际启动runtime/source闭包、真实native-completion并发证据和双MOD身份/义务绑定，不触r12冻结39源码。已纠正额外人为门：原H3在真实source/Plan/producer接线后应按原60/8/.2/10窗口真实执行并保留503/超时/fault/recovery失败，不要求先两请求资格正向PASS；public200仍必须全部原semantic obligations真完成，不能降格为invoked。正式0、原225/36计划不变、NO-GO。

当前进展：r11 已封存失败；仓库归属恢复；两项新 PR 待 CI（2026-10-16 15:20 UTC）

以下旧节的“正在运行/待 CI/归档中”均为当时快照，以本节终态为准。PR222 已在 exact-head 三项 CI 全 SUCCESS 后合并为 b106732，tree2242b2c4d84aad1a81ac72c7a8c147b4e7374ccc；当前 Manager main 如标题。

r11 为真实 TP2 FAIL：Manager209771/API209857/workers210251–210252，物理0/3各57471MB；完整281全局记录、56 tensor、56 OP、2 closures，producer/owner/default consumer canonical SHA均77d97674a074f07fda64c012591062852e5a39b55e16e946f338972e9796b0c8。semantic与base consume均发生于原30s期限内，但最终deployment校验晚0.952190691s，实际public503（晚0.970974929s），无200/phase1。full consumer实际8.241486258s；不能据此给资格PASS。原源码完整失败链独立重放通过只证明FAIL证据一致。root确认124原epochs全部退出、5端口关闭、NPU0/3为空。

r11封存713 regular成员，archive740585872B SHA d0c3afc3c2bf476af0e288e3076c0c5e4400db8b6c6ea845caad87de1178ef9a；archiver核验全payload SHA，root独立全archive SHA及713成员名/size/mode/count全部通过。r10亦封存631 regular，494424748B SHA aa80adc454a7de9cfafbe1c319407dd6f6d6ac9a32734b2f0ff7703100d76323，root独立核验通过。失败原始文件不改。

PR224 head0cf36ecf76ca18685834451433098b03ca6e15e7，仅5文件，去除同一次owned immutable materialization内重复SHA；每次fresh read仍独立SHA，全部原source/OP/tensor/ACK/drain/clock校验保留。38测试及独立misuse审查通过；56/112完整历史纯CPU谓词等价，分别节省1.126/2.375s，不是完整consumer或H4性能。CI38922761487实际in_progress；未合并、未跑新资格，不提前记PASS。

经用户明确授权，使用用户token将原profiler仓库ID1296664162恢复至 vLLM-HUST/vllm-hust-request-lifecycle-profiler。恢复前后main均8b8245cdba61b2ccc92a02c81b158c8fc9f90d14，非新fork或代用品；独立MCP再次确认owner/name/ID。profiler PR34 headd013a7f68354006ef87b1c119deb1abd133f5a12已在正确仓库发布7文件Host47兼容修复。idle-evidence CI成功，CPU CI与bundle CI仍在运行；真实双MOD activation/H4尚未完成。

H3 dynamic载体新19文件本地ccfab467，真实Popen/HTTP CPU机制测试通过，但实际Host47/Ascend153/KVd409 compile仍有worker native-completion义务。当前invoked-only载体正确拒绝该实际Plan，三arms均UNREADY；不会删除义务来凑正式结果。下一步连接实际native producer完成证据和新epoch动态authority。正式H3/H4仍0，225/36原计划不变，整体NO-GO。

#223 已合并；r10 真实失败，r11 新组实际启动（2026-10-16 14:48 UTC）

PR223 最终head b35c239、CI38911747494 wheel117009030049、Python3.12/3.10 jobs117009030351/117009030722全部SUCCESS。root fresh PR head/base确认后exact-head合并为a85dd1cc63b8264b93791e8925ddfec9929ecae7；独立MCP Gitcommit tree6c3f05b0d7ba22f2147a158b2fff4887c28dc9f7==最终PR tree。仅三consumer源码+targettest+prospective生成hash同步，旧失败CI未覆盖。

新空Git canonical HTTPS source admission 31.1s PASS，报告SHA3ddba4bb51d2227a080c00b4ff90f5d6f0c742d8ab5fa8cfd455fba82c058b7d；仅Manager本次fresh、其他三固定组件观察显式复用。另独立fresh空canonical Git捕获91个真实blobs、core snapshot44、静态publication59，全Gitblob/localbytes通过，三份SHA分别a7c17f4cccf7263c3a39b19cb65cb83c8ae95ca80be227571370ca8dea515f61 / f33a5a6b2bb24a69542ecf18b732baf064e8a5c1f5166ef2520675625728d4be / 3cacce057e121f5df4b39947acfd2320e3e308e0e626e458ca30de72941d8ccf。实际运行SDK引用39，与原r9冻结声明及fresh import/declaration精确相等；59是更广静态捕获范围，多出的20不冒充runtime imports或历史validity。 初次harvest把fresh39与旧59等同而拒绝，原失败stdout/stderr保留，随后明确两套范围再fresh新prefix manager223-r2通过，不靠SDK/src强凑集合。runtime仍用installed core与CANN vendor paths。

r18官方core42 fresh构建、全wheel源码字节核验并安装；core未改，wheel SHA仍84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e，不声称新native编译。新组ecpa-request-semantic-tp2-20261016-r10 两份原inputaudit、162冻结源、新Plan/book/nonce已通过；config SHA87ceee318d5ed9e5c8174af634fc9ce7b7e76143784772515adceebb33046b00，root实际outer session19958已启动，独立只读live observer75094等待真实enrollment/SMI/epoch现场。原r10已终态FAIL：实际public503，owner/outer均exit1、watchdog未触发、cleanup=[]。Manager200463/API200509/workers200795–200796，root现场SMI两卡各57471MB与实际前后kernel一致；完整journal实际69records（4start/9native/56tensor/0OP），无完整semantic completion。原receiver源谓词正确拒绝：66个peer refs fresh SHA全正确，但SDKobserver新db9d2不在其中，仅installedHost原observer538320在；过去两文件同bytes偶然满足digest membership，不是新的receiver实际执行证明。root承认是本轮runner依赖声明遗漏，不修改旧组/不放松source gate。

root独立终态122epochs gone/五ports closed/NPU0/3empty。434原件882827668B inventory SHA40d24f16e02286344223b9fe73efa3a652eb9842dd391b7914f880d0fbcce667；完整原162/official91/core44/publication59与原freezer已捕获，manifest SHA87135cf626972712e96c49da5a636bf1f134a9550a574f3f71013233a71ba7e3。只读source-predicate诊断非中断链fullconsumer PASS；原r10现正按批准补充196copies+manifest封存，最终archive未完成，不预报SHA。

仅management freezer新增显式九receiver模块依赖闭包，保留全部原Host producer pins（包括旧538320），native refs66→71，SDKobserver新db9d2独立声明；构造/原始路径freshSHA检查在mkdir前，11个缺依赖/Host偷换反例拒绝。freezer SHA b602256070654457ef7cbf82ed26688d8eedf5198be4682966e2e1aa02b9a8fc；原谓词诊断报告SHAd9742f235b695b704ccc0eea48a58340096a9807342dcffaf6025fdfa672b758；构造报告SHAeef5ddb6becbb2af0c524b351b92d965a94458c56c59ac7e4374d66855f1e9df。没有改SDK/Hostwheel或原30秒。

新r11组ecpa-request-semantic-tp2-20261016-r11新Plan/book/nonce、两原inputaudit、162source freeze通过，复用同一精确official source/core wheel（不冒称重复构建）；config SHA839839e809fd5140a3373cc1fa93e22e1b4da53fbe481075f8f3693908c1ff97，71个peer refs。root outer95566与独立observer53584于14:48真实启动；尚无终态，不预报PASS。两组均NONFORMAL，H3/H4仍0。

H3 PR222 已重基本次实际main a85dd1c，新head6e18102ad9628017cb9007794f5217ce103373f8、treef6ac85c7f955ad3e12f77118d2a8eafda0301ccc；作者12files原bytes+正确union generatedmanifest共13files独立远端核验通过，新CI38913898166完成1775tests通过，但Ruff I001/E501等失败，未合并。root随后仅修五个H3 Python文件的格式、显式zip(strict=False)及具体ValidationError测试，local331cf19；target57passed/5.48s、scoped Ruff、mypy、release readiness、manifest03及failure-permission checks全部过。最后remotehead87c6db8b8313aa7d13dfb5c4e908957969aa2a48/tree2242b2c4d84aad1a81ac72c7a8c147b4e7374ccc，五远端fullbytes==local且原union manifest未变，新head CI必须通过才合并；未混入新的dynamic authority/carrier未跟踪代码。新的真实Popen carrier、独立dynamic authority/client仍实现与审查中，旧static格式/源码不改；portreplacement在发送任何HTTP bytes前验证accepted socket属原API epoch的修复已有实际双backend0body反例，但RPC peer identity/MOD binding/完整client join仍在补，不能作为正式可执行资格。

正在发布的 runner / consumer 修复（2026-10-16）

PR222 已发布H3明确cell dispatch与独立worker→指定API真实祖先关联；原head c6854c6 的 CI38909605652 wheel成功、Python3.10/3.12均1767passed/1failed，唯一失败为prospective SOURCE_PREREGISTRATION_DRAFT_ONLY生成文件的h3_registration源码hash未同步。不能标CI通过或合并；正按实际PR base修复生成文件，完整失败记录保留，不改任何formal结果/矩阵/阈值。

PR223 发布consumer重复纯JSON关系优化，本地commit f89d98a4bb4ce73efc4d9ed7a3c89409439d8cc4，严格三production文件+一targettest；另需同步其实际base的三源码prospective hash。新source CPU矩阵34passed（含实际CPU HTTP/Unix两次新请求与112tensor/112OP及历史篡改拒绝）、私有owned针对7passed。完整before原r8 consumer11.2105s/canonical与两原件相同；candidate默认原sourcepins正确拒绝，不伪oldraw fullchain PASS。原真实r8全部56payload纯关系+laterfresh读取5.398→1.601s，首次owned parse/canonical/完整tensor5.041s另列；真实r2全部514records/112payload纯关系11.057→3.305s，首次10.249s另列。均为POSTRUN_OFFLINE纯关系诊断，非新NPU资格、完整consumer加速比、formal结果或H4性能。 最终CPU报告SHA23d188d3f02d3efb7440f1e8fb179a45ee8e4c004a112490bc6f31c3ee13b1dd。

优先成本PR最终head CI通过后exact-head合并→fresh官方source/build/freeze/新Plan nonce双卡r10；H3新可执行Popen carrier与独立动态authority实际enrollment并行，不将另一个缺能力preflight包装成formal start。原60请求/concurrency8/.2s/10s窗口不改，若55s真实重启赶不上窗口保留失败。正式H3/H4仍0，整体NO-GO。

用户质询后的正式 H3/H4 推进重点（2026-10-16）

正式H3/H4此前确实仍0；功能资格、论文和CPU检查不能替代矩阵。现并行实际修复正式入口：run_h3对所有cell无条件走prepare恢复导致baseline/非prepare必拒，analyze非prepare引用只在prepare分支定义的proof会异常。新共享25-cell dispatcher与worker source-owned carrier/独立新epoch及authority/client raw verifier已提交本地00fe01f7d1dd8a678de62b130611f9e2bbb20b28；55项定向检查通过，包括同adapter下两真实CPU进程树的正确祖先关联与wrong-Host交叉拼接拒绝。已核实实际Host role为api-server；正在独立发布/CI，真正执行adapter仍待实现。缺actuator在launch前拒绝，不能制造formal失败行；225计划不改，旧prepare验证不放松。改动仅未被r9引用formal_campaign代码，原SDK59/core/source_provenance/loopback保持冻结。

H4原lifecycle-only cell并未要求所有case都做selected-KV full-native completion，不能把30秒单请求资格作为其无条件前置。最短真实pair为KV+真typed EventBus profiler。旧 vLLM-HUST/vllm-hust-request-lifecycle-profiler 地址现301至 Qixin-Gaoke/vllm-request-lifecycle-profiler-plugin；GitHub repo ID1296664162与独立公共API读取一致，但未查明是谁、何时改归属。本轮未发起转移或fork。用户明确“不应该转移”，后续以vLLM-HUST归属为要求，停止向Qixin写入，不能将其默认为预期canonical。 对现地址实际GitData写入403(Resource not accessible by integration)，未产生tree/branch/PR。vLLM-HUST/vllm-hust-profiling是不同ID/内容的仓库，不能冒充同一源码。用户随后明确授权使用其GitHub token恢复原仓库归属。当前容器未找到个人token（环境/gh/Git helper无凭据），已请求文件路径；恢复脚本已准备但尚未执行。仅对同repo ID1296664162恢复到vLLM-HUST/vllm-hust-request-lifecycle-profiler并验证main不变，不创建冒名替代仓库；此项不阻断H3与live producer修复。

已保留7-file Host47兼容proposal本地commit231b950b47b698330ad9e245042705e456bd1f34、干净source wheel与四typed callbacks CPU契约；旧88ffd commit只在本地、旧wheel METADATA不全等，不作为published/formal。proposal未安装运行、未正式发布。H4仍须vLLM-HUST下准确可发布源码、真实pair激活与原三臂matched注册，不能把lifecycle invocation写成runtime semantic effect。

r9 ecpa-request-semantic-tp2-20261016-r9 已真实结束 FAIL/NONFORMAL，不是进行中。config SHA b1401812d5375b8bbe33908f780a016b73320b02d0f30b8f9d4f59970b0a49b9；实际Manager175957/API176042/workers176436–176437，root实时SMI/前后epoch观察捕获NPU0/3各57471MB。phase0完整273条global raw，56tensor/56OP/2closure，producer/owner/独立full consumer canonical均为96bed11a8f504e9638f509762063bd7473ef1aa6fae3a53328cbc86a3e4679aa。原semantic和base consume均在producer原30秒内完成；最终release嵌套deployment RETURN晚2.665451606s，真实public503空body完成晚2.685080744s。没有release guard RETURN、没有public200、没有phase1；failure-0001仍是phase0，不能因文件序号计成第二请求。

完整source FAIL replay报告SHA08cef8726c142c0515f2eaced0996f50ceb61057f7570799597edd093921487b，162冻结源/91官方/59SDK/44snapshot/42core/7wheel/两inputaudit/原PlanGrant均核验；未重造MAC/cap。root终态116epochs gone、五ports closed、NPU0/3 empty。637原件及明确postrun补充逐SHA/size/mode封存，archive740256876B，SHA e2d0fbb2292603dbe8f20dafc968b2d6411412b54bca3b800b1004f9027485c1；archive manifest SHA4e0256666160fa9cf87c54b1e6c4d4838f4cf33310bfa27aa5a36b33be3ab96d；旧组永久冻结。

下一修复限定完整consumer的重复JSON materialization解析/序列化，保留每次原始fresh read/SHA、所有global history/ACK/operator/drain、原30秒和公开API；只在单次调用内复用自身完整验证的精确canonical bytes，不接受调用方parsed/digest。纯CPU prototype不是资格或H4，实施需完整真实raw前后canonical一致、负例/CI与新的TP2请求验证。H3 formal runner修复独立并行，不等待该单请求优化。

#221 已合并：最终head完整CI通过；r17/source完成，r9终态FAIL已封存

PR #221 仅authority/live_route_reader及两target测试；初始本地 66663d1e0c0dbd32a23034417a107bb5ad1833f3 的78项定向回归+五个实际CPU HTTP/Unix场景全部通过。实施后真实CPU验证发现marshal4引用标记导致未变audit仍回退，安全检查有效但节省未成立，已暂停合并/新NPU并修复为private-process marshal2和constructor完成后取snapshot；补丁commit 927fe0f73ba322cce3b405f3ac8919fe40fc969a，34 authority tests通过含numeric type/重排/状态与源码修改/未变声明fallback0。原canonical SHA始终是trust anchor，unsupported或bytes失配回原canonical，未使用marshal.loads。

最终实施后POSTRUN_CPU_FRESH_FILE_STATE_FIXTURE（同8148原paths的NOW_lstat与162当前source hashes，不是原r8已不再current的冻结声明）验证：六次original-identity digest调用canonical fallback0；pair比较24.94ms vs原86.26ms（3.46×）；九次完整fresh compiled walk+sourcehash 1.628s vs每次重编译2.549s，省0.921s/guard。fixture SHA ba519bfd8742f96d51d5d75b27762bff19a4746726defb56e13636a9c6308c52，report management/request-semantic-post221-fixed-cpu-cost-20261016/report.json。只复用不可变纯声明，不缓存任何filesystem result、FD、actual ancestor identity、hash/kernel/socket/route判断；原9次fresh walk/source检查、五完整authority边界、原30秒和一次burn全保留。此CPU结果不等于现场、H4或formal资格；PR同分支已更新final head ffb32ca25c699ce9e1715d08f6ca9e98b932f427，tree 2e612da559e73bf144ac0a2e5b3e414bc7ed7bbc，base仍merged220 14d7a87f...。四文件远端Gitblob/fullbytes/compare与local927fe0f一致，metadata-v2 SHA cc1f84b3dca88f30c191d06082e7ad215f681e6469a324db65861a68d75f2c9b，初始head记录保留；CI454/run38904262951 最终head wheel116983797408、Python3.12/3.10 jobs116983797479/116983797800全部SUCCESS，root exact-head合并为 2fb54b7269c14661e11e683d5970da67a1f8390e，tree 2e612da559e73bf144ac0a2e5b3e414bc7ed7bbc。旧head CI不作为final验证。官方91/SDK59/core44全部重新捕获与独立Gitblob核验，SDK59==local，r17官方core42构建安装通过，wheel与前core未改保持同SHA84a250f...；fresh canonical标准代理空Git准入55.41s PASS。

当前主线与真实进展

#220 exact head cbf413601402719b93256f3f3d22feff2a1d55bd 已合并为 14d7a87f8abd2a9cb4314236c7e1425ecf381c07，tree 0aeb82d4be1c22c3dc53db2c67af92b9a1c7e53e。CI451/run38899267640 wheel/3.10/3.12均SUCCESS，jobs116967191722/116967191948/116967192063。仅2源码+2测试97+/4-，去掉4处相邻重复whole-authority current；每次完整deployment的9次fresh文件/source检查、5处完整authority边界、原producer-issued30秒、nonce/一次burn及最终response IO后release均保留。45 focused CPU PASS48.03s、最终实际CPU HTTP/Unix v2 smoke1PASS11.39s；CPU检查不是现场资格。前序#219的9→6 marker因跨实际IO已撤销，未发布。

merged220官方91源码逐Gitblob验证，SDK59全==local，core44交叉完全相等；metadata SHA 37828d92864f5e56bbebf60d37f878849c950c45b556f1fa02443a3c2fbbc5c0。r16从官方core42新构建安装，wheel SHA 84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e；core未变故与r15同bytes，不声称native重编。新空Git canonical首次同标准代理curl28失败84.57s保留；第二次同proxy/TLS/原predicate成功37.48s，manager220-request-semantic-standard-proxy-r2.json。仅Manager是本次fresh观察，其余三个固定组件观察显式复用；源码403已解除，传输重试没有放松gate。

r8 evidence/ecpa-request-semantic-tp2-20261016-r8 是新Plan/nonce/两份原inputaudit/162-source冻结组，config SHA 6950633b76135f1fa762c45cceff7e592f6e62dda8813c2c8043169d44ddc3a2，owner SHA 8cf05e8ec0d3cfb07087f4e5da5a7c57a70bc3120e5003016fa0a67671e212e0。actual outer69711 exit1，owner FAIL，watchdog未触发、cleanup=[]。真实Manager/Host/TP2/collector/producer及compiledPlan、原grant、完整native epoch绑定均由原件和独立full replay验证；不伪造已退出后才尝试捕获的root峰值SMI。

phase0原281条全global raw、56tensor/56OP/2closures；producer与owner两份原canonical均等于独立fullconsumer重算 0c5598572c73e4106cc72e29e5e4d9b0e449d9d46d747e1db0b08e298ff7dfc7。原semantic ticket与semantic consume持久，consume 7870148868609901 在原producer expiry 7870152049643832 前；但postconsume完整deployment结束 7870154066240930，晚2.016597098s，正确拒绝 completion expired after consume。原public503空body及其SHA已实际捕获；没有base consume/public200，没有phase1，整组FAIL/NONFORMAL，不以burn/consume记录替代成功release。

原source独立FAIL full replay95789 exit0，report management/request-semantic-r8-independent-failure-replay.json SHA a06b961c58f3981226d949082fb80904fcae0756dffab874f2dfa0f439a28a93：162当前/冻结源、official91/SDK59/core44/core42/7wheel、两原inputaudit、真实Manager/Host/Plan/grant、原semanticconsume ticket/nonce/obligation/clock全通过；不重建已销毁MAC或cap。root独立终态123epochs已退、5ports29552–56closed、NPU0/3empty。493原regular与3sockets已登记，原162源、official91、全部replay/CPUprofile已完整capture；明确postrun补充172文件，原组逐SHA不变；665/665成员SHA/size/mode全核验，原组重验一致，整档已永久封存：739,645,468B SHA 512004eb560ccacc2b450faa7bb78a6ad987c58aa188770677009941e21e0c68，manifest SHA d4d0ee0bf1f9bbc183f716fdd8b89444bf11ed324e040eff724fa67c7bf9e67c。root另独立整档SHA与665 member名称/size/mode/count核验通过，payload逐成员SHA由封存代理独立完成。

原阶段时钟、CPU定位和下一步

r8 owner仅在5个精确code对象上用局部sys.monitoring记录内存START/RETURN，结束后disable/free再写；没有global profile/trace、无args/retval，不改producer或guard。actual runtime3.12.13双线程隔离预检通过；本轮setup_error=null、cleanup_errors=[]、tool已free。局部UNWIND不支持，原17events里未RETURN的consume不补造异常时刻。原函数跨度：owner fullconsumer10.82224s；各完整deployment4.45–4.64s；verify entry+consumer+exit共20.991442s。因此5×完整deployment+consumer已超过33s。此为本轮诊断，不是H4，不改变原30s。

原fullconsumer只读CPU cProfile90750 exit0并再次与两原canonical一致，插桩12.776s；JSON dumps4.473s、loads3.220s、SHA1.517s、base64decode1.106s、789 read_bytes仅0.694s。不能把事后profile归因成精确原stage耗时。另一纯CPU诊断确认每audit约2.586MB，union8148states/162sources；保留canonical SHA anchor/fallback的fresh marshal bytes快路径及每cut纯声明immutable trie可分别降低重复序列化/建树成本。普通dict equality会混同True/1、int/float/正负零，不采用。

原源码full replay和所有profile已完成，原窗口capture后才放行修复。authority/live_route_reader优化已随#221合并并由r9实际运行；r9完整deployment降至约3.14–3.31s，但最终放行仍过期。当前新修复限定attention_consumer/collector/operator_observer三文件的重复JSON materialization开销，不能省略fresh文件、完整历史或original30秒。旧raw source pins必须继续拒绝修改后的consumer；离线纯helper等价不冒称原source fullchain PASS。新源码的完整default链需新source CPU HTTP/Unix正负场景、CI和新TP2验证。正向两新请求200/consume/release通过后，才运行已准备的3phase未耗尽真实worker故障资格组；不把book耗尽503当epoch故障。

正式接线仍待：真实外部traffic authority的admit/complete语义、实际generation/membership转换与新Host epoch、predecessor可恢复、连续请求/窗口的完整bounded prefix协议。现有registered formal semantic入口仍fail-closed；直接实验RequestServer不等于正式H3。原H3 60请求/concurrency8/0.2s/10s窗口不能静默替换为当前serial unique-body/240s。

当前固定运行范围与结果边界

物理NPU0/3、runtime0/1，两张910B2足以推进TP2，卡数不是阻塞。Host 47c8aa1caa7638d2e5e231eedced45448106fde5；Ascend 153535b32417b3ad8fb10dad2f564ddf4dcab1ef；KV plugin d4090a888f971ea50e874cdf86bf63a8e22e647f；精确wheel、Triton3.6.0+git92513dba、Torch2.13.0+cpu/TorchNpu2.13.0rc1/CANN9.1及model/calibration绑定见原inputs/封存。模型/旧calib/旧失败原件不改。Ascend ELF是逐byte验证复用，不冒称新clean-native编译；Ascend PR50仍须独立核验，未因本轮Manager合并而宣称已合并。

旧forward TP2 r2两臂四个真实请求PASS是v1功能结果；r5 producer完成但owner原期限失败、r7 owner出票但消费过期、r8 semanticconsume后guard过期均保留失败。r6仅GROUP/run启动前路径错误，不计Manager/Host/NPU执行。旧clean-wheel、baseline、tensor/attention、CPU或历史资格均不能晋升为正式H1/H3/H4或性能。

H1#59 closed但falsified：原三臂/五来源/9次validator-approved formal-real starts保留，partial-worker-coverage中3/3 ECPA false-effective、coverage0.5；不能因close称假设通过。H2#63独立n4 TP2/TN2/FPFN0，原n5的ownership_conflicts泄露case排除并保留；不推总体prevalence，真实compatible multi-MOD Host执行仍缺。H3/H4正式0，225/36计划及预注册阈值不改；H4按冻结protocol startup_join=and评估“同时超过5%和250ms才falsify”，throughput1%、p99 2%，manual主成本baseline、vanilla单列，失败行不删。

#59–#65 逐项验收（2026-10-16 fresh GitHub读取）

以下保留各issue当前验收清单；unchecked不视为完成，issue为详细权威来源。论文只用Tectonic；匿名/新颖性/12body页等gate未满足前保持NO-GO。#65日期现已按上节官方CFP再次核验；未执行对外投稿或通知。

#59 [OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) — closed

Study and deployment artifacts contain no stale/open producer facts or null identity fields.
Registration and registry validators pass before the first measured run.
Exactly nine validator-approved formal-real starts are retained; failed starts remain rows.
The oracle independently derives false-effective outcome, event coverage, detection latency, and incomplete-exposure window.
ECPA never reports effective with incomplete required process coverage. Falsified in the retained partial-worker-coverage cell: 3/3 ECPA starts reported false-effective at 0.5 coverage.
Process, port, and allocated-device cleanup is proven after every start.
The generated paper table reports confidence intervals and raw failure counts without replacing missing data with zero.
H1 is marked falsified from validator-approved r5 evidence; it is not inferred from release status.

#60 [OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership — open

External requests cannot reach a new generation before every required obligation has fresh authority-owned evidence.
Gate-open and gate-close events are observed independently from the SUT.
Worker replacement creates a new process epoch and invalidates stale coverage.
A Manager crash, observer loss, or query ambiguity closes or preserves the route according to the frozen policy without fabricating effectiveness.
The predecessor generation remains recoverable until the new generation commits.
Real traces feed the formal runner and are clearly separated from synthetic model traces.
Tests prove that ECPA-owned cleanup does not stop externally owned services.

#61 [OSDI '27][P0] Complete the version-skew, failure, and rollback campaign (H3) — open

Every unsupported tested tuple fails before serving.
Every supported upgrade preserves functional correctness and evidence identity.
The predecessor plan is never lost before the replacement commits.
At least 95% of injected failures meet the preregistered automatic-recovery or bounded-operator-action objective, or H3 is reported falsified.
Recovery time, lost/duplicated requests, operator actions, final route, process/port/device cleanup, and raw failures are reported per cell.
Failed rollback is classified as failed-safe or bounded operator action, never counted as successful restoration.
No result is generalized beyond the exact host, accelerator, topology, versions, and extension classes tested.

#62 [OSDI '27][P0] Run the matched startup and steady-state overhead study (H4) — open

Manual integration remains the primary cost baseline; vanilla loading is reported separately.
All three arms use the same model, workload, topology, and pinned runtime identities.
Per-cell distributions, paired effects, confidence intervals, and raw failure counts are reported.
No aggregate hides a failed provider, topology, version, or extension.
H4 thresholds are evaluated exactly as preregistered; thresholds are not changed after observing results.
A threshold violation is retained and H4 is marked falsified or the paper is re-scoped.
Benchmark processes, ports, and allocated devices are reclaimed after every run.

#63 [OSDI '27][P0] Replace the synthetic composition seed with a real multi-MOD oracle (H2) — open

Every case is bound to repository commit/tree and exact manifest/schema versions.
The oracle contains meaningful real admits and rejects; blanket rejection cannot pass.
Conflict precision and recall are each at least 0.95, or H2 is reported falsified.
Error classes identify the conflicting owners/resources and a remediation path.
At least one compatible multi-MOD composition reaches real host execution with process-owned evidence.
At least one real conflict is rejected before launch.
Results distinguish static compatibility, activation readiness, runtime effect, and performance benefit.
The paper removes or clearly demotes the synthetic seed once the real corpus result is available.

#64 [OSDI '27][P1] Strengthen the systems novelty, baselines, and external-validity argument — open

Every novelty claim names and compares against its closest prior mechanism.
Baselines are implemented faithfully and pinned to exact versions/commits.
The introduction contains a concrete failure consequence and quantitative result, not only a taxonomy.
Contributions separate new system mechanisms from implementation, corpus, and evaluation artifacts.
Related work includes recent peer-reviewed systems/ML-serving work and historical foundations.
Limitations match the actual experiment matrix and do not rely on future-work language to support present claims.
An internal hostile review can summarize one crisp, non-product-specific OSDI contribution.

#65 [OSDI '27][P1] Produce the anonymous, reproducible Tectonic submission artifact — open

A clean Tectonic build produces at most 12 body pages plus references.
The first pages are self-contained if preliminary review is enabled.
Text extraction and PDF metadata contain no public ECPA alias or identifying repository/organization/person data.
All figures/tables are legible without magnification and in grayscale.
Every numerical paper claim is generated from validator-approved artifacts.
A fresh environment can reproduce all non-hardware results and validate hardware-result provenance.
The abstract registered by 2026-12-01 22:59 UTC is substantive, not a placeholder.
Submission is ready by 2026-12-08 22:59 UTC only if the evidence gates pass.

Correction to the 2026-10-12 audit snapshot: the current Tectonic PDF is 14 pages, and approximately 4,112 extracted body characters continue on page 13 before References begins. It does not meet the 12-page body limit; #65 remains open. PR #69 already recorded this correction in the paper audit. The producer record is no longer stale: PR #27 is recorded as merged and human-reviewed, but H1 remains pre-admission (0/9) with no registered commands. PR #71 merged the non-container stack fail-closed checks; PR #72 is under CI for binding its environment and accelerator-plugin identities into H1 registration. None of these replace a reviewed host/plugin pair or a formal NPU result.

2026-10-12 gate update: PR #73 merged; Python 3.10, Python 3.12, and wheel CI passed. Local full suite: 648 passed; Ruff, mypy, research-matrix validation, clean-wheel install, and Tectonic PDF audit passed. The public paper now has 12 total pages with the body ending on page 11; this creates space but does not supply H1-H4 measurements or anonymity. H1 remains 0/9 formal starts and deployment unregistered. Two visible 910B2 cards are sufficient for the first partial-worker-coverage topology, not for eight-card performance generalization; exact mutually verified host/Ascend-plugin commit pair and deployment commands are still required (vLLM Ascend issue #49). Gate remains open.

2026-10-12 gate correction/progress: #65 was automatically closed by wording in PR #73 despite unmet acceptance criteria; it has been reopened. PR #74 then merged a private Tectonic preview renderer (commit b1b0431; Python 3.10/3.12/wheel CI green). The preview passes automated identity scanning but not human anonymity review, and formal H1 remains 0/9 with no NPU request under the latest native stack. The required triton-ascend 3.6.0 wheel is internal-cache-only and unavailable from this container; the plugin verified host pin also differs from latest host main. Submission gate remains open.

2026-10-12 gate update: PR #75 merged a fail-closed loopback traffic-authority journal and real HTTP routing integration trace. Python 3.10/3.12/wheel CI and 653 local tests passed. This narrows the #60 exposure-observation gap but does not satisfy its real host/evidence/membership/formal-runner acceptance criteria; H1-H4 remain unmeasured formal studies. The submission gate remains open.

2026-10-12 go/no-go delta: PR #78 is merged and CI green. It demonstrates a separate loopback traffic process independently rechecking frozen Plan/host-journal/live-PID coverage before and after route open, with CPU fixture events and external HTTP requests. It does not satisfy the real-host ExposureGate gate: host events are test-generated, same-UID journal forgery is outside the slice's trust model, formal H1 remains 0/9, and no H2 real execution/H3/H4 formal campaign has been admitted. #60 and this submission gate remain open.

2026-10-13 H2 source-bound candidate advanced (no formal scoring)

Opened #88 from Manager main@374b255 with the exact KVCompress manifest and a KVCompress × Knorm case on vLLM/vLLM-Ascend 0.23.3.

Evidence boundary:

source commits: KVCompress 00cc78dc7f3491eecbc79c5068e29aed9f59afc3; Knorm c490cfbfd2372635e8e874c8d7ba866ca5c476fb
both sources wrap Scheduler.update_from_output, while declaring differently named exclusive resources
both wrappers preserve their captured predecessor, so static overlap does not establish incompatibility
the audited record is forced to oracle_label: null, status: unknown, runtime_effective: unmeasured
both installation orders remain required before independent labeling or H2 precision/recall scoring

Validation at PR tree c5f13996c36326c00283bc648d4c8dcae5d4183a:

targeted preflight: 5 passed
Manager full suite: 670 passed
Ruff check/format check passed
local generated audit SHA-256: 2cc0a4c3666fcc892faf471b3cdc20be83563b652973e45d4eb28ae50cd6a5eb
full-test log SHA-256: a2894bd3550513cacceeaaec24698518289fc364dd4f21b13f779b53e5bf13b1

This advances H2 executable case construction while H1 formal qualification gates remain open. It is not an H2 result, oracle label, or runtime evidence.

2026-10-13 real TP2 production-observer checkpoint

Manager PR research: add production formal host observer #90 merged at e2962ba7; runner now sends one canonical observer-captured correlation request only after the independent lifecycle fact succeeds. The production observer derives activation, invocation and coverage from the immutable process transition, deployment-owned host journals and live Linux identities; it accepts neither SUT truth nor a SUT causal ACK.
Real logs exposed a loader/runtime value distinction; PR research: bind runtime effective evidence by plugin identity #92 fixed effectiveness binding and merged at current Manager 9f075f8e after CI run 154 passed.
Exact candidate: Host b093ae0096a4ee801064f7a3673d42383e89f5c7, Ascend fd70a5c818363ee4357604e637e36fb52860ccca, MOD 9728ccd9df68c654aaf541bb7565c0bd3f85b983, Manager 9f075f8e70da574fb90bdd392cf7c7e424c75972; Manager wheel SHA-256 ec7d718a92361f77da53095547ae3ab407eabce9d471e6cc2e5f859bb69173da; installed-environment digest sha256:52cdc8b6356c57899c15bf1aa3e0dafeeac3192eb71a8fab4d72c90d59335aa0.
Real two-card TP2 preflight succeeded: health 200, completion 200/non-empty, dynamic membership freeze passed. After quarantining real worker ordinal 0 journal, production observer emitted effective-claim=true, one effect identity for ordinal 1, and coverage=0.5; cleanup proved no owned processes, port listener or NPU processes remained.
Artifact digests: result sha256:ed78d28566ba99a8e83468da3e0f37d2f982f34c09245553155ef3f7bf8119f2; observer result sha256:7f8afdbf894132922dd0990d541e3945ab44647ca4810e6283744794a3290455; process snapshot sha256:4cb4dbcf2dcfe796d1555401ba3e70c3196b434eaf2f1290a398bbcf3b7c5067.
PR research: record real TP2 production-observer preflight #93 records these machine facts. This run is explicitly unregistered-real-tp2-production-observer-preflight, is not a performance result, and contributes zero formal H1 starts. H1 remains 0/9.

Current non-fabricable gates remain: the GitHub App still returns 403 for Host and MOD blob writes, so their local candidate commits are not repository-reachable; the formal adapter registry is empty and independent admission reviews remain false. No historical, fixture, simulated or preflight evidence has been promoted to formal.

PR #93 passed CI run 157 and was squash-merged without waiting for human review. Repository main is now 0713c12c18d64c67775b23da617bba27707141b0; the exact Manager binary used by the recorded TP2 observer preflight remains pinned to source commit 9f075f8e70da574fb90bdd392cf7c7e424c75972. This distinction is intentional: #93 adds evidence metadata only and does not retroactively change the executed binary. Formal H1 remains 0/9.

Three-arm real TP2 observer preflight checkpoint (PR #94, CI run 161, merged as 5b046c91567281dd11f50a8166fd81617e8551e8):

Vanilla entry-points, manual integration, and ECPA each reached health 200 and completion 200/non-empty on the exact Host b093ae009, Ascend fd70a5c818, MOD 9728ccd9, Manager binary 9f075f8e tuple.
Each arm froze both host-assigned worker epochs before workload, quarantined worker ordinal 0, retained effective-claim=true, observed only worker ordinal 1, and independently computed coverage=0.5 through the production observer.
Each arm proved process, listener, and allocated-NPU cleanup.
Exact installed tuple: Python 3.12.13; vLLM 0.31.1.post1.dev164+gb093ae009.empty; vLLM-Ascend 0.25.1rc2.dev874+hust.20260903.4.gfd70a5c81; torch 2.13.0+cpu; torch-npu 2.13.0rc1; Triton-Ascend 3.6.0+git92513dba; CANN runtime 9.1.0; driver 25.2.1.
Device mapping is now explicit: npu-smi reports allocation IDs 3/6, while CANN worker logical IDs are 0/1. Successful launches inherit container visibility; explicitly setting ASCEND_RT_VISIBLE_DEVICES=3,6 is retained as a failed preflight with aclInit invalid-device evidence.

These remain unregistered functional preflights, performance=false, and formal H1 remains 0/9. No preflight was promoted into the paper's formal result tables.

2026-10-13 execution-ledger update:

research: prepare exact H2 install-order campaign #95 merged as 0cf02c2a (CI Reject invocation-only evidence at the formal traffic exposure boundary #164): real exact-wheel, two-order H2 installation preflight; runtime and oracle remain unmeasured/unreviewed.
research: freeze H1 registration commands and exact tuple #96 merged as 2ea7dfd5 (CI research: qualify six real TP2 worker launches and three owned-worker faults #166): executable H1 three-arm/five-source/nine-start registration candidate, three successful activation probes, atomic transition dry-run, and exact Host/Ascend qualification report.
research: freeze fail-closed H3/H4 campaign intake #97 merged as 646d1758 (CI Correct the overlooked H2 conclusion counts with generated macros #167): fail-closed H3/H4 formal campaign intake (225 H3 starts and 36 H4 starts required by the frozen matrices).
Combined local validation: 725 passed; Ruff, mypy and research-matrix checks passed. Tectonic-only PDF build: 12 pages, zero automated audit errors, SHA-256 0c0deb119eaa15e13362c566bfdf3d85c4bfafaa600433f1ff10335402d485b8.

Formal H1 remains 0/9. Host b093, MOD 9728 and Ascend fd70 are still not remote-reachable refs; Ascend PR #50 remains open; independent admission assertions are unset. The three-arm two-card observer evidence remains unregistered preflight and no performance result has been claimed. Current go/no-go remains NO-GO.

Additional #60 progress: PR #98 merged as 69a79f8d after CI #170 passed. A real loopback authority path now binds route state to generation, membership epoch, target-set digest and process epochs; worker replacement invalidates coverage and closes traffic while external services remain alive. Evidence is explicitly preflight/formal=false/performance=false because issuer events are still test-generated. Submission go/no-go remains NO-GO.

Further ledger update:

research: bind H1 local source archive receipts #100 merged as 0d7cdacd (CI Publish real nonce-bound native API and two-rank NPU upload evidence #173): exact local Git bundles and receipts for Host b093/MOD9728/Ascend fd70; atomic H1 transition dry-run strengthened. Remote reachability and independent admission remain false; H1 is still 0/9.
research: record legacy H2 runtime preflights #99 merged as d45f3fa3 (CI Require a new long KV challenge and portable metadata/upload evidence #174): two exact H2 legacy source-pair import/admission preflights. Both plugin orders registered wrappers, but KNorm remained inspect-only and was rejected before server start; runtime effectiveness/oracle/performance remain unmeasured.

No preflight has been promoted to a formal or performance result. Go/no-go remains NO-GO.

H1 execution update (2026-10-13 11:01 UTC): PR #101 is merged at f3dee542 with CI #177 green (741 local tests + Ruff + mypy). The Manager now owns the vanilla/manual launch shim, so the candidate no longer needs unpublished Host b093 or MOD 9728 launcher changes; the intended reachable heads are Host 973d9ef5a and MOD e343fc5.

Formal H1 remains 0/9: no preflight is being promoted. A clean wheel for remote Ascend PR #54 head 8735840 is currently building, after which the stock Host/MOD + merged Manager stack will run a real Qwen2.5-7B eager TP2 vanilla launch on assigned NPU 3/6. If that launch succeeds, the same stack proceeds through manual and ECPA arms, then registration and the frozen 9-start order. PR #50 head alone is not usable because it imports absent fla_npu; #54 contains the lazy import needed for non-GDN Qwen but is being validated against the exact runtime now.

Concrete H1 hardware update (2026-10-13 11:46 UTC): the exact reachable stack now passes real Qwen2.5-7B eager TP2 qualification on assigned NPU 3/6 for all three arms.

Sources: Host 973d9ef5, MOD e343fc5, Ascend PR feat: compose hash-bound StateAxis MOD plans #54 head 87358402, Manager main b734a923, Triton 92513dba.
Vanilla: health 200, real completion 200/nonempty, cleanup proven.
Manual: health 200, real completion 200/nonempty, cleanup proven.
ECPA: canonical formal-run -> exact Python ELF -m vllm.entrypoints.cli.main target, health 200, real completion 200/nonempty, distinct worker epochs and effective host evidence, cleanup proven.
Qualification receipt: /root/ecpa-audit-20261013/pr54-stock-tp2-qualification-receipt.json, sha256 846a4260e607543db547ba0fe22ef7f9a17f559c459798b537d0e92ecefee5f8.

A failed ECPA attempt using the ecpa-host-launch console script as the Manager target is retained: Python multiprocessing reused Manager fd 3 and deadlocked during spawn. The canonical Python ELF + -m target fixes that without weakening the gate.

These are fresh real qualification runs, but still not formal H1 starts and not performance results. H1 remains 0/9 until the updated registration candidate, producer admission, and atomic official registration land. PR #103 is green and is being amended with this qualification plus the corrected ECPA target before merge.

PR #186 merged as 8c75f06 after CI 373 passed all three jobs. Its byte-bound portable archive independently reproduces both strict-task PASS responses while retaining the original HTTP-intake-window rejection, all late records and cleanup evidence. This is a finite partial diagnostic, not formal H3/H4, KV tensor equivalence, attention consumption, full quality or a fresh-nonce qualification. The prospective-clock implementation in #185 is being tested only in a new independently frozen tuple; no old evidence was upgraded.

PR #189 is merged at 5cffbb4 after all three CI 379 jobs passed. Its stdlib portable replay independently verifies one new real TP2 metadata observation: exact HTTP 200 task, 1201 prompt/77 completion tokens, all 160 original rows (one native API map, two materialized projections, 156 NPU uploads), the source-issued final-prefix ACK contract and owned cleanup. Both late intakes are retained. Archive SHA256 996a889521ef81d71802824720efa1e8421b3cf96f136f2891923cdd97b333ce (201 regular members). The standalone oracle precondition was 76 tokens; it is distinct from actual usage. Scope remains finite metadata only: no formal H3/H4, no tensor equivalence/attention/full-quality result, no loss/duplication or overall-objective claim. Original #186 partial evidence stays unchanged. Next tensor tuple is separately built and installed; its typed mixed-journal/clock integration needs its own actual CPU source contract before the sole owner launches a fresh GPU cohort.

Archived execution ledger snapshot (2026-10-14)

This preserves the complete prior ledger before its issue body is compacted. The issue body remains the current authoritative status. Source body SHA256: 62a8e41c26b60a68a58107d2923883ff3e769d9a28d68532843a6b3eab4c29fc.

当前执行总账（2026-10-14；Manager `f87bb29f3c5322d65d732055df9ea78f16d577bb`）

NO-GO；H1 正式 9/9，预防假设 falsified；H2 独立计分子集已纠正为 n=4（原 n=5 含预诊断报告消费 case）；H3/H4 正式启动均为 0。 下方旧 main、0/9、准入状态保留为历史，不覆盖本节。

项目	当前可采纳证据	仍缺
#59 / H1	r5 三臂×三次、五注册来源、formal batch PASS；各臂 false-effective=1.0、process coverage=0.5	ECPA 预防假设被证伪，不证明真实流量保护
#60 / real gate	#144 真实 Qwen2.5-7B TP2 + 独立 HTTP authority：worker invocation coverage 0.5 时 open 被拒，HTTP 到闭合前驱返回503；恢复原始journal后候选真completion200；再次证据丢失关闭route并503。原始Host journal/proc/HTTP/authority chain及四次失败均保留，95文件归档；便携离线复算PASS	QUALIFIED_NONFORMAL / invocation coverage only；不是 runtime effectiveness 语义、H1/H4/performance，也不是 formal producer registration
#63 / H2	原n5中的external-authority case已审计：prediagnosed ownership_conflicts直接输入provider；with report compatible=false，移除仅该报告则unknown，精确provider源码复算	排除该报告消费case后独立子集n4、TP2/TN2/FP=FN0；audit四文件/真实对照/4项聚焦检查（3负测）已由#160合并，历史raw/oracle/prediction保留。完整H2仍缺来源/冲突表面；PP2×TP2 cell未运行
H2 compression	两加载顺序真实TP2、1201 semantic→1024 physical、两个worker ACK	QUALIFIED_NONFORMAL，frozen_utc不准确；不计score/performance/quality/correctness
#61 / H3	#158 真实双Qwen7B TP2 finite window：native SQLite prepare→SIGKILL→新coordinator恢复；60冻结single-attempt请求跨完整故障/恢复窗口，deadline lost0/admissiondup0/reused response IDs0；另7阶段marker。186raw+一次失败CPU预检分别归档，root独立便携复算PASS	QUALIFIED_NONFORMAL / ECPA-only / before-effect gen0；execution duplicates/request duplicates/full objective未知。不是匹配三臂、candidate曝光后回滚、正式H3或性能；Host未合并。共同worker runner已完成#159原生身份交接；r1真实六次启动RPC/lifecycle通过但文本正确性失败；#166封存r2六次严格文本/三次owned故障资格通过，仍不补正式计数
#62 / H4	r3绑定484d6fd，清除继承ASCEND_RT_VISIBLE_DEVICES；13/13 prelaunch及offline验证PASS；真实issuer fail closed	正式0，无性能结果；Host379a0ad未远端可达/合并
#65 / anonymous artifact	#176同步137raw真实native transport，当前H2 n4与有限H3窗口的公开/私有匿名Tectonic PDF：14页/12正文、自动audit0errors；root独立核验当前source/summary摘要匹配	间接身份/视觉人工检查未自动证明；整体科学gate未闭合

已合并：#140慢POST完整body后再准入（旧四负例200→新503/503/503/400），CI274；#141匿名渲染/隐藏PDF身份扫描，CI275；#142 H3/H4 runner，CI278；#143真实Host上下文不计目标coverage，CI279；#144硬件实跑原始证据与防篡改验证器，CI282。均按精确head在CI绿后合并。

此前#60实跑source为 484d6fd16180065784729f23d2abd85f229f5049，Host 379a0ad35e9de6928e3481d375692204b0dee6e4、Ascend 873584026f8a683ac73523f15127569e9f6ab34b；实际wheel/安装Python字节、14模型文件、Plan/launch/请求在启动前重新核验。原始归档 SHA256：33adce307dcdb533c548e89580eb5db300625d5cadf9010e30f07391f7114de9。从合并main运行 python -m experiments.exposure_gate.qualification_verify --package experiments/exposure_gate/artifacts/real-invocation-gate-qualification-20261013 可复算有限结论；不需要重放模拟数据。

精确设备结论：容器仅暴露physical3/6，runtime logical0/1；实际tensor allocation/sync/readback探针PASS。显式ASCEND_RT_VISIBLE_DEVICES=3,6导致无可用runtime设备，已保留失败并修正H4输入。两卡足够当前TP2，卡数不是Host登记或H3适配阻塞。

Host发布仍被App仓库授权阻塞：installation160328991未选择vLLM-HUST/vllm-hust，403；容器无Git写凭据。Ascend#50仍open/dirty/CPU CI red，本地修复未发布。下一关键路径：发布/CI/合并精确Host→正式#60登记与匹配实验；并独立完成真实H3各臂prepare/fault适配→H3/H4正式执行。不得再称H3只剩权限阻塞。

本轮清理：NPU3/6无进程；8000/8187/18187/28187连接拒绝；无自有vLLM/EngineCore/proxy残留。目标保持推进，#60–#66保持open。

持续窗口执行工具与模型论文（#153–#154）

paper: independently recompute bounded two-TP2 native crash qualification #153（af987a85，CI301）生成器独立复算r4四份归档、156raw、三次失败与null指标，论文有限报告两TP2/七marker/nativeSQLite kill/restart。仅Tectonic，14总页/12正文/audit0errors。
research: execute and verify finite crash-window HTTP client traces #154（3a559522，CI302）可执行60-request continuous client与独立raw authority join；绑定deadline、request/admissionID、原始responsebytes、backend listening PID/epoch及generation。CPU真实SIGSTOP/CONT负例检测13次deadline交付失败；backend execution duplicates未知。CI首次3.12既有fixture自然退出0/signalNone竞态失败，完全相同head重跑该job后通过，未改production或冻结源码。
后续完整two-CPU/nativeprepare SIGKILL/restart/60请求预检r2 PASS（CPU_ONLY，非模型结果）；真实Qwen completions prompt/tokenizer/oracle在NPU启动前冻结。下一真实双TP2持续窗口运行已开始推进，结果未定，不补正式计数。

当前发布检查点（#157–#158）

research: add CPU-qualified owned worker crash and common full relaunch runner #157（d8983955，CI309）补充共同worker SIGKILL/full-relaunch工具：真实CPU三臂3/3清理及15检查通过，支持Manager监督器的嵌套SUT sessions；仅CPU-qualified。实际Manager原生身份交接尚需适配，不能把外部reserved env指定身份当native mint；原manager-crash cell不动。
research: qualify finite real-model delivery window across native controller crash #158（49f1c153，CI311）真实模型有限交付窗口证据已合并：raw archive SHA256 42d63eb7213b744c9e5e73c9de6b13af81d19f7c1b264f548f15ec693ea69f7f，186成功raw、失败chat-CPU预检单独归档；运行source 3a559522，后续分析source独立记录。完整window直到client.stop始终gen0，重hash但在post-proxy插入candidate exposure仍语义拒。root从远端精确PR提交解包复算PASS。
复算：PYTHONPATH=src:. python -m experiments.formal_campaign.h3_model_client_window experiments/formal_campaign/artifacts/h3-model-client-window-20261013/raw.tar.gz。输出明确formal=false/matched_three_arm=false/performance=false/fullobjective=null，有限60请求deadline lost0不是backend exactly-once。
当前用户原始 /root/extension-manager 工作树干净；105 Manager worktrees审计留存，四个脏树保留原样而未重置。成功实验进程/端口/两卡均已清空。论文生成器、私有匿名Tectonic产物及Manager native handoff继续推进，不等待人工review；正式H3/H4仍0，整体NO-GO。

H2 独立计分纠正（当前审计，优先于历史 n=5）

实际 source-matched provider 对照已证明 external-authority-production-stack-keda 的旧预测将预诊断冲突结论作为输入；只删除 ownership_conflicts 后得到 compatible=null，而不是独立检出冲突。这是报告消费资格，不能算 conflict detection TN；unknown也不能被旧collector的else分支当admit。当前独立子集排除此case为n4/TP2/TN2，旧oracle/predictions/原aggregate全部保留。Root已冻结audit commit7889512、便携真实对照与防再计分负测；#160审计已合并，#162生成器、公开稿与新私有匿名Tectonic产物已同步正确数字。H3真实60-request窗口不受影响，正式H3/H4仍0，整体NO-GO。

原生身份交接及 H2 独立计分修正（#159–#160）

research: observe native Manager phase bindings through private owned handoff #159（0a6fdbc7，CI313）：opt-in Manager native mint→private Unix SO_PEERCRED/源四hash/ACK→原supervisor，所有reserved env拒绝保持；实际CPU三label完整CLI r2=3/3clean，两份fresh native ECPA UUID；r1 teardown race失败完整保留。不是模型三臂、不是preregistration或正式H3。新exactManager wheel与独立venv正在核验，然后推进真实6次backend启动/3次worker fault。
research: exclude prediagnosed H2 reports from independent detection scores #160（4c4193e3，CI315）：external authority输入报告消费case从独立conflict detection分母排除。当前n4/TP2/TN2/FP=FN0，source-matched实际provider with-report=False / without-report=None；unknown不是admit。4聚焦checks（1positive+3negative）通过，旧oracle/prediction/原aggregates完整保留。PYTHONPATH=src:. python -m experiments.real_mod_composition.h2_scoring_input_audit可实际复算；论文/生成器/匿名Tectonic现在按新审计同步，旧draft不作新sourcefinal。
Host发布ready bundle/patch/source/wheel和PR正文已准备；fresh权限显示用户Host admin/push TRUE，但实际Host create_blob仍403 notaccessiblebyintegration，shell/SSH亦无可用写凭据。科研与实现工作继续；不弱化正式merged-source gate，不等待人工review。

三臂真实 worker 故障进展（#161–#163；当前运行检查点）

#161内部hostile review已合并，CI318通过；明确强manual comparator、独立semantic obligations与完整H3/H4仍缺，整体NO-GO。
Correct H2 independent score and bind paper to finite H3 delivery evidence #162（13b791a5，CI319）论文从真实raw复算H2 n4和60请求有限窗口；53检查通过，仅Tectonic公开/私有匿名14总页/12正文/audit0。不新增正式结果。
fix(research): require frozen exact response and stop reason in worker qualification #163（86043ef4，CI322）共同worker runner加入启动前冻结的exact-message-content与finish_reason=stop判据；HTTP200但错误文本立即失败并留raw，32聚焦检查通过。
r1真实三臂各首次/故障后全重启共6次TP2启动、3次自有worker SIGKILL、fresh PID/epoch与清理均完成，但六份输出均未满足请求标记：只证明RPC/lifecycle，不证明文本正确性，不计正式H3。原始失败保留，不改变其输入或判据。发现缺HOME/TRITON缓存根导致Python/C++缓存解析不同及launcher警告；尚不把日志共现当完整乱码因果证明。
r2独立冻结runner aef46c09、实际Manager 0a6fdbc7 wheel/独立venv、明确缓存与允许环境；三臂使用同策略的每臂空缓存首次启动/同缓存重启。当前root已独立读取三臂全部六份原始response：6/6次真实TP2启动返回严格标记ECPA-WORKER-READY/stop/9tokens；三臂首次/故障后重启result均通过且cleanup_errors=[]，3/3次owned worker SIGKILL。owner已封存最终设备/端口清理原始记录：双卡no-running、29281–3关闭，30Host/Manager身份及8owned sessions无live。三臂封存后继续独立整包复算；不把短标记正确性称为完整质量、正式H3或性能。
Reject invocation-only evidence at the formal traffic exposure boundary #164（e17349e9，CI324三jobs全绿）：复现formal authority仅凭invocation coverage就authorize的缺口后，formal traffic path现缺可信semantic producer就failclosed；普通v1和真实95raw历史qualification仍兼容。root实际复算archive33ad…4de9，六条semantic绑定边缺失，formal_traffic_admissible=false。此修复关闭错误正例，不声称已完成semantic正例；正例producer接口继续推进。
本实验是共同worker-crash/full-relaunch补充资格，每臂仅一个故障episode，不能替代原manager-crash baseline N/A cell、正式多episode矩阵、authority exposure/rollback、完整lost/duplicate/objective或性能。H3/H4正式仍0；设备由当前实验独占，不能引用旧清空检查当当前无进程。

封存发布与真实语义接口（#165–#167 已合并）

research: qualify six real TP2 worker launches and three owned-worker faults #166（7a91e71d，CI327）：r2三臂6次真实TP2 generation启动、3次owned worker SIGKILL/full-relaunch，六份rawresponse均exact ECPA-WORKER-READY/stop/9tokens；fresh两rank/epoch、nativeManager mint及30Host/Manager身份/8sessions清理独立核验。175文件原始包SHA256 5202308dfe08cae258e222d60b527c8c0840872f218f26fb72d49bf3dc032173；root从合并main便携复算PASS。r1六次RPC生命周期通过但文本失败，97文件SHA256 c192cbf3d3d93744d742882013452720ca14bfd765f795b2d6d0da0fbad6df6c完整保留；含会话字段的私有CPU输入不发布，仅原SHA与排除声明，不冒称公开CPU字节完整。
复算：PYTHONPATH=src:. python -m experiments.formal_campaign.verify_h3_worker_real experiments/formal_campaign/artifacts/h3-worker-real-20261013/r2-manifest.json。26聚焦检查和独立重打包/rehashed负例通过；修复rank1错phase/原生receipt改身份/terminalobserver只检查最后journal等分析缺口。APIcreated只作可信时钟一致性检查，相同短prompt无独立nonce；不是challenge-bound authority、通用生成质量、正式H3、完整lost/duplicate/objective或性能，后三项仍null。
Add CPU-review typed producer for worker Host block-table projection #165（41dfa446，CI328）：精确00cc78 source hook后的typed CPU block-table projection候选、私有durable writer和ACK消费者，44聚焦检查；实际并发reader可在dirfsync前读raw，但无匹配publicationACK必须拒绝。ACK认证source channel尚未实现、未注册formalproducer，#164正式流量guard保持关闭。CPU投影不是GPU上传、KV tensor等价或model质量，不能用此候选关闭[OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership #60。
Correct the overlooked H2 conclusion counts with generated macros #167（3be1eac0，CI329）：root灰阶逐页阅读发现#162结论遗留“two admits and three rejects”，现用生成TP/TN/n宏纠正2/2/n4。公开与新私有匿名稿仅Tectonic14总页/12正文/自动audit0；root独立核验private manifest当前main.tex与summary摘要一致、identity与commitidentifier扫描均0。此自动检查不证明间接匿名性或完整视觉审查。
当前实际npu-smi info确认physical3/6无运行进程。下一新资格批次独立冻结native external→internal request映射（Host随机化internalID，不能猜suffix）、每rank真实GPU table upload/barrier观测、authority challenge与原始response join；不改r2旧source/wheel/nonce协议、不追溯晋升。H1正式9/9且falsified，H2n4partial，H3/H4正式0，整体NO-GO，目标继续。

原生请求关联与收集通道（#168–#169；尚未硬件资格化）

research: prepare native request-ID mapping and NPU table-upload hooks #168（3047d6e6，CI333全绿）：精确Host379/Ascend873 native patch，实际external→internal随机ID映射、真实upload后的current-stream barrier与GPU前缀readback；5CPU contract/check/patch tests。不是GPU结果、KV等价或完整质量。
Add source-peer native collector and durable ACK channel candidate #169（fc9f10b0，CI335全绿）：32聚焦真实CPU/socket检查；API/两个rank/authority四独立进程、SO_PEERCRED/PID-start/boot/session/cmdline/source冻结、durable rawchain/ACK及成功fsync后推进prefixseal。每个decode fresh upload都保留，严格递增/重放拒绝/有限cap，不把重复报告当模型失败；两rank计数不随step增加。ctx bootstrap缺失则non-producing，不以普通RPC当native证明。
Root实际构建Host bb5218f7ca7ebca5eba8cbf7255335c7e425acbd wheel，SHA256 7e68aa929f052502ceaa994950a9da9975c3ba6c88e0c6e8a8d31e5416d45be0，native module/InputProcessor源码字节及RECORD核验通过。随后在新clean Host 34f6c3241a0a409ce0d302c5d53d9ea752feff95 接入bootstrap并成功构建另一wheel，未修改旧wheel。新独立venv已完整复制（非hardlinks）并独立安装Manager3be1实际新构建；39 packaged runtime Python与该source完全一致，wheel hash与0a相同是runtime代码未改变，不用hash推断唯一commit。
Ascend新clean fcbb827af 正在真实CANN9.1/custom-kernel编译，唯一既有build handle持续推进；无新硬件结果。输入SOC=ascend910b2，但实际OPC存在Ascend910B1 family recipe；真实toolpath/生成variant分列保存，不称all kernels B2专用，也不把旧cache命中伪称fresh编译。
Root portable审计又复现#169离线缺口：live拒CPUdevice/qualityTrue/wrongscope，而旧offline verifier在重hash整链/prefix后仍计transport。三实际CPU/socket反例已复现，下一source独立修复shared pure predicate/真实acceptclock；旧无clock保持legacy unverified，不编造时间，也不回写169旧freeze。在新source/helper/Host轮冻结前不执行新NPU资格。
新request runner真实HTTP+三peer多decode+post-authenticated-prefix CPU pipeline已跑通，但待上述collector修复冻结。Header/body同clientID→实际chatcmpl外部ID→native随机internal映射，保留默认随机化，不猜suffix；缺rank/nonce/mapping/prefix保持失败或unknown。
新阶段仅native Host request/upload/challenge接口；generic Host GPU upload不能替代KV扩展真实效果。后续真正compression obligation仍需165 actual pendingprojection/anchors/destination→其后matchingGPU witness→request/response关联，当前semantic_obligation_satisfied仍unknown，#164正式guard保持闭。Fresh Host create_blob实际仍403 Resource not accessible by integration，source发布正式gate没有解除；两卡不是阻塞。H1正式9/9且falsified，H2n4partial，H3/H4正式0，整体NO-GO。

原生 collector 验证修复与可执行请求链（#170–#171 已合并）

Apply the same native fact predicate to live intake and portable evidence #170（0a7f81d6，CI338全绿）：三实际CPU/socket重hash反例复现旧离线漏洞后，live与offline共用同文件pure predicate；真实start/acceptclock、exactfields/device/null-quality/rowblock/type/顺序/age均重算，旧135无clock链保持legacy unverified、complete transport=null。42聚焦检查通过；生产collector最终SHA ee62c51444acde7b813c33ea4c2b20ab07248ea050753199cbfc79d73f1c5075。首次CI337的旧有限窗口fixture错误选择late200，失败log保留；新head仅将该负例绑定actual on-time200，不改deadline或生产collector。
Freeze phase nonce requests and verify native transport joins #171（ea843034，CI340全绿）：实际执行CLI、独立128bit phase nonce/clientID、source-only actualAPI外部ID oracle、singlePOST、原始HTTP/descriptor/statusbytes保留、前后真实SO_PEERCRED+实际cmdline与fsync-prefix、native实际内部ID/两rank/acceptchronology联结。14CPU target及与collector联合46检查通过；actual3peer/collector/HTTP进程多decode路径和missingrank/staleseal等拒绝完备。当前CPU/interface only，没有新NPU结果，KV效果/质量/完整恢复仍unknown，正式guard保持闭。
Root新clean Host a4bdbe74c1bdc1228e3cc19c61887225d35f16f8 genuine wheel SHA256 a55e4e98b44f789fed78b87ed826ba33ed5cf70ac0d385f6e2c8c644c4c67eb7：InputProcessor/nativeobserver7397/collectoree62/bootstrapb346与源码字节完全一致、RECORD0errors、sourceclean；已装入独立copy venv并再次比对installed bytes通过。此前bb和34f轮作为未运行的构建阶段保留，不改写它们。该新Host仍local/unmerged，正式source gate未解除。
Ascend fcbb827af 的同一fresh CANN/customops build当前634/651并进入installer/jsonpack，具体handle由owner继续监测；在最终native ELF/wheel/安装字节审计之前不以旧873替代。真实OPC family含B1，不能宣称所有binaryB2专用；后续设备实际验证仅支持测试范围。
下一NPU资格只冻结最终新Host/Ascend/Manager/installed helper/model/allow-env/cache tuple，启动后从真正nativehandoff/Host记录冻结动态IDs、再发唯一nonce请求；不会预填PID/epoch或由RPC推断nativejoin。另独立KV candidate正在实现00cc真实pendingprojection aftereffect（anchors/destination）→同rank后续matchingGPU upload→actualrequest/response；普通早期Hostupload不满足该predicate，generic171接口不可替代KV效果。
本轮有实际源码、构建和CI状态改变；H1正式9/9且falsified，H2n4partial，H3/H4正式0，整体NO-GO不变。

最新新 wheel 安装及真实 native 启动失败（2026-10-13 23:18 UTC）

Ascend fcbb827af84f793939bf03d01a1dfe0338a0164c fresh customops build已完成：wheel SHA256 be5a69b8dc2dd9a77144657a6d394aa7079e95054aef54dda41f260b0af6eb86，750源码Python/7个AArch64 ELF及RECORD检查通过；159新编译cache SAVED、0 HIT。新独立venv安装757文件逐字节一致、196包venv-only pip check通过；原资格环境未改。
新 Host a4bdbe74 / Ascend fcbb827af / Manager native runtime tuple、7 wheel、14模型及20source（41输入）已冻结并独立重新hash通过。r1实际启动Manager native mint/handoff、真实两rank Qwen7B TP2模型并完成动态Host成员登记；没有预填PID/epoch。
r1 collector拒绝继承setgid的目录（实际mode2700，要求0700），readiness EOF导致owner失败；未发nonce HTTP、未收集native upload资格事实。完整原始失败保留在独立r1目录，cleanup无错误，终态NPU3/6均无running processes。不是成功资格、正式H3/H4或性能。
下一r2修复新private目录的实际mode及collector启动预检，使用新冻结owner/recipe；不改r1冻结件、raw或判据。当前generic native request/upload scope仍不能证明KVCompress效果；独立00cc source-bound实际projection→后续matching upload候选继续推进，#164正式guard保持关闭。H1正式9/9且falsified、H2n4partial、H3/H4正式0、整体NO-GO。

KV 效果候选合并与新 r2 冻结（#172）

Add source-bound KV metadata to native upload candidate #172 已按exact head 39b4affd636dbba99d2c1e00580e8e7215ffaa1f 在CI342三jobs全部SUCCESS后合并为 e5a4997c1d8f8904cb67409c0f1d8c32c20bab87。58聚焦检查/Ruff通过：新schema仅允许真实00cc provider效果后读取request.block_ids、实际CPU blocktable、active anchors和runtime threshold；关联实际API请求并只接受同rank/request/plan/launch、投影后matching destination-prefix上传。早期普通上传全部保留但不满足KV谓词。当前仅CPU/source candidate，KVtensor/attention/完整质量null，未解除formal guard。
r1完整真实TP2启动失败保留；独立终态核API/两个rank相同身份均gone、两owned sessions空、29493关闭。新r2 freeze及sourcepreflight PASS，直接执行冻结owner.source.py；collector父目录实际0700/uid/devino及同inode先验门槛、EOF具体错误修复已在CPU真实三peer/collector/HTTP完整路径预检通过。新nonce/cache/recipe保留独立，7wheel/14model/20source未与新KVcandidate混用。
r2的实际硬件请求结果尚未产生；本轮使用generic ee62 collector，不把#172尚未新wheel化的KV候选称为运行证据。独立新Host/KVCompress clean source和genuine wheels继续构建，当前运行环境保持冻结。H1正式9/9且falsified，H2n4partial，H3/H4正式0，整体NO-GO。

真实 native request/upload 第二轮终态（2026-10-13 23:27 UTC）

r2实际已通过并清理：冻结owner 6988b703…5b27c9直接执行，fresh recipe SHA256 5bed99bdc705299d909da94895c24386f89a98a9be79f5549f2e194765758a7d；同一真实TP2服务对singlePOST返回200，exact冻结nonce文本、finish_reason=stop、39completiontokens。response原始SHA256 751ba10e8217c053ffe35f54b3c1d93b30a6e40b509ae9fa50b9e2ce6180250f，request.bin与冻结payload逐字节/解析核验。
原生API PID851014产生external→随机internal实际映射；实际NPU worker PID851363/851364分别physical3/6、各40条source-owned upload/barrier/readback。完整raw82行（start+mapping+80uploads），SHA256 436b1c6ca67d7a9cfae02467861f62ef81d61398556574b1066fea369cd3f1d9；真实SO_PEERCRED、source/epoch、同runtime请求、acceptchronology及fsync ACK prefix(sequence82)独立联结PASS。root使用运行冻结ee62源码重新verify_journal PASS；新172 analyzer会正确拒绝旧ee62 source，不去除source等式。
实际kernel/env与冻结config一致；privatecollector目录0700。独立晚采样确认所有captured自有进程身份gone、sessions空、29493closed、physical3/6无runningprocesses，cleanup_errors=[]。r1的2700拒绝失败raw仍独立完整保留，不拼接为成功。
REAL_NATIVE_REQUEST_UPLOAD_TRANSPORT_NONFORMAL：实际硬件transport=true，与producer候选注册classification分开；KV MOD语义、KVtensor/attention消费、完整质量、lost/dup/fullobjective仍null，formal=false。当前是KVmaterialization/generic upload，不是KVCompress效果正例，不关闭#60或正式H3/H4。正在封存portable source-specific verifier/成功失败原始归档并走CI。
新KV candidate Host 89ee8c07 wheel SHA256 f575fac91bf30059210b185bd6bcbfab32f42bb757c29a605fd3a57a06937aa3、KVCompress d30e956a wheel SHA256 8f53c169e641b1f5569584ab862d3dfc47f18693272b63ca55f7d5c53b11abca在另一个独立venv构建/安装：2652HostPython+22KVPython及Ascend757Python/ELF exact/RECORD通过，197包venv-only兼容；当前r2冻结tuple未改。新的KV recipe/runner正在补实际tokenizer1201token与selected-phase双rank投影→后续prefix predicate，尚无KV硬件结果。

原始证据发布检查点（#173）

新 PR #173 head 2282130c87d705dd74656ccc5024d4a1abdf2245 封存137文件成功/失败raw，archive SHA256 b04787939bd54931e34e05beb2ca71e0a2df5df55846ecf78917783d654acf73；exactee62 source-specific portable verifier实际CLI PASS。11检查包含10个完整rehashed归档反例；独立审计12原始链反例和9归档反例全部拒绝。修正draft对非200正文与不完整清理范围的错误接受，R1/R2均核真实owned session/PID/port/NPU终态。CI344尚进行，不宣称已合并。
KV新schema runner67聚焦CPU检查通过，真实tokenizer API预检发现BatchEncoding返回类型与预期plain IDs不符：保留失败、显式return_dict=False按真实API修正并重新CPU核；尚未新KV NPU实验。另H2 QuantizedKV-cache/KVCompress新sourcepair先验oracle unknown，CPU attempt1留JSON但最终SIGSEGV(-11)，不计成功/计分；正在用准确CANN import closure作新attempt诊断，旧n4不变。不得把这些准备记录提升为formal结果。

#173–#175 已合并与下一真实 KV 校准

Publish real nonce-bound native API and two-rank NPU upload evidence #173 final head 2f3207751207a559668d8c836cf1b9a5316acdb6 / CI346三个jobsSUCCESS，精确squash merge 1744b63297830a9bf848ea3cb229351a5ac8a69d：R1/R2共用实际registered peer/source/kernel/Host invoked绑定；独立发现的R1 foreignworker+matchingterminal反例现拒绝。12聚焦检查，raw137文件SHA b047…acf73未变；root从合并main实际portable CLI复算PASS，两rank各40条真实NPU上传、nonce/stop/39tokens及sourcechronology/durableACK/两轮清理全部有限联结。不是KV效果或formal。
Require a new long KV challenge and portable metadata/upload evidence #174 final head c28f340a2d74a362ee5f6c427b6efddf1aa62e10 / CI345三jobsSUCCESS，merge 4aa92d5dff15d4a080daa90464a378f6440e5f8e：新KV opt-in真实tokenizer1201输入/完整tokenIDs/模板及实现/7资产hash、selected-phase相同actualruntime的两rank投影→后续matching prefix/ACK及nonce/response联结；67聚焦检查/真实CPU tokenizer预检通过。旧generic默认兼容，不能被普通prefix满足KV谓词。新NPU KV效果尚未发生。
Retain real QuantizedKV/KVCompress CPU checks without expanding H2 scores #175 final head 35ecad7f8f28dc0df9af6cdbc30e93c2efbeb5cf / CI347三jobsSUCCESS，merge 423418ec6868b8494b878e8b6a4ac69b496a0792：QuantizedKV-cache+KVCompress真实CPU provider两成员/两声明顺序检查；67raw SHA256 fd2f579b258ad7810917328e63c03dd08e38c9ee13ab67301ba5fc2a606293eb，首次SIGSEGV原件保留，第二次准确CANN closure exit0。root从合并main实际portable复算PASS，oracle unknown、score=false/n4不变；两个Host import文件只postrun快照，prelaunch closure partial，不追溯修freeze。
下一cohort未冻结的独立新KVvenv已移除旧KVmaterialization（卸载前metadata/可逆原wheel/日志保留），普通plugin/core3与selectedKVCompress显式控制、arctic未授权插件过滤；已封r2环境不动。旧校准产物实际CPU weights_only metadata确认14B（48层、queryheads40/KVheads8），当前7B为28层/queryheads28/KVheads4，不能凭改名复用。唯一设备owner正在准备独立真实7B calibration源码/配方/输出，完成后才冻结新的KV效果输入。校准不等于KV正例，H1正式9/9且falsified、H2n4partial、H3/H4正式0、整体NO-GO继续。

当前论文与真实 7B 校准产物（2026-10-14）

paper: bind real TP2 native request/upload transport qualification #176 head 67d0eb1a477800a874d1a9570697b2688d4d639c / CI351三个jobsSUCCESS后精确合并为 be909c9c8cdd0ae34b1b148d7e8f28c19ccc8c5b。generator实际复算Publish real nonce-bound native API and two-rank NPU upload evidence #173 portable：137raw/1mapping/80prefix(每rank40)/1nonce/39tokens/1preHTTP失败及两轮清理；有限transport边界写入正文，KVeffect/tensor/attention/fullquality/objective仍unknown，H2n4/TP2TN2/formal0/NO-GO未改。51聚焦检查/Ruff/matrix通过。只Tectonic公开及新私有匿名PDF均14总页/12正文/自动audit0；root独立核private source与当前public main.tex及generated evidence-summary.tex字节摘要匹配，公开PDF第10/12/13页灰度实际视检无截断，结论2/2/n4、参考文献从13页开始。此有限视检不宣称完整间接匿名性已证明。
真实7B standalone HF前向已产出新校准数据：独立freeze recipe SHA256 020b42ed2b0024a161e6de594aed9e8b9986c496f82a7952aec94e3675738c0e，真实Oct14时钟、4096tokenIDs、14模型文件fullSHA、8wheel及31源码、Accelerate1.15.0 wheel/84installed.py exact。source shape28层/28Qheads/4KVheads/head128；源指纹仅name/size/mtime与另绑的weightsfullSHA明确分开。
fresh stats SHA256 d8cc47fbdae931785fcbed403fcc688d1b12000cee76e591622c7d70e3b254d7（655783bytes），实际CalibrationStats.validate及_validate_artifact对当前7B/fingerprint/input4096均0拒绝理由。原runner终态exit1是后置diagnostic找不到npu-smi；原failure/无result/leafexitraw未知保留，不重写成PASS。晚采样通过真实绝对路径核自有session gone、3/6无runningprocesses；独立审计没有赶上live采样，明确不伪称。真实artifact可作为后续新freeze输入，不等于TP2校准或KV效果资格。
未冻的新KV环境已补固定Accelerate，venv-only197包兼容；runtime含CANN路径230distributions记录与前者范围分开，不声称SDK全依赖PASS。下一新TP2效果cohort采用新owner/nonce/1201输入/ascend_kvcompress实际invoked成员/KVspec，检查投影后两rank目的prefix及持久ACK；尚未产生效果结果。
Oct14再次实际Host create_blob仍403 Resource not accessible by integration；已留sourceSHA/真实错误，不改正式source准入。实验、实现与Tectonic工作继续，不等待人工review；H1正式9/9且falsified、H2n4partial、H3/H4正式0、整体NO-GO。

新真实 KV 效果运行 r3/r4 与实际 hook 缺陷（2026-10-14）

r1/r2仅CPU预检保留；r3实际Manager启动后独立发现native_source_files为34条/32唯一路径，生产collector source_digests必拒。仅对匹配PID/start/session/boot的自有Manager受控SIGTERM，原owner finally终态exit1/failed完整保留，两个owned sessions/Host API及两rank身份gone、29494closed、原绝对npu-smi双卡clean。不改冻结清单或动态去重为成功。
r4新freeze config SHA256 247686a44eff2fc16f4ce47eedd0b72c49e95e288a09ef2803bcd804b2e34bd7 / recipe 402a4db7e3216670b16d188acc6ceae26e2bcddcda56addf9fb9418f5e551b36 / owner 5afcbd04407019a8a5e84eaa1d03b59374d445c05f45f0f604fde13186aa0018；actual6eba source_digests32唯一路径和完整CPU预检PASS。真实TP2 Manager/nativehandoff、API、两个新7B workers均实际启动，仅core3+ascend_kvcompress被invoked，旧KVmat/arctic未invoked。新nonce实际tokenizer1201和genuine7Bstats d8绑定，singlePOST已发出。
r4真实HTTP500/qualified effect=false：source provider.before_update_states调用新projection helper时，真实request对象存在但InputBatch row尚未由Host恢复，req_id_to_index触发KeyError。原response SHA256 21868750…94629/traceback/冻结source不改。raw只有4行（start、真实API mapping、两个rank初始普通上传），没有projection或aftereffect prefix，不当KV效果。所有owned sessions/实际Host epochs清空、29494closed、原双卡NPU clean，cleanup_errors=[]。
Source审计已确认before→原Ascend/Host _update_states→after→_prepare_inputs上传顺序：原Host会append实际scheduler新增block并重新add_request，r4真实新增block为[19]；原producer既接点过早，又把全CPUrow误限制为仅8个压缩dest，无法容纳真实后续分配。正在独立新v2候选：保持真实pending，等原Host row恢复后读fullCPUrow==actualRequest==destination+actualscheduledsuffix，再要求后续GPU完整row前缀；真实时间戳，不假row/不回填/不软化旧r4判据。需新Host/KV sourcecommit、genuinewheel和freshcohort，Ascend源码未变可保持原fcbb字节。
校准原wrapper exit1/leafexit未知、r3/r4失败原件已只读hash保全；实际设备3/6空，卡数仍非当前阻碍。下一关键实现工作是真实after-row hook与v2 source/collector，新效果正例尚未产生，formal H3/H4仍0、总体NO-GO。

#177–#178 合并、新 v2 硬件部分证据与下一请求预算

Preserve real 7B calibration input and failed KV effect attempts #177 head c34fc8feeaff97e70e0a0aab6f50ef023d1a9871 / CI353最终三jobsSUCCESS，精确merge e1c63540051edc02812733a088a5de02ea25ccd5。最终234raw文件归档和source-bound failure verifier封存校准wrapper exit1/leafrawunknown、r3受控pre-request失败、r4真实HTTP500/缺row及完整清理。14聚焦检查、独立7全rehashed反例、default与原sourceCPU --validate-stats实际CLI均PASS；stats结构验证与runner成功严格分开。首次CI3.12旧continuousHTTP fixture incomplete日志保留，samehead该job复核后成功，未改生产oracle/冻结实验。
Defer KV projection receipts until actual Host row materialization #178 head eb6fc3dc711c57a3006cd1a1b82cdde4b3199854 / CI354最终三jobsSUCCESS，精确merge 7a6513ef11d6db57facda32256f56d60dec38924。新v2真实after-original-Host-row接点保留actual cached scheduler追加块、before实际effect时钟；after读取fullCPUrow==Request.blockIDs==dest+actualappend，再匹配同rank后续GPU完整row前缀。共享purepredicate强制mapping≤effect≤row≤GPUbarrier，v1严格隔离；77聚焦检查/实际pinned Host AST row-restoration反例通过。首次CI3.10旧同timingfixture日志保留，samehead复核成功。
新独立Host b1f0f3e3adbf0ef6e95c666285354930a0a1cb4c wheel SHA256 b16aa2412c7de8799462565609589bb8fd5c2a2e94c5f7313d57a431ebccf677（2653Python）及KV 81e094ddcb5c3f73d064cab5ed5dd5abf280ceb9 wheel 00123d092f9be938a684de53245f69a4dd31a0946ab5f4df82817d360cd71377（22Python）genuinebuild/安装/全部字节/RECORD审计通过；另环境197包venv-only兼容，Ascendfcbb原757Python/ELF逐项一致。旧r4环境/source/wheels不改。
新v2 r1已真正TP2启动并发singlePOST，但仍终态失败：freeze cfg 144088598bb457ff70831eb016ddc79c62be31e7a82eec2c18a8c3d3f850f18f / recipe 86bcb26854a6a40a2c7a5aefbb6ddb01f488bf95e0e4b06a84be6a0b5328b757 / owner 08a3dcf02d6d5e7b9a623b9bd14216f47a05a9abe1e3a70e414dfafc017f2df3；34唯一路径真实source_digests/54sources、7wheels/14model freshhash、1201输入和新nonce/78-token oracle均先冻。
实际raw100行=1start+1API mapping+2真实v2 projection+96真实GPU uploads；两rank实际CPUfullrow=[11..18]+actualscheduled[19]，semantic1201/physical1024；各47条后续matching full9-prefix，独立真实epoch/env及mapping→effect→row→barrier均核。raw SHA256 80ee39aedc68cbb019f4eb72ca1be2f3d6ec82c46dc3031dc554da681f408b3b。原source默认30s HTTP timeout触发，无response/finish/usage/afterstatus seal，durable完整KVjoin未知，不能从partialraw提升qualification。原failure、两owned sessions/peers gone、29495closed、双卡无running均保留。
下一独立新recipe/source将预先明确180s bounded请求预算，记录实际dispatch/completion clock及elapsed gate；旧default30/r1/raw/oracle/min32/1201/typedGPU谓词不改，不调整H4性能阈值或声称性能。生产Host/KVwheels无需改，新experiment模块仍须CI绿和freshfreeze后才重跑。
只读发布审计确认当前GitHub App安装仍仅selected Manager/MOD/workload，不含Host；工具无repo-selection修改接口。Host真实远端main已到 2454e5289e0442c0f93794b4a05a7a478f4b06ce，冻结b1f0基973的8filedelta不是当前main兼容证明。已准备可审patch/gitbundle并verify，但sourcepublication/当前maincompat/formal准入仍未通过；不替换冻结tuple、不弱化gate。H1正式9/9且falsified、H2n4partial、H3/H4正式0、总体NO-GO，目标持续推进。

历史执行检查点（保留审计过程；旧状态不覆盖上方当前总账）

状态：OSDI 投稿 gate 未通过；H1 r5 正式 9/9 已执行且 post-cleanup validate_batch(formal=True) 通过。r5 三臂的 partial-worker-coverage 结果均为 false_effective=1.0、process coverage 0.5（各 n=3）；它闭合了独立检测 cell，但没有证明真实流量边界能阻止暴露，#60 仍是中央安全属性阻塞。不要把两卡 wheel 预验收、enabled/import、模拟实验、产品发布或 H1 启动时间字段当成 H4 性能结果。下方 2026-10-12 审计快照保留为历史，不覆盖本节的最新事实。

已完成并上传：

H1 r5 正式 campaign：PR fix: stabilize concurrent H1 host journal reads #111/fix: retain formal H1 plans for offline replay #112 修复并发 journal 读取、持久 Plan 离线复验和动态 process epoch 聚合；H1 runner 执行基线为 73ba06ede8a94f6ee7323a4fa5add60439845595；纳入 H2/H3/H4 gate、论文结果、formal proxy membership 和真实 parent-membership 预检后当前 main 为 041060527f43ef0843e54a58f4cfc40b659effcc。全新 /root/ecpa-h1-formal-20261013-r5 完成 3 臂 × 3 次 Latin square，9/9 complete/PASS，每条均含五个注册 lifecycle source；runner-owned pointer SHA-256 为 0a6151281e486514edccb8904c9c08e9a5a5c07d4843639d1b8fa0dd213ffd58。清理后从 pointer 重新加载并运行 formal batch gate 通过，NPU 3/6、端口 8187 和全部 driver/SUT/observer 进程清空。r2/r3/r4 保留为失败或缺陷发现证据，不与 r5 拼接；详见 comment 6148020243。
最新 vLLM-HUST 973d9ef5 + Manager fix: pin bounded formal shutdown budget for TP2 #84 wheel + Ascend PR docs: record current native NPU dependency blocker #50 精确 head wheel + 真实 KV MOD，在分配的两张 910B2 上完成 check → enable → plan → run → 请求 200 → 宿主 observer 的 runtime_effective → Manager-owned stop；进程、端口、NPU 进程释放，停止后状态撤销。仅算预验收，见 #59 实跑记录。
PR #85 已合入：当前两卡栈、模型与已安装环境字节摘要可复算；Python 3.10/3.12、wheel CI 通过。栈预检准确保留插件/宿主上游提交不一致的拒绝。
PR #86 已合入：本任务唯一未提交的 Triton Ascend 工作树差异按精确基准提交、原始补丁 SHA-256 和压缩包 SHA-256 隔离归档。补丁未审查、未应用，不是实验资格。其他相关源码工作树干净，已提交的 Triton #2526/#2527、Ascend docs: record current native NPU dependency blocker #50/feat: compose hash-bound StateAxis MOD plans #54 由现有 PR 承载；可重建 wheel/venv、混合运行日志和无关 /root 项目未塞进源码仓库。

2026-10-13 runner 与精确栈检查点

PR #87 已在 CI run Observe target coverage in complete real host journals #143 的 wheel、Python 3.10、Python 3.12 jobs 全绿后按精确 head 8e60e7df squash 合并；该修复合并提交为 8e140279。它修复 formal-real 的 fixture ACK 依赖、启动后 worker epoch/PID/start-ticks 冻结、注册/执行 fault descriptor 死锁，以及真实 TP2 暴露的 effective/runtime_effective producer-consumer 契约缺口。最终 Python 3.12 全量 698 passed，Ruff/mypy 通过。此合并解除 runner 代码阻塞，但不代替 H1 登记要求的独立命令、activation-path、producer 与 observer 审查。
精确提交重建结果：宿主 973d9ef5；Ascend PR docs: record current native NPU dependency blocker #50 head 54d31aaf 的真实 TP2 启动因非 GDN 模型导入未声明的 fla_npu 而失败。候选 fd70a5c 仅在 docs: record current native NPU dependency blocker #50 上加入 36d4ea5 的 lazy GDN import，custom-op wheel 构建成功、相关单测 6 passed、当前配对 CPU 契约子集 151 passed/1 skipped；它不是 PR docs: record current native NPU dependency blocker #50 或 feat: compose hash-bound StateAxis MOD plans #54 的现有 head，也未取得支持矩阵资格。
统一 196 包 clean-wheel 候选环境现安装 Manager 52922dec、Host b093ae009、KV MOD 9728ccd9、Ascend fd70a5c81；仅 venv 安装集的 uv pip check 通过，更新后 venv 字节摘要为 sha256:9aabf5ce2e4022724770ab56f75ded0c1005e82994ae5c70b8abd7186ddb6013。包含 /usr/local/Ascend/cann-9.1.0/python/site-packages 的 pip check 仍报告 CANN 工具包缺少依赖及 profiler 的 OpenTelemetry/pandas 约束冲突；不得将前者表述为全栈依赖一致。Host/MOD 提交也尚未上传或人工审查，环境仍未取得正式资格。
同一次预检的 97 条 host journal 记录全部经严格解析；包含 1 条宿主拥有的 effective/runtime_effective，绑定 Plan、launch、engine-core PID/start-ticks/epoch 和字符串 request occurrence，且无 sink-write/unsupported-schema 错误。停机后无自有进程，端口 8187 拒绝连接，两张 910B2 进程表为空。它仍分类为 unregistered functional preflight，不是 H1 或性能结果。
首次 KV MOD 候选 38d0a03 的真实 manual TP2 预检得到 health/completion 200 但 0 条 runtime_effective，证明只在前端直接调用 hook 无法跨 spawn 边界，已废弃。修订后的签署候选为 KV MOD 9728ccd9 + Host b093ae009：Host 用严格 JSON import-target 显式 callable 在 frontend、engine-core、workers 逐进程加载；manual wrapper 排除普通同名 entry point 并传递该 callable，vanilla 保持普通 entry-point。Host 定向 32 passed；MOD 定向 27 passed、可运行回归 98 passed，Ruff/format 通过；4 项仍缺 vendor submodule/外部 workload 包。
新候选已完成两次独立真实 Qwen2.5-7B TP2 基线预检：manual 与 vanilla 均 health/completion 200、回答非空，各产生 1 条 engine-core scheduler 拥有且绑定请求 occurrence 的 effective/runtime_effective；manual 还在 frontend、engine-core、两个 worker 留下显式 resolved/invoked，并把已安装的同名 entry point 标为 skipped。两次均无 sink/schema 错误，端口、子进程和 NPU 进程表清理完成。证据位于 /root/ecpa-audit-20261013/baseline-arm-{manual,vanilla}-tp2-hostb093-mod9728/ 及汇总 JSON；仍分类为 unregistered baseline-arm functional preflight，H1 不计次。
Host/MOD 候选 patch 与 wheel 已按 SHA-256 封装在 /root/ecpa-audit-20261013/{explicit-host-plugin-candidate,formal-arm-launcher-candidate-v2}/。2026-10-13 再次验证：shell HTTPS 缺 Git 凭据；GitHub App 对 MOD 仓库 create_blob 仍返回 403 Resource not accessible by integration，所以两个候选尚未上传或进入人工审查。
精确 host/Ascend 支持矩阵仍未通过：插件声明上游 ced6857，宿主记录上游 2d69083，不得只改 pin。当前 H1 候选 Host b093ae009 + Ascend fd70a5c81 的窄契约子集为 175 passed / 1 skipped；完整 CPU UT 在阈值处为 1985 passed / 12 skipped / 50 failed，失败集中于 310P、DCP/MLA、Dyntra 与 profiling-chunk 等 Host API。因此最多只能提请审查 Qwen2.5 eager TP2 + KV MOD 的明确排除式支持范围，不能宣称通用兼容。报告 /root/ecpa-audit-20261013/h1-exact-pair-support-candidate.json，SHA-256 5ae6af2ba1936574c5ab4754a222a2c453574b92435240d76a37d391dc3db40a。正式部署仍未登记，verified-adapters.json 为空，H1 保持 0/9，当前 go/no-go 为 NO-GO。
H2 source-bound 候选 PR #88 已在 CI Retain real TP2 invocation coverage gate qualification #144 通过后合并：固定 KVCompress 00cc78dc 与 Knorm c490cfbf 的 manifest/source blob，并记录两者同时包装 Scheduler.update_from_output。审计强制 oracle_label: null、status: unknown、runtime_effective: unmeasured，目标测试 5 passed、Manager 全量 670 passed。它要求两个安装顺序与独立标注，当前不是 H2 结果或 precision/recall 输入。\n\n- [x] PR #89 已在 CI research: bind H3 baseline phase support to exact source oracle #148 通过后合并；当前 Manager main 为 37d1f1e6。它独立冻结 Host b093ae009、Ascend fd70a5c81、Manager wheel 52922dec、KV MOD 9728ccd9、196 包 venv、Kubernetes image ID、14 文件模型、canonical workload、v2 logical-slot fault 与三臂 activation-probe 摘要。负测保证正式 study/deployment 仍为 pre-admission/unregistered、全部 identity 字段为 null、registry 为空、H1 0/9。\n\n按依赖顺序执行（详细证据留在子 issue；本 issue 是唯一总账）：

修真实 formal runner（ECPA 自身问题，[OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) #59）：真实 formal-run 不实现 fixture 的 stdin/ACK 协议，runner 目前却拿该 ACK 作为启动生命周期事实的门槛。改为五个独立、注册的 source 驱动阶段；就绪探测须覆盖实际模型加载时间；安全排空 SUT 输出但不得把它当真值。保留 fixture 路径，补真实进程与超时/错误负测、离线 validator。
修动态进程身份（ECPA 自身问题，[OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) #59）：启动前只冻结 host/role/ordinal 逻辑槽位与 Plan 义务；启动后从宿主拥有的事件冻结每个 worker 的 epoch、PID/start ticks，并在故障和 observer 前固定。缺失、重复、替换、重放、跨 launch 均 fail closed，runner receipt 与离线复验绑定两个快照。不能预填上次实跑生成的 epoch。
资格与依赖收敛（Ascend #55、PR #50/#54）：插件验证上游为 ced6857，宿主记录上游为 2d69083；不得只改 pin。完成精确 fork-pair 的契约测试、真实服务与支持矩阵，解决 PR docs: record current native NPU dependency blocker #50 旧宿主 CPU CI；核对 Triton #2526/#2527 的合并/替代状态。
原子登记并执行 H1 partial-worker-coverage cell（[OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) #59）：冻结模型 14 文件、安装环境/依赖、canonical workload、故障描述、Plan、三组真正不同的 vanilla/manual/ECPA 命令、五个独立 source 与宿主 observer，完成跨臂等价和 producer/命令/observer 人工审查；verified-adapters.json 与部署 packet 同步通过 schema 和负测。只在此后执行 3×3 Latin-square 九次独立启动并保留原始记录、失败数、validator 结果和资源释放。r5 已完成正式 9/9，该 cell 的 H1 预防性假设按证据判为 falsified；[OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership #60 真实流量权威边界尚未完成。
真实 ExposureGate 与扩展实验：[OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership #60 用权威方拥有的真实流量 gate 和进程成员证据；[OSDI '27][P0] Replace the synthetic composition seed with a real multi-MOD oracle (H2) #63 用真实多 MOD 独立 oracle 替换合成拒绝种子；[OSDI '27][P0] Complete the version-skew, failure, and rollback campaign (H3) #61 完成版本漂移、故障、回滚与卸载；[OSDI '27][P0] Run the matched startup and steady-state overhead study (H4) #62 对相同模型/软件/拓扑做三臂匹配启动、吞吐和 p99 测试，至少每 cell 三次独立启动，报告置信区间与全部失败。性能收益不得由 check/status 推断。
论文与 go/no-go：[OSDI '27][P1] Strengthen the systems novelty, baselines, and external-validity argument #64 补系统新颖性、忠实基线和外部有效性；[OSDI '27][P1] Produce the anonymous, reproducible Tectonic submission artifact #65 仅用 Tectonic 编译匿名可复现 OSDI 产物，完成身份与页数审计。按本 issue 下方 gate 判断是否投稿；未过就保留失败和阻塞，不夸大或提前提交。

硬件：现有 2 张 910B2 足够先完成 TP2 正式链路；加卡不是上述 1–4 的挡路条件。若要声称跨拓扑外部有效性，再安排单机 8 卡短窗口覆盖 TP2/TP4/TP8；它是更强论文结论的实验资源，不是当前 H1 准入前提。

Objective

Bring the ECPA paper from a disciplined design/release draft to a defensible OSDI '27 Research-track submission. This issue is the submission gate; it must not be closed because the product was released, the paper compiles, or a synthetic/reference experiment passed.

Official CFP: https://www.usenix.org/conference/osdi27/call-for-papers

Abstract registration: 2026-12-01 22:59 UTC
Full paper: 2026-12-08 22:59 UTC
Research-track body limit: 12 pages plus references

Audit snapshot — 2026-10-12

Audited commit: eb67cfbba4ead51a65f0c12cc123c57746ab1161.

Strengths:

The problem is systems-relevant: independently developed inference extensions span process and authority boundaries while conventional enabled/loaded state can be false-effective.
The design has a concrete contract compiler, durable coordinator, evidence identity model, transaction states, fail-closed behavior, and rollback target.
Manifest 0.3 and ECPA 0.3.0 have release evidence, conformance vectors, a real clean-wheel Ascend lifecycle qualification, and reversible Manager-owned cleanup.
The paper uses the USENIX format and Tectonic-only build; the current PDF has exactly 12 body pages and references begin on page 13.

Submission blockers:

Formal-real aggregate: 0 completed cells.
First H1 study: pre-admission, nine starts planned, deployment unregistered, all arm commands null, runtime adapter registry empty.
The producer record is stale: it says vLLM-HUST PR docs: record request lifecycle contract evidence #27 is open although the PR merged as b326fafe5405b9996db9c9f0d7758536148ecc9b.
H3 recovery/version-skew campaign: planned only.
H4 overhead/performance campaign: planned only.
H2's perfect result is limited to a 31-case modeled seed whose rejecting cases use synthetic boundary controls.
ExposureGate evidence is reference-model/in-process; no authority-owned real traffic gate exists.
Related work is too narrow for an OSDI novelty argument and contains few peer-reviewed systems/ML-serving comparisons.
The public ECPA name and repository cannot be used directly in the double-blind submission.
The body has no page slack, so measured results and stronger related work require substantial editing rather than append-only growth.

The release gate in #44 is a product-release concern. Passing it does not close any paper evidence task. Historical issue #7 was closed before its listed experiments were completed and is not accepted as submission-readiness evidence.

Required issues

P0 — scientific evidence

[OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) #59 — first three-arm formal-real study completed 9/9 and H1 falsified by retained evidence
[OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership #60 — validate an authority-owned ExposureGate and real process membership
[OSDI '27][P0] Complete the version-skew, failure, and rollback campaign (H3) #61 — complete version-skew, failure, recovery, and rollback experiments (H3)
[OSDI '27][P0] Run the matched startup and steady-state overhead study (H4) #62 — complete matched startup and steady-state overhead experiments (H4)
[OSDI '27][P0] Replace the synthetic composition seed with a real multi-MOD oracle (H2) #63 — replace the synthetic composition seed with a real multi-MOD oracle (H2)

P1 — paper and submission

[OSDI '27][P1] Strengthen the systems novelty, baselines, and external-validity argument #64 — strengthen novelty, baselines, related work, and external validity
[OSDI '27][P1] Produce the anonymous, reproducible Tectonic submission artifact #65 — produce the anonymous reproducible Tectonic submission artifact

Final go/no-go gate

Submit only if all conditions below hold:

H1–H4 are supported or explicitly falsified by validator-approved evidence; no planned/null quantity is written as a result.
The central safety property is exercised at a real traffic boundary with independent authority-owned evidence.
The evaluation includes real independently developed MOD compositions, not only synthetic fixtures.
Every experiment retains failures, exact identities, raw artifacts, confidence intervals, and cleanup evidence.
The paper states one crisp systems contribution and compares it with the closest mechanisms and faithful baselines.
Claims remain bounded to tested runtime, accelerator, versions, topology, and extension classes.
The anonymous PDF passes the private identity audit and all OSDI format checks.
A hostile internal review finds no release-evidence substitution, SUT self-attestation, baseline mismatch, post-hoc threshold change, or unsupported generalization.

If these gates do not pass by the full-paper deadline, do not inflate claims to submit. Preserve the artifacts and retarget the next appropriate systems deadline.

2026-10-14：#179 已合并；新实跑前补齐总超时

PR Freeze nonformal KV RPC budget and independently gate observed elapsed #179 94b88ad264569b069fbfc409fe58768d1fdab138 的 CI run 38493962625 三个 job（wheel、3.12、3.10）首次全部 SUCCESS；expected-head squash merge 11d5b79d695b3bb42ac074e626b233e5d8426904，root 已独立核对并快进干净 main 工作树。
下一独立 nonformal KV v2 cohort 可以预先冻结 rpc_budget_s=180。HTTP 客户端与便携 verifier 同时校验实际 dispatch/completed-read monotonic 时间；这是 socket timeout 加观察到的总 HTTP 耗时资格 gate，不是 urllib 硬总截止时间。保留原 30 秒失败 cohort、不重试其 request、不改 oracle 或 H4 性能 workload。
root 实读原 r1 owner 仅有 startup/collector-ready deadline，未证明 overall watchdog。新 owner 正增加并独立验证 phase/overall watchdog、真实 owned PID/start/session 检查与 finally 收口；完成 CPU 真进程正例及外来 epoch 负例后，才重新冻结 source/recipe/nonce 并启动新双卡 cohort。此条是进行中，不是新 NPU 结果。

2026-10-14：新 overall watchdog 真进程验证（CPU 控制逻辑；不计 NPU 结果）

原 r1 没有可证明的 overall watchdog；旧 r2 仅 CPU 冻结发现 source-gap，保留而未上卡。新源修复 phase-expiry 仍可晋升以及 owner 被杀后独立 sessions 遗留的问题。
最终 outer 源 SHA 0a1db5cc0182dd3dcb5d967a8fe3d84633c1770e04d63be91e8b1225d4a3461b 已由独立 auditor 真执行并由 root 复算与执行 snapshot 一致：正常 TERM 到期、全部忽略 TERM 后 KILL 到期、owner 提前 exit0 留子进程三个实际案例，每轮四个独立 sessions 全部消失、outer exit124；外来 session 保持存活，错误 start_ticks 的 pidfd signal 被拒。
phase 资格同时要求 watchdog 未 fired、取消已记录以及从 probe 入口起（含认证/HTTP/封存）的总耗时 <=180 秒。生产 overall1200 秒；CPU 缩短期限 fixture 只验证实际进程清理控制逻辑。不会把这三轮 CPU 测试写成硬件/H3/H4结果。

2026-10-14：独立 KV v2 r3 已启动真实冻结 launcher（尚未宣称成功）

唯一执行句柄 4400，新 cohort /root/ecpa-native-kv-materialized-effect-20261014-r3。同 clean env CPU 前检 exit0 后，实际 outer Popen owner PID896701/start1096965254/session896701，独立实际 kernel 原始记录已落盘。
config SHA 60b8fbee94f24b4c8b402b5335a1a6e583fb4a7bc07633784f753b008744fff5；recipe SHA 1f8429d4d1a83746780c13dae678b1efc691eec57cb502226aaa54ab89b38438；owner SHA 7f5319e3719ca1f51fdc4bc1384e0a9c5710290d2861c03b202d8234fb8d12e5；outer SHA 0a1db5cc0182dd3dcb5d967a8fe3d84633c1770e04d63be91e8b1225d4a3461b，与实际 CPU 四案例验证版本相同。34 native source/55 total source，冻结 nonce oracle70 token IDs（CPU输入，非生成结果），HTTP180/含认证封存probe总180/overall1200秒。
同一运行持续观察，不因观察超时重启；完整双 worker、HTTP oracle、post-ACK seal、metadata完整row/GPU上传和清理要逐项复算。此处只记录 launcher/owner 已实际启动；没有完成结果，也不计 formal H3/H4。
root 随后通过真实 npu-smi info 观察到两张已分配卡均进入运行：NPU3 worker PID897553、NPU6 worker PID897554，各约21.9GiB进程显存；API PID897130。Manager PID897007/start1096969563/session897007 已有独立原始 kernel 记录。新 r3 确已上双卡，不是 CPU fixture 或重放；仍在运行，HTTP/ACK/qualification结果待终态复算，formalFalse。

2026-10-14：r3 真实 HTTP 完成但文本 oracle 失败；#180 封存旧 r1

新 r3 同一真实运行终态 exit1：HTTP200，prompt1201/completion81/finish=stop，实际 HTTP32.01909209秒 <180；phase总32.133919325秒通过，两个 watchdog 未触发。原响应 SHA e187ad89cbd81b2ba65f61971da2d2438e8ed8cc27c4e5ef1154e0084ffaf563。
冻结 oracle 要求精确两次 nonce；实际只输出一次正确 nonce，随后追加解释。独立从原始 response 重算 oracle=False，不修改预冻 oracle、不计成功、不根据单个样本归因 KV 压缩质量。
原生 raw168：start1/API-map1/两条projection/164上传；两 rank 各81条同源同PID/epoch/request/完整row9的后续GPUprefix。缺请求后 ACK seal，durable KV join 仍未知。Manager/API/两workers gone、29497 closed、两卡无进程，outer四个独立 sessions（含collector）全空、cleanup_errors=[]；这属于 r3 自己的终态，不能补旧 r1 缺证。
下一已授权动作：新独立 compression-disabled TP2 counterfactual，复用 r3 精确1201 prompt/token IDs/nonce/双nonce oracle，明确只是原输入复用诊断、新requestID/daemon/port及新配置冻结；不冒充 fresh challenge 或 formal。除关闭KV bundle外保持core/Host/Ascend/model/输入相同，以判断提示本身是否可满足；一个配对仍不支持总体质量结论。
Seal and independently replay the partial KV v2 timeout attempt #180 head ad3412d129bd6643f4a2b838af291df4fb0d856b 的 CI359/run38495511043 三项全绿，expected-head merge f5f8b5818a5869c4fa1df4f8a985a5bd200ec0fd。旧 r1 原 tar SHA 3fe0c18383ec787e5f06446ac99f7360a4738c6f21c4a4f1effe880935829713 已可从 merged repo 便携复算100raw/47later每rank，同时强制HTTP/最终ACK/collector独立终态unknown、runner_success=False/formalFalse；root独立CLI PASS。不读取当下主机补历史缺证。
进一步边界审计：r3 两个最后 upload 的 fact 时间在 HTTP completed-read 前，但 collector accepted 时间分别晚3.803834ms/11.506064ms。因此每rank81是有限原始后缀匹配计数，不能说全部81已在HTTP读完前durable admission（读完前accepted为80/rank）；缺afterseal仍unknown，既有成功谓词与原clock不修改。
compression-disabled 诊断还停用 semanticcollector/bootstrap、ordinary plugin selection保留core3并移除KV entry point；这些是如实记录的观测路径变化，不能把一个配对写成精确隔离压缩算法原因。payload除fresh request_id全部与原r3相等，包括model alias/sampling/template/max128，phase receipt如实RPC-only、无认证/封存。首个CPU freeze在tokenizer return_dict差异处被IDs equality gate拒，未上GPU；下一次使用原冻结actual_chat_ids实现，保留失败raw与精确原IDs。

2026-10-14：compression-disabled 原输入诊断已启动

新独立诊断 /root/ecpa-kv-disabled-diagnostic-20261014-r2，唯一运行句柄56624，CPU前检通过后实际 owner PID903122/start1097055485/session903122已启动。config SHA 965954fba528f612a19df3b7b9e2e725e8466964a681f0e5d27e8201c5f7e72e；recipe SHA 7c8ff7d0feb228b11b954f76b7452aa505c9562149b6607add3272a4d1794113；owner SHA dfa7c31e8d969e58bab474f30dff123a2f0a289df3ce518c18b6003d72f96ccf；outer已验证版本0a1db5不变。
root与独立 auditor 均逐字段复算：payload除新request_id外全部与r3相等，1201实际prompt token IDs、同nonce与双nonce精确oracle保持；配置关闭KV、核心三entrypoint保留、bootstrap停用、独立冷cache和新端口29498。真实源/轮包/model输入冻结已核。原nonce复用被显式标为counterfactual诊断，不计新的fresh challenge资格。
当前仍在启动/观察，没有结果；用180秒HTTP及phase/1200 overall原预算，只测原提示在关闭KV堆栈时能否严格满足，单对不能证明压缩算法因果或总体质量、性能或formal。
上述 disabled r2 在真实 Manager 入口被 native phase handoff requires enabled bundles 原生拒绝，未启动API/workers、没有模型请求；原件保留、清理通过。源码审计 CLI 空bundle分支不mintIDs，因此没有修改 gate 或加入 no-op bundle。
新 disabled fixed-baseline r3已启动唯一句柄52395：config SHA 61191efdbc1f42c22756067c54e4ddf90252500d0a050da07255e266373c61a7；recipe SHA ba308778f09b0a10fe13e711faa74397ff5937904eb282bf737fb08ee8c663b4；owner SHA bf9305638722cbea765cfc6302d0e751a59914c753d272bc2ab0971740b18f15。CPU前检exit0后实际Manager PID904755/start1097086475/session904755，root与独立auditor核实际kernel一致且仍live，port29499正在服务启动。
实际 Manager CLI run 无handoff，空bundle原生supervise路径；Host记录使用预注册基线fixedIDs与sink，kind明确preregistered-baseline-fixed-IDs-not-native-Manager-mint，没有native-binding伪收据、没有调用launch_environment([])伪造issuer。固定baseline环境/停用bootstrap/冷cache变化明确记录，HTTP180/phase180/overall1200保持；仅原prompt诊断，等待真实请求结果。

2026-10-14：#181 封存 r3 失败；disabled r4补齐实际平台闭包

PR Seal the strict r3 task failure without promoting HTTP or late native receipts #181 head2359033a5f8fd482bedfa2d6676d5d0251255078，CI361/run38497294975三job首次全部SUCCESS，expected-head merge 3faa2b9fde8611248beddcc88b790ab390687c3a。新独立原r3 archive SHA a201f045f3e38422c2d7b701cbedd31421b189e2a2cb535fff5ecbec61972fd2（105members/55sources），root从merged main便携CLI独立PASS：modeltaskFalse、HTTP200/1201/81/32.019秒、168raw/81每rank、两个晚accepted时钟、no-finalACK/unknown-durablejoin全部保持，不访问当下机器补证，也不能归因压缩。
disabled fixed-baseline r3在模型请求前实际失败：Host平台ascend被共用VLLM_PLUGINS allowlist过滤，无法infer device；没有API完成服务、没有GPU模型请求。原日志保全。独立查原enabled r3真实API环境有core3+ascend+ascend_kvcompress；baseline原先只是seed core3，不能误称实际有效平台闭包一致。
新 disabled r4明确core3+ascend平台、KVdisabled、无nativehandoff；CPU实注册actualNPUPlatform/device_type=npu通过，未产生模型结果。唯一真实运行句柄48682；config SHA 4ceaf19b64dc2763334d0b8e15823f2c5e0a25403084b8644932a37ad33be93c，recipe SHA 7e81056a1a25b20b11963eca8d0f7bc8313e4e16aad9db57994e34fd6fe8ad41，owner SHA 75168fb7fc171602acd4259f99e2d20c1203629f8b887bbe229d64ae576ea2d5；owner906157/Manager906339实际进程已启动，29500正在服务启动。同原1201prompt/nonce/双次oracle及source/wheel/model组合，不改输入；仍只是明确fixedbinding的诊断，不具nativeManager/ACK资格。

2026-10-14：disabled r4 真请求也失败；下一任务不降低 oracle

disabled r4 唯一实跑48682终态exit1：真实HTTP200、prompt1201/completion119/stop，20.815822612秒（预算180），原响应SHA c406c007d898c99e3a228d3b6ac608d68916470ba763cc5bdf7613210a316212。actual核心三插件invoked、KV0；三source peers在运行时独立kernel已采、终态全gone，29500closed、两NPU无进程，outer独立captured sessions全空/cleanup_errors=[]。
同一原prompt/nonce/双次exactoracle仍失败：一次nonce开头后解释、正文再次提nonce，不是精确两次串。enabled r3 与 disabled r4 都失败；不能据这对数据归因压缩算法质量，当前任务在基线上的严格可行性也未证。两次失败不改判据、不重试原输入；没有正式资格/H3/H4性能结果。
下一独立任务已授权并开始源码实现：明确新strict-system-copy-v1提示variant，显式system指令与尾部逐字复制要求，但仍精确两次nonce、实际输入1201 tokens、输出>=32/max128/temperature0/n1/stop、HTTP/phase180/overall1200。不使用guided decoding/regex强制答案；old default legacy/archive语义保持。一次fresh nonce抽样、CPU真实tokenizer预冻，新源码CI合并后先实际禁压缩一次；若通过再新的明示paired诊断，不把旧失败晋升。
同时隔离审计真正KV语义producer接点：从实际selectedsource KV workspace、逐layer destination materialize、stream barrier到真正PA/FIA attention op缓存与blocktable参数。当前CPUrow/GPUtable事实仍不证明KV张量复制或attention消费；新候选CPU源/字节谓词亦不作硬件或注册资格。

2026-10-14：#182/#183 已合并；strict baseline 首次真实通过

Add strict two-nonce copy input variant without changing legacy KV evidence #182 最终head 7756c9c2cd3faba04a515df056171e99edc09d35，CI364/run38499138241三job全SUCCESS，expected-head merge 4842bc9aa31575006b6f9501134ba170209788d0。新opt-in strict-system-copy-v1 source仅加强canonical系统/复制提示；仍strict两nonce、1201实际输入、>=32/max128/temperature0/n1/stop/exact180，无guideddecode；缺省legacy语义不变。真实CPU tokenizer1201/74只是CPU证据，未复用其debugnonce。
research: preserve failed original-input KV disabled counterfactual #183 head d8f00582752f413cbc12c17785c1039632f9ca06，CI365/run38499273290三job全SUCCESS，expected-head merge 49daae6245e981fa3a66db75f3af0023f5065fff。原enabled失败+disabled r2/r3启动拒绝+r4 HTTP失败的173file诊断archive SHA 16fb999ee4f351552c3c096023fed0e3473fb11621e7f0a51874143d65e08c5a 已merged，root独立stdlib CLI PASS，bothstrictfail/unknowncausality/non-native基线/lateaudit不是prereg/formal0均保持。
新strict disabled r1唯一实跑47889/29501，首次真实TP2功能通过：HTTP200，输入1201/output75/stop，raw正文精确两nonce单空格，17.015564964秒；原响应 SHA 2111f47a77fcd3472717553576708b905923a5acd641cb1c4258bd589ac24a6f。config ba4a22a73bb6a30941ee6d9afcc5c43fdef95587152d600a2cdc002a6b4c8db4、recipe 20f59490adc6b052a324a4d3e0faf4376254192640dda8b1fdb9f66272d4c877、owner ae66dd56e175482a0eef24b5735e579b1969603391a41317e9428a483dbaab50，源固定4842、freshnonce一次、实际oracle74IDs。先前68口述误数已由原件独立读取纠正，没有输入变更。
root与独立auditor从原response复算strictPASS；三actual source peer运行时kernel已采，核心3实际invoked/KV0；终态三peer/所有captured sessionsgone、29501closed、两NPU无进程。两个watchdog未fire，owner exit0/cleanup_errors=[]。这仅证明单样本提示任务在基线上可满足，不是KV效果、nativeManager/ACK、全质量、正式H3/H4或性能。
下一已直接授权新enabled配对：同完整messages/nonce/输入、显式paired复用且新requestID/29502/nativeManagerMint+KVcollector，coldcache与源4842冻结；livemetadata flag须由同版本portable archive严格复算后才采用。旧成功archive accepted<=HTTPread约束不因已见lateaccept而修改，新latefail如实保留。

2026-10-14：strict 两实跑任务均PASS，但旧窗口校验仍拒 enabled

新enabled配对唯一98491/29502，config bf31bbae595d8111490ad61424ff19fa0db7d539a47e21ebdeb5c73293f46956、recipe 9abbe755b5a5d832160faf14c902efebe96a784aede8d9d576b905d0d48eb7f7、owner 1a07690843ca98edff2c27696586ecfff354f66ba5e5e321ec3d45b861d46936，源4842固定，原nativeManager实际mint+bootstrap/collector运行，同nonce复用明确paired诊断/新requestID。真实HTTP200/1201prompt75completion/stop/exact双nonce，31.412061001秒；原响应 SHA 3362ac453ff31b207832f3f6b3f229fccddbbc0ac5191fdbeffe3a650ec781eb，root与独立auditor读取原body复算PASS。
原156raw（start1+API-map1+projection2+upload152）、每rank75later-fullrow9。afterstatus持久prefix记录真实存在，原collector verify_journal/phase_join可复算记录层metadata绑定；不能覆盖旧HTTP窗口校验拒绝。seq154/155实际accepted分别晚HTTPread4.789211ms/12.342410ms，fact产生时钟在HTTP内。使用真正源4842 seal→verify实际REJECTED KV source facts lie outside the observed HTTP request window，manifest SHA 2c596e3231aa6eb2c0e69f2072b234307fc430a54a50b4d4b58c5d17a1bc46c9。原liveflagTrue、时钟、prefix、failure均保留，不截末两、不重封或赌时序重跑；qualification未知/UNQUALIFIED/formal0。
enabled终态三source epochs/所有capturedsessionsgone、29502closed、两NPU无进程；watchdog未到期、cleanup_errors=[]。这对数据仅证明此完整提示在两实际加载条件下各单样本可满足，不是全质量、因果性、KV张量/attention效果或性能。
Add source-bound selected KV tensor CPU witness candidate #184 finalhead 464214f0b738f756b7e26c8146f16a7fd27a4279，CI369/run38500478181三job全SUCCESS，expected-head merge 8288939dcdf5bf68915875c27ea8df011082be4f。独立selected-source/workspace/destination字节候选、source immutability/alloc/rank/layer谓词、精确源patch与22focused/7真实TorchCPU案例已合并，helper SHA a00d761a0bbee5dd1e7d627a5d8bf6a25b70ec23ffe5fe98eb754c747423c4e7。CPU_SOURCE_CANDIDATE_ONLY/noACK，无NPU；多MB私有artifact/digestACK、源transaction/phasejoin、真实PA/FIA消费仍缺，不开formal guard。
下一已直接授权实现 prospective opt-in ACK时钟政策：事实仍必须产生于HTTP窗口；collector源真实fsync-prefix后issued mono与客户auth窗口夹定，接受≤源issued且TTL≤5s、sameboot/peer/source/finalprefix认证，在线与离线共享谓词。旧默认accepted≤HTTPread保持；旧afterstatus无源/客户mono字段，不能事后套新policy升级。新producer大blob私有artifact+小digest envelope源绑定另独立实现，现64KiB上限/正式注册不变。

2026-10-14 新 ACK 时钟契约已合并；严格配对原始失败保持

Add prospective source-clock final-prefix ACK contract for KV v2 #185 exact head 143ea0d0260f9f0baf4d34f232c798e69ebda01b，CI run 38502796929 的 wheel / Python 3.10 / 3.12 三 job SUCCESS，合并 7fc5f8700452bc3b3d7b94e8cc2903ff1a05d453；root 独立核验并 fast-forward。新 cohort 才可显式预注册 source-fact-in-http-final-prefix-ack-v1，要求事实产生于 HTTP 窗口、接收延迟不超过 5 秒、完整 raw final prefix 的 fsynced source ACK 及真实 client/collector 时钟/身份绑定，并将 before-auth 到 after-auth 限于冻结 180 秒预算。live/portable 共用判据。130 related tests PASS、2 skip；真实 CPU HTTP/Unix 时钟对照不属于 NPU/model 证据。
真实严格配对 disabled/enabled 均 HTTP200、1201 prompt、75 completion、stop、准确双 nonce PASS；enabled 保留全部156条 raw，末两条 admission 仍晚于 HTTP read 4.789211 / 12.342410ms。旧 source 4842 的 durable prefix / metadata matcher 与 portable HTTP-window rejection 分开记录；不裁剪、补时钟或升级旧证据。research: preserve paired model-task passes with the original KV window rejection #186 提供239文件原始归档与隔离旧模块复算，CI三job SUCCESS，root已附加并独立复算。
下一轮须新冻结 client/collector/time-policy 来源与匹配安装 Host wheel 后真实 TP2 启动。Add private selected-KV artifact digest ACK source candidate #187 为新私有 tensor artifact source/CPU Unix 候选（87 focused PASS），尚不提供实际 NPU tensor / attention / full quality / formal 证据。H1正式9/9负结果保持，H3/H4正式0，NO-GO保持。

2026-10-14T03:02Z 当前实际推进

#186 合并 8c75f06a3f94a7207cb9dd0ac09d3351a2f89a3b；#187 exact head a214ee4d0c51d5b63e026092c8fee62587d5475b，CI 38503754032 三 job SUCCESS，合并 f87bb29f3c5322d65d732055df9ea78f16d577bb。root独立核验并FF，187保持CPU/source候选、不声称GPU或attention。

185时钟metadata下一真实TP2独立Host源码checkout、普通完整venv复制与新empty-device wheel build已启动，tensor候选不作为此轮前置。仅完成source/wheel/installed逐字节闭包才启动新cohort；旧档不能补新clock。NPU3/6空闲、两卡不是阻塞。

03:02:18Z 用实际6b3e源码重试Host GitHub blob写入仍403 Resource not accessible by integration；本机管理员权限不等于GitHub App repository access，Host source未发布/未合并。此外部来源gate保持，继续本地真实非正式实验，不因403停止其他可完成工作。

投稿时点核验（2026-10-14）

USENIX OSDI ’27 官方 CFP 当前明确 Research / Operational Systems 两 track；本任务仍为 Research Track。摘要硬截止 2026-12-01 22:59 UTC，完整论文硬截止 2026-12-08 22:59 UTC；提交正文最多12页（参考文献另计）。此时间核验不改变当前 NO-GO，也不将任何资格预检填入正式实验。论文继续仅用 Tectonic。

2026-10-14 新时钟契约真实双卡 metadata cohort 成功（非正式）

/root/ecpa-kv-postack-metadata-qualification-20261014-r1 首次运行 exit0：Host clean 46763abda1ad34e03b6137cb8a7a8a3911897fe0 / wheel a90f4db72bd68dc09e7f604d883122eddaaeb205a937faceb73d3176826c6401，只新增 exact6b3e collector3line；全Host2653及Ascend757/Torch2384+3versionedso/NPU1683/Triton175/Manager39/KV22 byte closure独立通过，7wheel/14model与实际tokenizer均冻结。

新cfg 062a2cace2bb6e444bdacb40e7884ea8670c7b2b9fdfb419704b58e29b1fb329、recipe 4de00afc3283cb79d7fadba3284f0c33672a4f056e94545f19f20911deb8e92b，预注册严格prompt/newnonce/180phase/1200overall与source-clock final-prefix policy；原始input1201、oracle tokenizer76。实际HTTP200 / exact双nonce PASS / 1201prompt、77completion、stop / observed32.348588s。
实际Manager953808/API953875/TP0 worker954190 onNPU3/TP1 954191 onNPU6，native launch 37055c14-c2e1-41d0-ba97-d2c732eb2f07；root与独立agent实查/proc kernel epoch及实际卡进程。raw 160=1start+1mapping+2materialized projections+156uploads，新policyselected159。末两条 seq158/159在HTTP read后5.233954/13.161606ms接收，原样保留；source finalACK 10976821480325490 与真实client authwindow验证通过。
live metadata binding TRUE；exact frozen7fc portable CLI root独立 EXIT0，manifest 8d6afc88d42ba6dbd346d5e516f7d3655fa26bca154caf53c1f35ece59029943。完整finalprefix/事实HTTP窗口/5sTTL/actualACK clock均通过。四owned sessions清空，端口29503关闭，两个卡无running processes，phase/overall watchdog均未触发、cleanuperrors0，未重启。
REAL_NATIVE_KV_METADATA_UPLOAD_BINDING_NONFORMAL ONLY：已解决本轮任务+metadata时间资格，KV tensor equivalence / attention consumption / full quality / loss-duplicate/full objective仍NULL，formal false、H3/H4正式0。旧r1/r3/严格配对的失败不升级；32.35s单次含collector观测不是performance结果。root观察器原module-argv matcher漏捕、修正后的duringRPC观测及原gap各保留，不冒充完整beforelaunch观察。

#188 已附加，提供显式REAL_RUNTIME_UNQUALIFIED张量source契约/可执行sourcebuild，99focused PASS；此时仅源码候选，尚不含新张量wheel/NPU结果。下一步封存新metadata成功原始归档，接新tensor source/wheel→实际selected bytes→actual PA/FIA consumption，继续保持formal guard与NO-GO。

PR #193 merged at 28178e5 after CI387 Python 3.10/3.12 and wheel jobs all succeeded (exact head ae1670e).

The finite real TP2 Tensor R1 archive retains all 56 original selected-logical K/V payloads (2 ranks × 28 layers, 56 MiB), all 201 mixed journal rows, the original HTTP/nonce response, authenticated final ACK, source/epoch and terminal cleanup evidence. Thirteen ordered parts reconstruct the complete 76,364,712-byte raw.tar.xz, SHA256 f704e8d1e7bd35d99ecf0ebfbe6671d2e8baf8133a326b5df5dc935447846548; source-extra yields 279 total inventoried members. The stdlib verifier replays ten exact runtime source modules in an isolated subprocess; Root independently replayed final helper 841e009511a4d2417be480123eb3960399d5ba4a46fd26119bd69724bcac83cc successfully. Local positive plus eight nested rehashed semantic negatives passed; these negative tests are not represented as full outer-archive rehash tests.

Observed scope: exact HTTP task, selected logical tensor bytes, materialization/upload and final-prefix HTTP/ACK join. Both post-HTTP intake records remain intact under the prospectively frozen source-fact/final-prefix policy. Generic unjoined fields remain unchanged. Formal H3/H4 remain zero; actual attention consumption, full physical storage, full quality/equivalence and loss/duplication/objective remain unknown. Source admission and Ascend PR #50 are not represented as closed.

Replay from the repository: python3 -m experiments.formal_campaign.verify_kv_selected_tensor_observation --manifest experiments/formal_campaign/artifacts/kv-selected-tensor-observation-20261014/manifest.json --archive-directory experiments/formal_campaign/artifacts/kv-selected-tensor-observation-20261014

2026-10-15 07:11 UTC 精确新pair实际结果：fresh main47 r5已冻结并启动（cfg0bcdc0b83186b0c37127fa1eadfc824fbbf18e4d3fc5ca121bdbe8cda1d42f24 / recipe4233b3dca3c29a07a68abfb5f9a3de0e660fad9183d95183a4badea13041b51f），后台在模型/worker注册前因Ascend patch_kv_cache_utils导入Host已删除的_approximate_gcd而退出；原exit1/cleanup_errors=[]，原147sourcepaths已快照、失败归档及device终态保留。不能写成Host47/Ascend222组合合格。fresh primary审计Ascend最新main db7f9d4仍有同import，且比冻结源原生C++输入大改；不重标签165旧ELF冒充新main构建。接下来以source policy允许的精确published-commit为边界，在已发布Ascend222865上做完整审计的最小新Host兼容Python补丁/新official commit/真实wheel，native buildinputs未变才可明确复用原真实ELF。新nonce/cohort重新验证，不重判r5。

Manager#206已更新head22c00e827da790932edb7b1d47cc121321ad2509/tree2f1f57fba0d80d92a55478a538550ed33d70fdfd，含精确22模块tokenizer profile和未来fullquote/public response bytes记录；CI418运行中。CI416首次只失败旧KV producer patch与当前verifier的字节等式（1526passed），完整日志保留；改为旧patch仍固定原a00d SHA，执行旧producer/currentverifier对有效和损坏CPU packet对照，不改历史patch。

原r3真实完整PASS保持原tuple/范围，非正式H3/H4。独立便携审计发现原authority只保存quote hash、未保存完整nonce/quote；旧r3不补写，离线verifier明确该限制。完整1102member可无损CAS重包至76412184B（原244769640B仍保留），新CAS SHA be418bf2381edaa5c899ca8f4aae003f1722a8ff7c0db11165e84d90fc88620e；隔离校验与独立artifact分支发布准备中，不先向main追加大二进制。正式H3/H4仍0、NO-GO保持。

fresh r6真实终态（2026-10-15 07:43 UTC）：Host47c8aa1 + Ascend153535 + KVd409 已完整通过单请求 live bounded-response 验证。cfg4a1de164252cc1bf8adfdafce6cdb4eda673bcb118707b38ca49c1a52d44b19a / recipe6d8964fc671f7a98c9d16926bd4291fe13f36f896ed2131104aa9fc870d6a914。

实际Manager1457920/API1458032/worker1458521+1458522/producer1459988/authority1459990。独立producer私有HTTP200/task=true，56tensor+56native OP+2closures，完整未过滤261/261prefix ACK。公开入口初始503→同一冻结请求实际response200→wrongrequest503→对原注册worker1实际SIGTERM后原请求503。fault记录原identity一致且gone；fault503时固定lease尚余22985667695ns。实际公开成功body与probe/producer response字节相同，SHAe1d6c97589f9bccacfacce963ca7d1f5b80acdd56c767a5002adad18319e98c2。684条client observation的原responsebody全部存在且SHA逐项一致；未来完整quote/nonces/validationwindow本轮已采集，不补写r3。

原owner/outer exit0、phase/overall watchdog未触发、cleanup_errors[]；root独立核所有捕获sessions及原kernel epochs gone、29518/29519关闭、NPU3/6空闲。result SHA05824d75e570075bdb07f7b1cb2df04bc78452220a26fa9b26196a3b65427f2c。185个原source path/178唯一内容已逐pin冻结，包含27个原tokenization/runtime-binding依赖，避免late补源。完整raw归档及独立消费者重算进行中。

新tuple四仓canonical source admission也已各一次真实空bare fetch+原validate_observation通过：Manager f9bf(main)、Host47c(main)、Ascend153535(published)、KVd409(published)。source admission report SHA03edfcceb0f516e82ba3487337986b8d4696a3d0830c09648e3c7258825c872a，TLS保持验证、只清单进程proxy；不以本地object/API替代remote fetch。

分类仍 REAL_LIVE_BOUNDED_RESPONSE_RELEASE_NONFORMAL，不是任意后续请求连续保护、完整物理KV、模型数学质量或性能结果。旧probe原native_join_status=unjoined与missing_evidence原样保留；新mixed typed/attention join单独验证，不用旧分类错误拼成资格。下一步真实formal接线仍缺 staged-candidate controller原子prepare/verify/commit与typed注册（不能先公开路由再绑定），正式H3/H4=0、NO-GO保持。源码403已解决，无人工review等待。

r6 完整原 raw 已封存并完成第二遍 1820/1820 regular member size/SHA重验，889696255原始成员字节，xz 244007016 bytes，SHA 5e17b0c883e7997298b5c106e62ae316d0da65b9c8b3d2e7d615c76e25e99da1。包括全部684真实response.bin、完整quote/nonce/validationwindow、185路径frozen source、原terminal及明确标为后续独立审计的材料；没有改原proof/result。archive report SHA253e02747e96bc8badb73ae6ad4e13ca4ca2d45ef5577ceaafbe7aa0a515ae29。源码403解除、真实新tuple可运行；下一步接通typed注册与closed prepared-candidate controller，仍不计正式H3/H4或性能。

清理后准确runtime的 fresh r7 已真实完整PASS，原owner/outer exit0，strict prelaunch input audit8146 paths、187原源码路径/180唯一内容提前冻结；HTTP200/tasktrue、完整未过滤265 ACK、56tensor/56native OP/2closures。独立source-pinned完整重算 observation SHA3cbcfc97e6b0f9bb07bf77a50f07d2901222f7a3865ae50a6cfd87f5d7fdd6d6精确匹配原proof；675真实responsebody、680authority记录、674完整quote/独立nonce逐项核验。public200/错request503/真实registeredworker1 SIGTERM后503，原固定lease仍余23366100941ns；root独立核原epochs/sessions gone、端口关闭、两卡空闲。旧legacy unjoined和原3missing evidence不改，仍非formal/非性能。完整raw正封存。

PR208 final7906670b/CI423(run38704564849)三项SUCCESS已expectedhead合并，当前Manager main 3998f8e / treea2fe2063a232ed829c997f2f2fc27efb77afdfa8。10个新文件交付source permits/真实raw Manager握手/当前kernel+socket绑定/closed prepared-candidate controller/完整独立验证后短期不可续ticket/真实cohort接点；不是formal gate开放，也不是任意新推理转发。R8 owner/preparation完成、30个SDK协议文件发布映射逐byte/Gitblob一致，mapping SHA5c7c1ad0854171c2b3814d345bc28f02fb30ed9166107e08728e332cf4c31dd1。

当前R8 canonical-source gate仍closed：3998新空store HTTP2首lane framing失败，HTTP1第二lane初始fetch超时，原始失败保留。未用connector/API精确源码读取冒充canonical Git准入。独立小探针发现清空全部代理env的当前canonical HTTPS info/refs/TLS验证可达（GET200不代表fetch），正对这条明确不同的安全lane做一次有界完整fetch；正常TLS、原canonical URL/原predicate保持。卡数/人工review/源码403均非此阻塞。H1累计正式9/9/falsified、H2 independentn4、H3/H4正式0、NO-GO不变。

r7完整raw封存与第二遍全部1814 regular member的size/SHA核验通过：893013424原始成员字节、xz250222564bytes，SHA25da7194adcf533a06616acd575de30b6b9aca5e965fa91c9d3b79e49441fabe。包含独立prelaunch strict inputaudit原件及明确postrun打包说明；旧r6混合环境结果未升级。

canonical网络定位到路由差异：新公共DNS所指GitHub地址上，root已用临时opaque CONNECT只转发加密TCP，保持原canonical URL/SNI/正常TLS、无TLS解密或本地对象，实际git ls-remote已exit0并得到3998f8e main（1.77s）。完整fresh-store fetch+原source predicate仍由独立worker实际执行中；此小命令成功本身不代表source admission PASS。R8在完整准入通过前继续关闭，不变更资格规则。

R8 已完整封存并逐成员二次核验：raw SHA eac3c5440a2d45f2762fe8aca437ecaa239c7b2d4870ad84e6f3f51ad263069e，244,984,216 bytes，505/505 members，原892,537,945 bytes。43份外部来源材料以明确 postrun 包装另附；原 FAIL、proof/seals/journal 与过期故障原因均不改。独立终态审计：owned processes/sessions 已空、29518/29519关闭、NPU3/6无进程。

Prospective 修复 local ed19ba0c6385bbf92de49749195b667b71f5a7ba 仅优化 live reader 检查与回归测试：每次调用从根目录 no-follow fd 遍历、完整叶 state、祖先 namespace 前后与第二遍绑定检查，不跨请求缓存；44 target tests + Ruff通过。相同8150路径诊断 microbenchmark 1.390s→0.231s（单次旧/新各一遍，非正式性能结果），旧R8清单会正确拒绝新源码。正在发布/CI，之后新official来源、nonce、fresh输入冻结真实r9；30秒TTL和SIGTERM不变。

R9 完整原档已封存并逐成员二次核验：252,277,772 bytes，543/543 members，原始总892,811,599 bytes，raw SHA256 d1f1af5e3e5aa2ca3e3f84554443fac34443b4548cb0efdaa02de8afb59c27cc；archive.json SHA 549d3be49df107bfd1295f8f637c22707e2b81cecae48f307e9da393723aa1fc。原191 source paths/184 contents、input audit、四份MAC seal、raw handoff、完整journal、full重算/时序与root实际NPU/终态均在，外部资料明确postrun打包，不作为新runtime事件。result SHA仍 878595499864a483a69cb31ce2d88ee491154a298f130081103e9b17ae726e5b；whole PASS 与 formal_result=false / legacy unjoined / missing3 同时原样保留。

下一实际代码任务已开始：baseline_host_binding 的真实Host Unix callback、SO_PEERCRED/新nonce/严格ACK与Host-assigned late identity join；不把invoked当effect，随后通过明确observer-correlation作用域适配来复用同typed verifier，独立注册两baseline。现有正式H3/H4计数不变。

2026-10-16 continuation: container now exposes physical NPU 0/3, runtime logical 0/1. Actual two-process HCCL all-reduce passed (both exit 0; live npu-smi captured; terminal devices empty). This is NONFORMAL device/runtime diagnosis, no H3/H4 increment. Exact original torch/torch_npu wheels recovered from official indexes with original SHA 6f307c2… / 6f7da48…; no repackaging. Baseline activation group r3 frozen with config dc54caa5ddfa0da250f6e3386537728c98162cbb2d54eb3d912ca83ed06a6bed and 91 source objects; independent outer watchdog started. Both baseline arms remain pending until raw receipts + actual response + cleanup audited. Frozen Manager is official 11cbc76 (42 core files), intentionally unchanged despite newer main. Live baseline producer PR #213 is open, not merged. Formal H3/H4 remain 0; R9 remains cached frozen-request functional PASS only.

2026-10-16 actual update: r3 entrypoint TP2 started API/2 workers but calibration source-fingerprint guard correctly rejected the old artifact. Whole FAIL; manual NOT_STARTED; raw 96 callback chain preserved; independent cleanup verified all epochs/ports gone and NPU0/3 empty. Full 124-member archive SHA6920c0e93e0464f93c015b140572a928c0214965ab0948ed3ee5ff151ccd1db3. Instead of relabeling calibration metadata, root ran genuine fresh HF forward calibration on current model (4096 multilingual input tokens, bf16/eager/NPU0); exit0, 82.66s, new artifact SHAabbfce76952552e29f3fd171ff46b357acb2dbb65cb4f3a4a6b9f0a138e39bda, owner gone/devices empty. Fresh r4 cfg c47dda19f84881e9441e022f8271cd703c17d3baab4b2dd6ee10a5b60e8f86b2 with 93 frozen source objects and new calibration started under independent watchdog. No new formal H3/H4 result.

R4 baseline activation + current-model calibration raw archives are now sealed, original files unchanged. R4 archive 291/291 members, 3,282,188B, SHA1b9c1839dc7cf3c35992536e07a24cccbb53d14ea8f4ac0c37cfde2b6b11a479. Calibration archive 29/29 members, 663,824B, SHAcd09fd61ef6e6ff258ac151aac00f5b3a3e43078988a5e9eca3adb995b9e5129. Independent member-by-member SHA/size verification completed; root rechecked both archive hashes/counts. Final independent R4 audit after explicit device-field clarification SHA8ce8a6919f0e5fcbcc3e8d7ad9fc0b59c8f9b679232143fb4cdb7fa10c8de4a2. Clarification does not edit raw diagnostic: its visible_physical_devices=0,1 actually records runtime ordinals; true physical devices are0,3. All formal/effect/performance counts unchanged.

历史执行正文原样归档（2026-10-16，r8 更新前）。正文 64,199 字符，UTF-8 SHA256 49b48bfcffb33267e5e25e3349e6a241c777931f35747c8335d293edcbf4c93d。以下保留当时所有成功、失败、source gate、缺失证据与尚在执行状态，历史状态不能当当前资格；最新状态以 issue 主正文为准。

当前执行总账（2026-10-16；Manager `50dba4953d7ce17fc7c8f635dafe9321d6a5aa37`）

2026-10-16：#220 全 CI 通过已合并；r16/source 完成，准备 r8

PR #220 head cbf413601402719b93256f3f3d22feff2a1d55bd 已合并为 14d7a87f8abd2a9cb4314236c7e1425ecf381c07，tree 0aeb82d4be1c22c3dc53db2c67af92b9a1c7e53e；仅2份源码+2份测试97+/4-。base三个private transition hooks默认仍完整_current，semantic在相邻authority entry/exit覆盖处保留全套base fresh source/kernel/enrollment/collector，去除四处重复whole-authority current。原9次union walk、五处完整authority边界、原30秒、nonce/一次burn及最终response IO后release全保留；9→6 marker因仍隔实际IO已撤销。45 CPU PASS48.03s，最终实际CPU HTTP/Unix v2 smoke1PASS11.39s，Ruff/diff通过；本地commit 8ec1fccfd8e2bb531f88a280c99a279004ff7930。CI451/run38899267640 wheel/3.10/3.12全SUCCESS jobs116967191722/116967191948/116967192063，按exact-head授权合并。

官方merged220源码91逐Gitblob通过，SDK59全==local，core44逐字节交叉一致；metadata SHA 37828d92864f5e56bbebf60d37f878849c950c45b556f1fa02443a3c2fbbc5c0。r16已从官方core42新构建安装，wheel SHA 84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e（core未改，与r15同bytes，未宣称native重编）。fresh空Git canonical首次标准代理curl28传输失败84.57s保留；独立新目录第二次同proxy/TLS/原policy成功37.48s，report management/manager220-request-semantic-standard-proxy-r2.json。本次fresh仅Manager，其他三组件观察显式复用。准备全新r8 Plan/nonce/inputaudits/sourcefreeze；尚无#220新NPU或正向成功结论。两请求原期限内200/consume后再做真实未耗尽workerfault。正式H3/H4仍0、NO-GO。

2026-10-16：r7 真实 native/owner 出票通过，消费原期限失败；r6 启动前路径错误封存

r6 的新freeze通过，但root误传 GROUP/run，被既有outer的fresh-cell路径守卫在owner/Manager/Host启动前拒绝；未运行NPU，不补造outer/owner originalresult。原组永久冻结，185原regular+4显式outsidegroup postrun=189成员与4目录全核验；archive 1,119,908B SHA 8a4a0338d2e985a98fd45512933d19f56c1670fa8ec1dd921b8c1767941748bd，manifest SHA c3d6de972b9a08cebc3189c811890507bd698aa584c8433e196d4311942ea60d，root另独立整档SHA及全部189成员SHA/size/mode重验通过。该失败不增加正式启动数。

新r7改用全新 GROUP/cell，两original inputaudit与162-source freeze通过；config SHA dca273fe47b686b50d0faab9a57f5cc269f33add63657353ad027d649c1ca810，owner源码SHA 8af03667e356c144cc30e4123c6705fd00b72a821b5d91a733a26cdf0c743621。独立outer实际owner141828、真实installed Manager142130/API142187/TP workers142597–142598、producer143930/collector143890均由原件绑定。phase0真实273raw/56tensor/56OP/2closures，producer与owner两份原canonical相等，semantic-ticket已持久；但消费时原期限已过，原public503空body已实际保存，groupFAIL、无consume、phase1未执行。corrected原source独立full FAIL replay通过，canonical ec20af5e5247712fe52f54073f48cf68a71ce11c3dcd02dff987979e3c1f8a7b，report SHA 73de4c0c28c66910fffdea4f5971568085a841892160b3ed1978233a81d8033c；首replay错误把273事件硬编码265，失败attempt日志保留，仅改为与原manifest/fullconsumer序列绑定后重算，不改原件。原producer issued/expiry 7866823554384836/7866853554384836；base ticket原issued已晚于该expiry 0.803964568s，原public503完成晚10.816822328s；semantic-ticket本身无issued时钟，不能虚构精确出票耗时。root独立终态118epochs已退、5portsclosed、NPU0/3empty。原窗口完整capture162sources与91official bytes；整组已永久封存，491原regular+149显式postrun=640成员逐SHA/size/mode通过，原组重验一致，3sockets排除保留。archive 741,278,724B SHA 0fd58b97b24dde76db746ff6c5c44fb47af0f98fa3fa994be6860184ef8dc22c，manifest SHA 7362b390f1a10e96a07cbe172d25972ec0e20d7e92b5ed5a352634c259efe5df；root另独立整档SHA与640 regular member名称/size/mode/count核验，payload逐成员SHA由封存代理独立完成。仍为NONFORMAL、正式H3/H4=0、NO-GO不变。

2026-10-16：#219 已合并；r5 原期限失败保留，新组尚待验证

PR #219 exact head 16f7c995d8ef923da50640febf4067e5a4626c86 已合并为 50dba4953d7ce17fc7c8f635dafe9321d6a5aa37，tree ec57e0cb424dc2d0ad3d9963eab701853e5aa2e6。仅4文件：同一检查切面合并一致file_state，去除permit/grant嵌套和hook重复_current；不跨请求缓存，fresh connection、IO前后与最终release守卫保留，原30秒不延长。42项定向CPU检查PASS47.92s；CI449/run38892877380 wheel/pytest3.10/pytest3.12全部SUCCESS（jobs116946356149/116946356580/116946356821）。新merged-main空Git canonical准入PASS34.61s，report management/manager219-request-semantic-standard-proxy.json SHA ea64e302399942789fef8a45b1773fd581ce32c0a9ee2f8afb6ce99e6eaec53d；仅Manager为本次fresh观察，其他三组件按原报告显式复用。r15已从官方44源文件新构建并安装，wheel内42核心文件逐字节通过（wheel SHA 84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e；与上一core未变，未声称native重编译）。官方91源文件Git blob全通过，SDK59与本地逐字节一致；r6正在新freeze，尚无启动/成功结论，代码/CI/source准入不能当新TP2成功。

此前#218 接通installed Manager/compiled Plan obligation、真实Host/native epoch、独立controller原grant/fence/expiry；producer v2原clock固定，真实Unix receipt→唯一owner fullverify→opaque cap一次burn。旧forward r2 v1功能PASS不能替代新Plan bridge资格。semantic r1–r3 prelaunch与r4 acl导入失败原件均已封存，不追溯升级。

新r5 config SHA c2171453b0c5414711ddd3fb6679b1e0eaaf2781e22e832b80c1ac907f452843 在新162-source freeze/两原inputaudit通过后，以独立outer实际handle42683运行，实际Manager126816/API126877/TP workers127273/127274已真实占NPU0/3各57371MB。phase0实际265raw/56tensor/56OP/2closures、producer fullverify及原v2 issued/expiry成立，但owner到固定原30s检查时正确拒 original producer completion lease expired or clock order differs，原public503/groupFAIL，phase1未执行、无semantic票据/consume。独立原source FAIL fullreplay exit0，canonical df2378d38addf93a8e16c838a8d3c14816a11c2de2b9b8c3527006ae45094b58 精确同唯一持久producer观察；报告SHA 0c04da3d73cb3502e6bcb3d42857ef536587b683f3451bcc34ac905d9ee5603a，完整162source/official91/SDK59/core42/七wheel/两原inputaudit/真实Manager-Host-Plan-grant全部核验。原owner canonical未持久化、failure无monotonic、原503无单独rawbody，均不补造；不冒称owner原JSON已对比或精确原耗时。 root终态125epochs/5ports/NPU0/3empty。原件和原source已完整封存：629/629files逐SHA/size/mode通过，原组未改，archive739,367,452B SHA dac9ea6558ec40da28eafd37fb68e68281aae17b0ae11cc9c52fe50a087e17c7，manifest SHA 6a37c19f0614ae63a392b6528cf17237f32b59e868e84e9a099c7fe5430de857；root另独立核整档SHA与全部membername/size/mode/count。

8146leaves/约0.23s仅为postrun CPU去重定位，不是H4或原runtime计时。下一步在新official source/wheel/freeze/nonce组验证修复；三phase fault runner必须在仍有未消费请求时对真实登记worker施加故障，不能把耗尽503当epoch恢复。正式H3/H4仍0，225/36 starts及阈值不变，NO-GO；CPU检查、历史预检与失败组raw fullverify不晋升正式或性能结果。

2026-10-16：逐请求 TP2 r2 双臂四次真实推理 PASS，独立 full 重算完成

新组 ecpa-request-forward-tp2-20261016-r2 原 outer/owner 均 exit0、watchdog=false、cleanup=[]。物理NPU0/3，entrypoint Host98641/TP98934–98935，manual Host103057/TP103499–103500；每臂两个不同公开请求均触发新实际上游推理，四次公开200与一次性消费均成立，无seed或cached response。独立原始 full consumer 重执行四次，canonical observations 与 producer/owner 全部一致；每phase56tensor/56OP/2closures，各臂原累计514rows，第二prefix逐字节保留第一prefix。entrypoint prefixes 4,641,668/9,214,192B，manual 4,644,088/9,218,908B；未以8MiB限制误拒合法累计journal。

独立 fullaudit SHA 8f31ea5c421afef5ffff0a28b91fa912551f66e71dac5be49b048e723af6a2d7，177 frozen sources/SDK56/core42/原请求响应和ticket-consume绑定全部核验；不冒称离线重建已销毁MAC。root另独立224实际epochs已退出、4ports关闭、NPU0/3明确空闲。完整原件已永久封存：原1271 regular文件不改；128显式postrun补充，最终1399/1399成员逐SHA/size/mode核验、原组重验一致，177 frozen refs全匹配。archive 3,490,494,636B，SHA 1ea722550ce94e2b81c82a6a2c36465b8944292fb1f6228cc64a71372ba70567；manifest SHA 863806d0fa69b58100b2bf63fd74cef19179f14ff7af9d86429f82de74d7a607。REAL_REQUEST_FORWARD_TP2_NONFORMAL：这是四次新请求native功能结果；replay503仅证明已消费/耗尽，不是worker epoch故障恢复。正式H3/H4仍0，225/36目标不改，NO-GO。 真实Manager compiledPlan/obligation/controller generation/fence/原始lease桥尚需下一新组完整正向验证，不能拿本组baseline双臂当ECPA正式资格。

2026-10-16：首次真实逐请求 TP2 失败原件与 PR #217 修复历史

新组 ecpa-request-forward-tp2-20261016-r1 已实际占用NPU0/3（runtime0/1），真实workers86461/86462、Host85975，独立outer/owner启动。entrypoint两次不同公开请求各触发新实际上游推理，原始累计538 events/112 tensors/112 OPs/4 closures；两phase独立 full replay canonical 2d7d0707c891be5ff2adeddd61567b346fd417c70f069fa49cfaff334887b4ab / aa0219212ad275b51f8316ed3e78d9de82a52b76f4f15da4908059aa4aa33fe0 均精确同producer和owner原观察。第一公开200/consume成立；第二已完整验证但最终消费默认8MiB读取拒绝9,614,501B累计journal，公开503且无consume。prefix1=4,708,489B完整保留于prefix2。原组FAIL、manual未启动、formal=false，不增加H3/H4，不冒称全组成功或性能。 独立replay报告SHA 4a86ed09d57ec2bb370150aa413b7c8203f218d53e72b1ad112bcf8a0ec1266d，不重建已销毁MAC；原日志/票据/失败均保留。

root独立终态92epochs/4ports/NPU0/3清理PASS。原738files/3,080,542,863B、177 frozen sources已逐SHA核验；125显式postrun补充，manifest 06456765734a4bb483a450a0dbd50bdaf6207f650be8d19f3f592e915e51a55e，最终archive已完成，863/863成员SHA/size/mode核验；1,743,482,176B，SHA 3686d74dbb3878dca4169341c7a0fd03aab29f6ee34b9eec23c793e3bd90206f，manifest SHA ad36438a27ee70bf7d6b71c19982eb5d434f9ee347568484a24295db4d934b32；root另独立重验archive/manifest SHA与863成员数一致，原组永久冻结。只读full replay结束后，PR #217 head 07c24ac5366c6f1df76d88f0effbace734171f34 将消费路径改用既定64MiB journal上限，响应/单artifact仍8MiB，所有哈希/原链/一次性谓词保留；4上限回归+原4HTTP/Unix集成PASS，CI445/run38880524558三作业全PASS，已精确head合并main 79886df5fe5e3cfbc32a629dd90cd6438f473170。新canonical merged-main/完整88blob/SDK56/core42 r13 wheel均PASS；新组 ecpa-request-forward-tp2-20261016-r2 freeze177sources/两arm各2freshphase/四原inputaudit，config SHA 7c455043503c2342f54e684bff7d4a94ff560f1139752fbb71759286951b2838。r2随后双臂完成且独立full重算PASS（见顶部最新记录）；r1原FAIL永久保留。

2026-10-16：逐请求 live producer 已发布 PR #216，双卡执行待 CI/准入

PR #216 已由精确head 4d344572c5fe110c1dfe5362f5abd3461385e445 合并main 78e2bff0f7611183a813cbc9e9a1b386ad292ca8，CI443/run38876388551三作业全部PASS。新协议按公开HTTP到达触发独立producer实际上游请求，producer/owner各自完整验证56tensor/56OP/2closures后，同handler一次性释放原响应；预声明serial phasebook与真实postPopen3peer enrollment；每phase保留从0起的完整globalprefix，历史payload篡改仍拒绝。根真实CPU HTTP/Unix/process集成4/4 PASS（30.72s，日志SHA 74e1a239e0f89a30376b56cfcfdab269874f2be1a605ab6fd3797f8139cff32f），旧相关回归43+48及projection默认回归通过。这些都是CPU工程验证，尚无新协议TP2结果，不增加正式H3/H4。 CI441原两版本各1687pass/1fail（prospective来源清单旧consumerSHA）完整日志保留；仅更新一个prospective来源SHA后2/2对应检查PASS，未改资格/矩阵/计数。新双请求TP2 owner/freezer/outer已代码复核，等待精确head绿色与canonical/source/wheel准入后实际冻结启动。 CI442：3.12与wheel PASS，3.10原H3 window暴露故障前admit/故障后complete合法inflight被提前拒绝；完整日志保留。已修为严格唯一/哈希/顺序验证后跳过不合格inflight，再查真正postfault请求；17项定向回归PASS，未放宽缺失/重复/倒序拒绝。真实当前模型tokenizer双phase预检均1201tokens、body不同（仅CPU，无NPU推理）。

2026-10-16：baseline native r2 独立 full 重算 PASS，759成员完整封存

原始双臂 PASS 已独立调用原始完整 drain_consumer.verify_observation 重执行确认：entrypoint canonical observation f914fdb32aa80a6655b993cd2bcc830e617864475c18255809c0d9b27e0a1c50、manual 8907df1c74dbca2bfcc135775aed73cb1550e8b1564ba8a6fd36117b93711b1c，精确同各自 proof/ticket.verdict；各273 fullprefix/56 tensor payload/56 native OP/2 source closures，原response/public bytes、source/epochs/chain/ticket与故障原expiry余7.315980977s/8.064110563s均核验。fullaudit SHA 812bcf38f9b854585b4fb7cc69a9386f8c51aeec2a5184d166f5cef2f5fd72ba；MAC仅核原canonical envelope SHA/绑定，未冒称重构已丢弃的owner密钥。root独立终态187epochs/4ports/NPU0/3清理PASS。

完整归档 759/759 members逐member size/SHA验证，1772391132原始bytes，xz 489614412B，SHA 300636232f9f6b2fa1e4a9122e195c2642a7db7cd69baff5adfb50a23b35f9f4；manifest SHA cd2ad681ffbe9eafdb85a40d90265bc6ac766722fab05d4e639657a7d973bfbc。673原regular文件未改未删；86个显式postrun补充含独立全重算脚本/raw输出、root终态、完整49/source44/准入/build/校准实际字节；不把校准当TP2。root重新核完整xz SHA和成员数一致。

REAL_BASELINE_NATIVE_CELL_NONFORMAL；仅冻结精确请求cached response的bounded native资格，不是未来新请求推理/连续恢复/性能。正式H3/H4仍0，目标225/36及阈值不变，NO-GO。下一真实forward路径正在实现新显式多phase collector/client/consumer、不可变完整prefix、独立live producer与逐请求一次性响应ticket；必须由public请求到达后实际执行其唯一upstream RPC，再独立验证返回该次真实response，不能私有seed后cache替代。旧证据/旧schemas不改；必要中立validation primitive提取保留旧默认、按新source hash重新准入，未算正式结果。

2026-10-16：baseline native r2 两臂原始终态 PASS，独立 full 重算中

原 r1 真实Host/TP2、collector认证及permit完成，但producer在READY之前正确拒绝 sealed R4 profile 0644（要求0400/0600）；没有native probe成功，manual未启动。FAIL原件不改，253/253成员封存SHA 01b24a5b86b1c7cd8520eab99c094c52d2bb17c09cdb77c235b536e81e7ce0e1。修复只在新组clone字节相同0600 profile；实际producer reader对7份静态输入preflight通过，原R4未改。

r2 cfg da6317c88007be8fdd5128bd2074a7f8b30bc8328c2f054eb95da256ed6fe010 / common request e1e719bb0960023dab6b31c6ec1b26d454718da209e72fb0ab3f67de6f5de5dd / pinned Manager5606 wheel84a250、source170。真实 entrypoint + manual 各取得独立票据与 273 fullprefix / 56 tensor / 56 OP / 2 closures；public200/错请求503/真实registered worker SIGTERM后503，故障响应分别距原30s expiry余 7.315980977s / 8.064110563s。两臂original PASS、owner/outer0、无watchdog/cleanup[]；aggregate SHA d542876140b2d4a302e0515e6eda63576dd1015a0dfbd9f33c03eb5edaa3b0bd。root另独立检查187captured epochs全gone、4portsclosed、NPU0/3显式empty，审计SHA 5d62cb3ba51928d1d53ef7d9737a1c2a35c6f7d336e95d97a41cab4881d14a94。源钉住原drain consumer的双臂完整重算/链/bytes审计进行中，完成前不作独立full确认。

分类仅 REAL_BASELINE_NATIVE_CELL_NONFORMAL / exact-frozen-request-cached-response，不证明未来新推理、连续恢复或性能，正式H3/H4仍0。PR #215 continuous-window adapter head0529947/CI439首轮三job全绿，root精确合并新main 81946af4bef8a7657895ead6ed981fd03786c7f9；未安装或混入r2（r2仍冻结5606）。下一步新增显式multi-phase collector/immutable prefix/per-request one-use response release，真实forward新请求后才可能推进正式窗口；旧单phase/cached schema不改。

2026-10-16：新 baseline native r1 已实际启动

PR #214 exact head507a9c99 / CI437首轮三job全SUCCESS，root核对head/base后合并 main 5606b8ab4a27d65e713b090726fd14c00d2eaeef / tree a4061cc7427021c68c652506022548ab44740ff9。canonical Manager fresh-empty Git准入40.72s/full tuple原validator PASS，SHA f2226e4561cee9fedbd61150080a23f96c5f67dae3efbd8f5807a3b99fd9cb10；另三固定组件观察显式复用。官方44file/42core新wheel逐Gitblob/全字节核验并安装，SHA 84a250f77e0645e9d685bcbd2a35cffd23362746a89de8e491c4032ea15a976e；49 SDK文件remote/local一致，协议publicationSHA 087ee1b8fe22b9e38d283a0885ec38bf9bffc25609e2d76fd2e90dc4afc465d7。

fresh baseline native r1 cfg 63bb986731690910014c9132522ab180bf0fad09f92e34d44baead48794c5d07，170 source paths，common query 16bc74a4f0ed686614b9a028968965cdb2c4dbf7dc3679dc52811558efec295a，新phase/client/challenge/external IDs；当前模型的新真实校准 abbfce76…。物理NPU0/3、runtime0/1启动前空闲，独立outer实际启动；entrypoint arm运行中。目标每臂完整独立56tensor/56OP/2closures、原30s内public200/wrong503/真实registered worker SIGTERM后503，尚未有新native成功终态。不拿R4 activation作effect，不改旧archive，正式H3/H4仍0。

2026-10-16：live baseline producer 已合并，真实 native 接线继续

PR #213 final head aa776016a105244db95106d9dcaf5a4bbd1c7c6e，CI435/run38856813764 三项全部SUCCESS；root fresh head/jobs 后 expected-head 合并 ef6fd46e6c5c5886c109a4b994f728a57c1c227e。包含独占持久completion写入、固定原30秒、实际owner Unix凭据、socket替换及早启动失败清理；20 targeted tests 通过。尚无 baseline native-effect 成功实验，不把 producer 代码合并算运行资格。

独立 baseline issuer/controller + 真 DrainCollector policy 认证桥 PR #214 已发布，head 507a9c99cb19f685459e98e2e56908c829032808，仅7文件，CI437在运行。实际 native owner/freeze/四端口独立 watchdog 已准备并完成源码审查修正，待 source发布/准入/精确wheel 后新组 TP2；不改旧R4。

R4+新校准完整raw已封存：R4 291/291成员 SHA 1b9c1839dc7cf3c35992536e07a24cccbb53d14ea8f4ac0c37cfde2b6b11a479；新校准29/29成员 SHA cd09fd61ef6e6ff258ac151aac00f5b3a3e43078988a5e9eca3adb995b9e5129，root重核二档hash及成员数。最终独立R4审计SHA 8ce8a6919f0e5fcbcc3e8d7ad9fc0b59c8f9b679232143fb4cdb7fa10c8de4a2。

目标对齐审计明确：固定请求cache响应不能关闭H3持续恢复或H4真实推理吞吐/p99；原225/36目标及阈值不变。下一正式缺件包括真实forward请求/独立源证据、动态成员epoch重注册与跨fault连续客户端窗口。已实现prospective真实客户端/owned fault/forward journal恢复时间接线 local09ec179（CPU真实HTTP与进程验证，不是NPU/正式资格），后续仍须实际source-owned inference/effect证据。正式 H3/H4=0，NO-GO保持。

2026-10-16：容器迁移后精确制品恢复，真实 baseline 激活组已启动

当前物理设备为 NPU 0、3，容器 runtime 为 0、1。真实双进程 HCCL all-reduce 已 PASS，退出码 0/0，保存 live 与 terminal npu-smi；仅是非正式设备诊断。原 0,3 runtime 映射失败另存，不覆盖。

Torch/Torch NPU 原 wheel 从官方发布源恢复，完整 SHA 分别 6f307c2c32d764ffc6ff6893b801fad6d4752f3e67966cb8abf1843427c02604 / 6f7da48ba3db796b06ded6087e1a9a1827af4cada0fb298be76451e5947f10a8，与旧制品相同；未重打包。模型当前 config 仅省略可推导的 head_dim=128，新输入绑定真实字节，tokenizer 重新执行得到相同 1201 token。

PR #211 已经精确 head CI 全绿合并到 11cbc76；用户 PR #212 随后合并到当前 main 0426425。正在执行的 baseline 激活组刻意冻结 11cbc76（42 core Python），不是更新后的 main。两 arm（entry-points-unmanaged / explicit-manual-hooks）只验证真实 Host 回调、动态进程 epoch 和请求；cfg dc54caa5ddfa0da250f6e3386537728c98162cbb2d54eb3d912ca83ed06a6bed、91 个冻结源码对象，该 r3 现已因旧校准来源指纹不匹配而 FAIL；原始96回调/124成员归档、manual未启动、终态清理均已审计。前两次启动前冻结失败（制品路径、模型 config pin）保留。

Baseline live semantic producer PR #213 已发布，head 6589cbca8b3a24a81876561ea3b9924e9e41d0f5，CI434 attempt2全绿，首轮旧HTTP时序测试失败原log保留；合并前修复socket替换时cleanup不可删除替换endpoint的边界，需新head CI。后续新校准真实HF前向 exit0，统计 SHA abbfce76952552e29f3fd171ff46b357acb2dbb65cb4f3a4a6b9f0a138e39bda；当前 manifest 指纹及28层finite统计由独立CPU读取验证。使用新统计的 r4 两条真实 TP2 激活路径均 PASS：entrypoints 96条回调，manual 100条回调，各自API/worker0/worker1三进程真实kernel绑定、HTTP200、请求后身份复核；outer exit0/watchdog=false/cleanup=[]，所有epoch gone、端口闭、NPU0/3空。aggregate SHA b44ecde7f23da5801fe1bc6f47057780f0873c1152e78e296e943f6dbde0e9d3；独立审计 SHA 15f20c77ef334b7b32214f925f0ba84611ba90be83fb3e0eb10b08d59aac6d74。仅 REAL_BASELINE_ACTIVATION_PREFLIGHT_NONFORMAL；effect/semantic资格仍null，不能计正式启动或性能。完整raw正在封存。独立 baseline issuer/verifier/controller 已实现并通过103项相关检查，正做真实运行接入。正式 H3/H4 仍 0；NO-GO 不变。

2026-10-15：真实 staged r9 整轮 PASS；正式 H3/H4 仍 0

r9（精确 f15 wheel/30协议映射/新canonical315、cfg57fad/recipe7db65）outer 0、watchdog未触发、cleanup_errors=[]。真实NPU3/6上TP2 worker1521690/1521691各22,312MB运行；原lease固定E=11091467615404158，public200收毕余 15.113250415s，真实registered worker1 SIGTERM后的503收毕余 8.736696340s。fault-observed marker为实际gone+503+未过期后产生，绝非expired503。prepared→commit14.224755006s/public请求0.561204891s为单轮诊断，不是性能或统计结论。

独立frozen consumer full重算：277 fullprefix / 56 tensor / 56 OP / 2 ACK closure，canonical观察SHA c31c50ea45c629f1d949a9e54532448dd47a3ec78eb2e5f994d4ad0cfa786475精确同proof；全部767controller链行验证，原847B public/private body同SHA89aa95388860fae9dc29da935b2cbc71a5acfada0354e38ff43861ef01332d1a。191 frozen source路径、permit→原单次rawhandoff→deployment→ticket的scope/fence/generation/inputaudit/原expiry绑定全过。fullaudit SHA30c45f9eace311c483a491dac2aff6bb843d53272f8c3117856c7c7696b1e35a；时序/binding审计SHAaf6f7e5607009586b1a0a90e45595ce287edc44031ae347b3c369f091aaed10c；root终态再次核ownedepochs/session全gone、29518/29519关闭、NPU3/6空。完整raw正在封存，R8失败原档不改。

此PASS仅 REAL_STAGED_CELL_CACHED_RESPONSE_NONFORMAL：冻结精确请求缓存响应的live typed producer/source/epoch/固定lease资格，不是任意后续推理转发、全物理KV、模型数值质量、正式H3/H4或性能结果；原legacy unjoined/missing3和semantic资格null不回填。H1正式9/9且falsified、H2独立n4/excludedn5、H3/H4正式0与NO-GO不变。

下一缺件已具体推进：原baseline activation硬编码旧MOD；PR210仅增加真正ascend_kvcompress→register、direct ENABLE/同冻结provider+calibration/source-pinned profile、vanilla stockloader/manual显式调用和spawn漂移failclosed，保留legacy默认。CI427三job首次全SUCCESS，root exact-head核后合并新main 68c4700；尚未安装/无baseline实跑/不影响r9。仍需baseline专用真实Host→owner身份适配器，不能伪造Manager receipt或给baseline引入durable coordinator，再做同信息/同predicate/同scope正式登记与真实强基线。

2026-10-15：r9 已实际启动，完整来源准入通过

标准已配置proxy路径真实fresh checkout + 原predicate独立emptybare fetch在31.86s完成，原fulltuplevalidator PASS；report SHA 315fd65dec9857516d04018f0bf89750213f3e144a54bec5794b91ffa909a9f1，newmain f15/tree dbc。前述直连/US失败原件全部保留；header/CANN假说均未认定根因，不关闭TLS也不替换canonical Git证据。

r9 cfg 57fad7cf6784906d022ba0065fca0f80695c39a4c347104d7f7a06e33b5f742b / recipe 7db65bd2a803fa65e7231ef021fb5ed47f7d1e70dc3a597394bb64bca91ce340 已fresh freeze；191 source paths/184 contents及27 tokenizer依赖提前捕获，独立closure核验PASS。新30映射b757/新r9官方wheel41core/canonical315一致。root启动前核NPU3/6无进程、29518/29519关闭，outer启动且CPUpreflight0；actual input audit已完成，真实Manager 1521284及原始单次认证handoff已出现，TP2启动中。尚未有完整r9 ticket+public/fault终态，不计成功；formal H3/H4仍0。

2026-10-15：PR209 已合并；r9 等新 canonical 来源 gate，尚未启动

Manager main f15bfb8 / tree dbc41ce95ac4584ea27373e0b0fb9a7d5d65580c。PR209 head d07542e 仅2文件；CI425/run38721438773 attempt2三jobs SUCCESS，root fresh exact-head/base检查后合并。attempt1旧H3 CPU网络时序测试coverage=incomplete日志保留，同head仅重跑失败3.10一次；不改变任何资格predicate或测试预期。

官方merge-ref30 SDK协议文件全文/blob/local字节全一致，映射SHA b757b63ff0084b1bbaa6b2da41af782ca34a6a085c9586e96119474989e5b47c；43官方core源Gitblob逐项校验后新r9 wheel构建/安装成功（hash仍def13e...，明确hash不能唯一标识commit）。首构建误假定开发环境已有hatchling，保留失败log后恢复标准isolated build成功，无新runtime源码混入。未来baseline profile local1d5948未安装、不属于本轮来源。

新canonical Git gate首DNS20.27 route小GET正常，但真实fetch45秒无进展，FAIL原件保留；US114/112 v2header小GET也超时，正在做有依据的协议header/路由对照，原canonical URL/TLS验证/独立空Git库/predicate不变。r9 尚未冻结或启动，不计任何新的真实成功。NPU3/6可用且空闲，绝非卡数/管理员权限/人工review阻塞。R8 wholeFAIL和所有原始证据不改。

2026-10-15：staged r8 整轮 FAIL，已定位检查耗时

r8 实际产生 permit、认证原始 Manager handoff、deployment、完整独立 verifier/ticket 和精确冻结请求 public 200；273 native / 56 typed / 56 OP / 2 ACK 闭包均由 frozen consumer 重算一致。但 prepared→commit 用去26.891秒，public请求再用2.851秒；200收毕原lease仅余171毫秒，SIGTERM intent余156毫秒，故障503收毕已过期6.627秒。整轮正确失败，原result、缺失fault-observed marker和全部旧标签不改，不能算未过期故障排除或正式H3/H4。

实测8150文件的每次元数据检查1.400秒，主要为重复canonical路径解析；完整语义重算10.863秒。正在实现每次验证内部共享安全目录遍历，保留逐文件完整state、祖先/符号链接防护、epoch/fence/原30秒expiry；不延长TTL、不换SIGTERM。下一轮用新来源、新nonce与真实TP2重新验证。

2026-10-15 09:20 UTC：3998 canonical 准入已真实通过，staged r8 已启动

新安全路由已实际完成canonical Git来源准入：只用临时opaque CONNECT传递原github.com加密TCP，正常TLS/SNI/原canonical URL保留，无解密、无本地Git对象。独立fresh checkout及原predicate内独立emptybare fetch均成功，Manager3998/main3998/treea2fe、38.47s；复用另三仓已实测immutable观察后原validate_observation完整tuple PASS。report SHA4149b4af5e5f3e309b6b2311e40e9992524cf2e18ec571cbb6705e1e8edb1732；前三次失败记录全部保留，临时Git对象与网络helper已清理。

fresh staged r8 freeze/preflight已通过并启动outer runner：cfg 8c5cd89023d038799e9122fb94f04e243706f2d67a507ef6a93abf3969b3cdad，recipe 781d52022ece8631328185995bf313533ad7c4f3f408f4810b1cf52408025088，191实际原source路径/184唯一内容提前按pin冻结。原56native source/758Ascend/175Triton/七wheel/14model/22Host tokenizer source不放宽；独立actual input audit已完成，真实single-cell permit与实际原始Manager wire/native receipt/认证封装已产生，后台启动中。此时尚无新staged public200/完整ticket/故障终态，不计成功。新路径private prepared候选不先开public，完整独立重算后才commit固定原expiry ticket；scope仍仅冻结请求cache响应，不是任意后续推理转发。

r7完整封存已完成1814/1814 member二遍核验，xz250222564B / SHA25da7194adcf533a06616acd575de30b6b9aca5e965fa91c9d3b79e49441fabe。H1正式9/9 falsified、H2独立n4、H3/H4正式0、NO-GO保持。

2026-10-15 08:08 UTC：r7 严格输入审计发现 Triton 共存安装，保留拒绝并清理

新 live_route_reader 输入审计在真实 runtime（非fixture）拒绝额外运行文件：固定triton_ascend3.6.0+git92513dba之外共存上游triton3.6.0，29个额外文件共176574921bytes均由上游dist RECORD拥有且逐SHA一致，明确不在pinned Ascend wheel中。其余六wheel未见extras。原r6仅有边界功能/selected-effect记录，不能因此推定完整严格七wheel环境资格；原result/proof/raw与nonformal分类不改、不得追溯升级。诊断与旧额外文件先保留在独立postrun归因材料，root已卸上游triton、按原SHA10c14f7de72854a94827d41b6a9cf2fc5ce1c2fd94690895a6d0c8f9ccb3459d重装固定triton_ascend，以新审计/nonce/cohort验证。extra-file guard不放宽、两卡充足，不等人工review。清理后新实际strict input audit通过（8146 file_state paths，audit SHA2ab10f200ffe8f8125a6683931236765c364690d73f6e309f2d93612532a01d5），upstream metadata与29extra全部gone。fresh r7（原bounded profile，非新staged profile）已启动：cfg c3a430c2bd06c5702aaacb4a55f2c81102d59f60fbf9f4d34478e21256f7344e / recipe96b37862dc8fc940c7aa6b033ef8a53d222830acba038ca89b9e240e6d7a35ca；187原source路径/180唯一内容提前冻结。真实终态PASS/owner+outer0；265完整ACK、56tensor/56OP/2closures、public200/错503/真实worker故障503，原lease余23366100941ns。source-pinned完整重算SHA3cbcfc97e6b0f9bb07bf77a50f07d2901222f7a3865ae50a6cfd87f5d7fdd6d6精确匹配原proof；675responsebody/680authority/674完整quote逐项验证，全部owned epochs/sessions gone、两端口关闭、NPU3/6空闲。raw封存中，仍nonformal。Manager/r7 wheel来自官方fcbee精确43源码文件逐Gitblob核对后新构建；canonical Git HTTP2/HTTP1两条fetch失败保留，connector读取不替代canonical source admission，因此仍非正式资格。下一步typed staged controller PR208 finalhead7906670b已发布（10file/treea2fe2063），CI423/run38704564849三项SUCCESS已合并新main3998f8e6；独立staged r8准备/30协议源码publication mapping完成，但新Manager canonical Git HTTP2失败/HTTP1超时，gate仍closed，正按独立网络探针新证据做一次有界安全lane，仍待真实准入与实际运行；H3/H4正式0。

2026-10-15 07:43 UTC：Host47 / Ascend153535 fresh r6 真实完整 PASS，正式 H3/H4 仍 0

用户补齐选仓后源码发布成功，403 不再是阻塞。Manager PR206 final head22c00e827da790932edb7b1d47cc121321ad2509、CI418/run38696487324三项SUCCESS，已expected-head合并 f9bf53a。保留真实quote/nonces/验证窗口及公开HTTP response bytes的改动只作用于新cohort，不补写r3。

旧r5实际backend启动失败：Host47c8aa1配Ascend2228652，Ascend引用的规划helper已从Host kv_cache_utils移到kv_cache_planning，未注册真实worker/未产生成功HTTP。原失败完整封存180members，xz1366140bytes，SHA9b1fd8f3a021e9b9732bd1a0297c075c824b97a7b04322ab91053e0d24d140fc；owned sessions/端口/两卡已清理。r4 tokenizer路径CPU freeze失败也保留，均不升级。

新兼容源码 Ascend153535b32417b3ad8fb10dad2f564ddf4dcab1ef 已发布为独立 draft PR58，不覆盖Ascend main、不触PR50。修正真实规划模块的导入/patch目标，保留Host实现；wheel SHAa674e9826ce6a19c75062312229e742ab386a47686ad3fd083e993fe4a1726e6，751Python+7so=758。1787项原生输入不变，165 genuine ELF显式复用，不是新clean native compile；无workflow run，不冒称Ascend CI绿。

root已安装并冻结fresh r6：Host47c8aa1/Ascend153535/KVd409，56个真实native source路径包含7个Ascend兼容模块和2个Host规划模块；七wheel/全模型/tokenizer逐项闭包核对，CANN PYTHONPATH保留。cfg 4a1de164252cc1bf8adfdafce6cdb4eda673bcb118707b38ca49c1a52d44b19a，recipe 6d8964fc671f7a98c9d16926bd4291fe13f36f896ed2131104aa9fc870d6a914。真实终态PASS/原owner+outer exit0：独立私有HTTP200/task=true、56tensor/56native OP/2closures/完整261 ACK；public503→精确请求200→错误请求503→真实SIGTERM registeredworker1后503，故障响应距固定lease到期尚余22985667695ns。684实际client responsebody逐SHA核对，完整quote/nonces/validationwindow已保存。root独立核全部owned kernel/session gone、端口关闭、两卡空闲、watchdog未触发及cleanup[]。result SHA05824d75e570075bdb07f7b1cb2df04bc78452220a26fa9b26196a3b65427f2c；原legacy probe unjoined/missing_evidence保持，独立source-pinned消费者重算SHA5d3fce122f290e83748b206bc47b471dd98fa21421d28538131b52f5fa197523与原proof完全一致；689条authority链、683完整quote及不同nonce、684validationwindow和实际responsebody逐项通过，完整raw已封存：1820/1820成员第二遍size/SHA核验通过，889696255原始字节，xz244007016bytes，SHA5e17b0c883e7997298b5c106e62ae316d0da65b9c8b3d2e7d615c76e25e99da1。

r3原始证据已发布在独立artifact commit 246d398；原archive不变。内容去重CAS76412184bytes，SHAbe418bf2381edaa5c899ca8f4aae003f1722a8ff7c0db11165e84d90fc88620e；远端Git blob身份校验通过，隔离stdlib原始consumer重放通过。canonical raw/Git重下载未成功，r3完整quote/nonce transcript及多数公开response body缺失，不声称完整离线challenge重放；13个recipe依赖仅作显式late supplement。仅12个小文本文件的 PR207 exacthead61522ea0364116263389320a85ff1da9a56e21e9/CI420(run38700069292)三项SUCCESS，已expected-head合并fcbee398baf1a36d76f6c4ec2dcb8a592cd9159e；artifact branch没有合入main祖先。

仍是单个冻结请求有边界的非正式response release验证。H1正式9/9且falsified，H2独立n4，H3/H4正式0，NO-GO保持。

2026-10-15 06:54 UTC：首个真实 live producer + 独立 response authority 完整通过

Manager PR205 exacthead18733dc62b7426a34daf95931cc9de419556365a，CI415/run38693332730三项SUCCESS，已expected-head合并 93ca75e。CI415首次Python3.12旧continuous stop/resume fixture incomplete失败完整日志保留，仅该failedjob重跑后绿；初次CI414 source-audit失败也保留，没有改formal矩阵/计数。

fresh r3真实完整PASS/owner+outer exit0：Qwen7B/TP2、独立producer实际私有HTTP200/task=true，56张量记录、56真实native OP完成、2source closes、完整未过滤265/265 ACK。独立HTTP authority先503，验证后只释放同一冻结请求的字节一致response200，错误request503；实际对已注册worker1发送SIGTERM后，原请求503。root独立复核故障前kernel与注册identity完全相同，故障503发生时原固定lease仍剩23761395371ns，排除自然过期。phase/overall watchdog均未触发，cleanup_errors=[]，所有captured sessions为空、API/worker epochs gone、29518/29519关闭、NPU3/6无running。分类REAL_LIVE_BOUNDED_RESPONSE_RELEASE_NONFORMAL；不是任意后续请求连续语义保护、完整KV/模型数学质量或性能/正式H3/H4结果。

r3完整原始archive已封存并逐成员核验1102/1102，875520077 original bytes，xz244769640bytes，SHA76d68e7417479e9306955447842d910d79cbe6db54607ff70ae6ad170c565360。原result SHA86a0f0a5f7c49ae7a3cae4f70cd94ee9bd784667b6fa623b9d3e4c6490fec3cb。r1/r2仍failed，分别完整995/1126members归档和源码快照保留，未追溯升级。

最新Host main47c8aa1已genuinewheel安装并做fresh实际ND2：新observer538320/Host verifier witness b1035、双device共8cases真实ND2及6synthetic callback负例全部通过，owned kernel1442813/nonce/recipe逐项绑定、exit0、timeoutfalse、双卡终态空闲。recipe941eb0a1b0c2b25c39e7af478bf89873df6cd916301f8968e5148ffde7965e36，descriptor SHA f25b0000f066a1236daaa62ed7cf0e24e994330196a43f5f21c6df4a92a53d73；此tiny诊断无model/attention调用，不算正式资格。

PR206 six canonical模块按发布Host精确bytes同步，仍stdlib-only，KV d409实际capture source与Host verifier分开保留；未来worker fault加入拒绝PIDepoch替换/必须gone/故障503须在固定lease内。CI416进行中，base已转main。新main full-model r4在CPU freeze发现旧tokenizer source路径已迁移，正确拒绝且未启动NPU，失败目录保留；正修显式新tokenization source binding后使用fresh cohort。

canonical source admission也实际全4项PASS（下列为06:54历史tuple，07:43已另以Managerf9bf/Host47c/Ascend153535/KVd409全4项fresh真实通过，report SHA03edfcceb0f516e82ba3487337986b8d4696a3d0830c09648e3c7258825c872a）：未改source_provenance函数，fresh empty bare从规范GitHub HTTPS实际fetch Manager6feb/Host47c/Ascend222865/KVd409；本地proxy截断TLS，单进程http.proxy空后直连成功、证书验证不变。无local objects/API替代，无残留临时Git库。此为源码准入可达性，未来新Manager修订仍须按实际main重新取证。

H1正式9/9 falsified、H2独立n4、H3/H4正式0、NO-GO保持。

2026-10-15 06:36 UTC：r2 producer 已实际验证，HTTP runner 缺头修复后 r3 已启动

新r2真实HTTP200/task=true，typed/attention join=true，独立live producer完成 56tensor +56native OP +2source closures +完整285条prefix ACK，签发固定30s lease proof，独立authority实际从503转为ready200。随后公开POST仍503：runner漏发独立authority要求的X-ECPA-Request-ID（只发后端X-Request-Id）。整轮r2仍failed/exit1，尚未执行worker fault；原始证明、完整raw、原145sourcepaths快照和清理保留，不把partial成功写成整轮通过。

已修复public client仅在公开请求加入绑定header，新增真实HTTP+Unix回归：backend-only header503、exact identity/body200、wrong body/identity503。16项authority、18项combined检查通过。PR205更新exacthead 18733dc / tree fa3163ddd91e08350a1a0c9c57c3beebe61d095a。CI414最初Python3.10单项source-audit equality失败、1523passed，原840KB完整job日志已保存；只重算attention consumer新SHA，矩阵、eligibility、formal0无变。新CI415/run38693332730进行中。

fresh r3已冻结153source/七wheel/真实model/tokenizer：cfg413521082304ec041f5b265e5710bce3540a387753f588ac7e4bba2bbc56a022 / recipe548be0216cc8028deca513dfcf36244264c94004d100228763f1c2c96aa5ee1b，launcher1436471已启动，尚无终态。仍是新nonformal bounded response-release测试，不是正式矩阵。

Host新main后续兼容修复PR59保留上游变化/typed/SPDX，将4个协议module恢复stdlib imports，并用checker现有allowed_files精确窄白名单，维持跨架构-I/-S source重放；10项实际checker反例/隔离import与style/mypy已过，CI运行中。SDK6canonical同步与fresh ND2只准备、不改r3运行文件。

2026-10-15 06:27 UTC：新 policy r2 已启动；Host latest main 已合并

PR205 exacthead e824a01 / tree be49e58f1d6390df60ccb3b0fbef6eaf89ed0831 新显式opt-in source-drain v2 policy已发布，33项定向检查通过，TTL/缺opt-in补强后25项重跑通过，独立review通过；旧v1读取原r1实际265raw仍拒绝。CI414/run38692220687运行中。新policy只允许source-close前的非effect upload尾部；两rank首OP前必须已有完整HTTP内destination upload，typed join显式只用HTTP内upload allowlist。不能用tail补缺rank/首次destination/tensor/nativecompletion。

唯一owner已冻结153source/七wheel/14model/真实tokenizer并启动新r2：cfg 33f5a896d2346e229fda75e7e2cdd7bf76b8def50f4897faae59d9679cfd42c2 / recipe 65dd028ec47a5888ed078c8c351b5a12170962c6a182f66b53c8cd77f88db8d3。CPU闭包preflight exit0、真实owner PID1430333/start1107425504，启动中无成功判定。沿用精确16bd/222865/d409 runtime，只改新Manager source/policy/nonce，不以最新main替换旧结果。

Host#58 exacthead bbef8fa4 CI38690596347两项SUCCESS，已expected-head合并main 1adf8c05af5012f3e9c10f7ed4fe2f1d2c8654b0 / tree fe01435e36035f25da5efd459071cef1fa7e6682，与被检head树完全一致。该main genuineemptywheel已另构建，2699Python逐字节核验，SHA b464fd1b07f196ecd6af00060ffb14e0837a10d1552de76da5959d256adb25c8。1230仓库文件差异不能靠旧NPU结果推定兼容；新main ND2诊断/匹配SDK source审计单独准备，未安装到r2。

失败r1完整归档已完成，995members /875243083 original bytes，xz237961308bytes，SHA a2072539e8234cf77b78d5985ad36d7a9d4a56890698d08b6de28f6951b55134；全部995成员哈希独立重验通过。原r1仍失败。H3/H4正式0、NO-GO不变。

2026-10-15 06:16 UTC：首轮 live 真实终态失败，原规则拒绝且清理完整

PR204 exact head 58f4cea 的CI412/run38690316182 wheel/Python3.10/Python3.12三项全绿，已按精确head合并为 6febd28。

fresh live r1 实际 Qwen7B/TP2 请求 HTTP200、task check=true，原raw 265条 = 147 native +56 tensor +56 operator +2 source close +4 transport starts。完整消费者失败，producer拒绝证明，公共authority全程503，没有放行成功或真实worker故障测试。失败准确定位原seq262：worker1最后 block-table-upload 来源时间比真实HTTP received晚405203ns；source→accept 22.510655ms<5s，不是TTL失败。不能删此记录、改旧时钟或重判r1成功。prospective新policy设计将区分严格HTTP内effect witness和完整保留的source-close前非effect尾部，晚记录不得补首次destination/缺rank/张量/OP资格。

原owner exit1，phase/overall watchdog未触发，cleanup_errors=[]；独立终态全部已捕获session空、API/worker原epoch gone、backend29518和public29519均关闭、双卡无running。原config/recipe/native引用145个source path已逐哈希冻结为136份唯一原始字节；原始失败归档进行中。Host#58 latest-main carry bbef8fa4 的pre-run-check/pre-commit均SUCCESS，新main wheel正在构建，未声称旧结果可映射到新main。H3/H4正式0、NO-GO保持。

2026-10-15 06:11 UTC：403 已解除，live producer 新 cohort 实际启动

用户已补齐 GitHub App 三仓选仓；三仓写入和 exact Git tree 公开发布均成功。冻结源码对应 Host 16bd856 / PR57、Ascend 2228652 / PR57、KV d4090a8 / PR21。403 不再是当前阻塞。 Host 最新 main af5f930 的增量移植另见 PR58 / bbef8fa4，保留上游修改；CI运行中、尚未合并且没有该新 main 的 NPU 结果。

Manager PR204 / exact head 58f4cea 实现真实已安装 plugin artifact→semantic Plan→实际API/worker环境绑定，独立 live native producer 和独立 HTTP response authority。新 protocol 对固定请求验证当前真实进程 epoch、Plan/controller generation/membership、完整 native completion/typed receipts、sealed full-prefix ACK 和不续期 lease。目标是实际私有请求后释放同一已验证响应、错误请求503、实际终止worker后503；此 scope 仍是 bounded response release，不宣称任意后续请求已获连续正式资格。

fresh r1 已冻结153项source、七wheel、14model/真实tokenizer；cfg SHA a24c3c3af14854825b0df4e9996ec8e1f987da3c8cb03565bf6726fd2f158bc3 / recipe 0b108d00dc170c054ee1cc6a8111098d2a67e5edc5a15e59124348a91cf01ff6。独立outer runner已实际启动，CPU闭包preflight exit0，Manager/backend启动中，尚无新HTTP/producer成功判定。唯一owner使用分配双卡，180s phase /1200s overall watchdog。Host/Ascend/KV wheels按新官方revision重新打包审计；Ascend明确复用同一源码原651-target真实编译ELF并逐字节核验，不称新clean native compile。现有runtime环境已升级为本次tuple，旧R4 wheel/raw/失败证据保留。

H1正式9/9且falsified，H2独立n4，H3/H4正式0、NO-GO不变。下文403/0/9与旧运行状态均为带日期的历史，不覆盖本节。

2026-10-15：语义 Plan 编译与直接近邻比较

PR #203，精确 final head 7ed5fd7d68b9615e3ee5daed9de3dc9ea3ce2fcf / tree 4b05f5541ca3eea0f0b50a38bf0d6be27dc9bfb2，增加 compile-semantic-plan：仅显式 runtime/all-worker TP2 native-completion 契约可生成绑定精确插件、manifest、Host tuple 与 worker 集合的新 Plan。普通 invocation 不满足该义务，旧 invocation observer 拒绝新 Plan；错误 authority、覆盖不全、版本漂移、重复 JSON 与事后重绑均拒绝。83 项 compiler/observer/evaluator CPU checks、另2项论文 provenance checks、Ruff、strict mypy 通过。独立复核修复 requires 消费者代替缺失 provider artifact 的身份漏洞，当前 profile 只允许同一 extension 的 provides。CI408 两版 Python 首次各10处来源绑定失败，原日志保留；精确源码重算 modeled31case 后仅 compiler SHA变化，decisions/counts/oracle标签全部不变。最终 head 的 CI410（run 38683480574）wheel / Python3.10 / Python3.12 三项全绿，两版各1474 passed、3 skipped、6 subtests passed；#203 已按精确 head 合并为 07215d9b2a4f37d5d89739b2aff8f622b2866448，无需人工 review。这是前瞻编译，不是正式 producer 注册、live gate 或新 NPU 实验。

论文新增 D3S（NSDI ’08）和 Chandy–Lamport snapshot 的直接比较，明确 source-drained ACK 只闭合有限观察；同信息 predicate-monitor + gate 强基线尚未实测。公开/私有稿均只用 Tectonic，14 总页/12 正文页/8 嵌入字体，自动 audit errors[]；旧私有生成目录已清理，身份与路径不公开。

真实删除清理：144 个过时仓库/worktree、28 个旧环境，释放 56.8 GB；现在 4 个工作区/2 套环境。原始实验/失败、必要 source/wheels 与未提交草稿的可恢复档案保留。R4 隔离重放和 64 项清理后证据/论文检查通过，不计新增硬件结果。

今日 fresh source audit：Host 04c0b191…、Ascend 92c7ab31…、KV 5256d4b0… 的目标仓精确 commit GET 仍各 422；三个 create-blob 写入仍 integration 403。本机现有 Git/SSH 也未提供可用替代认证，未请求/等待人工 review。Ascend PR #50 仍 open/unmerged、head 54d31aaf204c77df8102cf30f8111c5baf3acadd。NPU3/6 健康空闲，卡数不是阻塞。H1 正式9/9且 falsified，H2独立n4，H3/H4正式0，NO-GO 保持。

NO-GO。H1 正式 9/9，预防假设 falsified；H2 独立计分 n=4；H3/H4 正式均为 0。 新真实 TP2 metadata 已在线、离线通过；随后独立新 cohort 的 56 份真实张量记录与 HTTP/ACK 关联也已通过，覆盖两卡各 28 层、56 MiB 选定逻辑 K/V 字节。完整物理 KV、attention 消费、完整模型质量仍未知；这些均非正式资格证据，不能作为性能结果。

2026-10-14 11:55 UTC 实际更新：Attention R3 已结束，HTTP 200、task check=true、56 条真实 OP 记录，但原始全日志 262 条、实际最终 ACK 仅覆盖 260 条，完整资格判定失败。两条尾记录的来源时钟在 HTTP 内，接收发生在旧 ACK 后；禁止截断全日志、补发 ACK 或重判旧 cohort。R3 完整失败封存 raw.tar.xz 为 74,848,484 bytes，SHA256 c338ef707f6ff08fdf592165191f614cf91feceffe5abbee3481001e2d165168，292 members；H3/H4 正式仍为 0。前两项真实失败原因分别由已合并 #197（按 layer 绑定共享 metadata）和 #199（精确 vendor Format 规范化）修复。

新的前瞻完整来源结束协议见 PR #200，head 34e45f2ec497f1d5362948ff03a8268ff5a3e6d8。两名 worker 在真实 finished request/InputBatch removal 后分别闭合来源，collector 才封存整个未过滤 phase prefix；关闭后的发布被拒绝。83 项 CPU 来源/格式/Unix/HTTP 检查及 3 项 client/manifest 检查通过，均非硬件结果。PR #200 精确 head CI402 三项 green，已合并为 d5d3febf12d769bb47ccf7fd0a4acfc82ad82b70。fresh Host 04c0b19163aa350837bc63e11ec5b4e2a51db572 / wheel SHA256 adc33a1773741a0038320acb86fa64c4b79cf93f71c8dbc8d7de6649a516a29a 已构建安装，2659 Python files source/wheel/installed 逐字节一致；Ascend 92c7ab3 / wheel bc31f0eb… 757 Python/ELF 安装字节不变。R4 fresh recipe SHA256 df4a88eae1775d5cff9def2a3a97efa5ef544e3fe4acfa5f687657953ca3af50、owner-config SHA256 e7526309a0da24d565263f8335b98d462f9ac9a9abc66899c746c2db4b2d2a73 已冻结（96 sources、47 native sources；oracle68、phase180s/overall1200s）。2026-10-14 12:00 UTC 真实 outer runner 已启动，CPU preflight exit0，已创建实际 owner kernel identity；启动/结果尚在观察中。R3 封存 292 members、442380596 original bytes 已逐成员 SHA 重验 PASS。正式 producer/source admission 与完整 H3/H4 矩阵仍未完成。

2026-10-14 Attention R4 真实终态更新：fresh Host/source-drain profile 下，HTTP 200、task=true、56 张量记录、56 真实 attention 参数调用完成记录、2 名 worker 的真实来源闭合记录，未过滤日志 261 条，最终 authenticated ACK 完整覆盖 261/261。在线 typed/attention HTTP/ACK join=true；root 事后纯重放 exit0（没有重新认证、补发 ACK 或改变原始时钟/记录）。owner/outer 原始 exit0、phase/overall watchdog 均未触发，四个独立捕获会话为空、实际 source peers 已清理、29508 端口关闭、NPU 3/6 无运行进程。R3 仍是原始完整资格失败。R4 只证明此冻结单次请求的有限选定张量/真实参数完成/HTTP/完整 ACK 关联，不是正式 H3/H4、完整物理 KV/数学正确性/完整模型质量或性能结果。完整 R4 打包发布仍待完成。H1 正式 9/9 假设 falsified、H2 独立 n4、H3/H4 正式 0、NO-GO 不变。

2026-10-14 工作区整理与 R4 发布：334 个目录、84 个散落文件已同文件系统归拢到 /root/ecpa-workspace/{worktrees,environments,builds,evidence,management}，保留旧绝对路径兼容链接；146 个 Git head/dirty 状态及 15 个脏 worktree 均保留，5 处相对子模块 Git 元数据路径修复，134 个 linked-worktree 注册修复。R4 原始证据哈希不变，迁移后 source-map 纯重放通过。

R4 完整 300-member、452122629 original-byte 封存现见 PR #201，head eb457d6e70b9e784d82044aa913843e287840b4e。完整 XZ 78193744 bytes、13 个连续分块，SHA256 69101ef1e478831ef2fde16df51baa4a23c5fe32b4488b9d3334e8fad4688d41；全部远端 part Git blob 已与本地字节重验。标准库 verifier 使用冻结 consumer 源码，在 -I -S 且禁止访问原主机 /root、模型、设备和进程路径下重放成功；Host/Manager/source-peer epochs、独立捕获会话、原始 cleanup 均交叉核验，截断 ACK、伪造封存但缺 worker close、张量损坏、live terminal peer 和 Host epoch 替换反例均拒绝。CI404 首次 Python3.10 的旧连续 HTTP 暂停/恢复 fixture 报 incomplete；1451 passed，新的 R4 六项均通过。保留首次失败；仅重跑 failed job 后精确 head 三项 green，#201 已合并为 e0c05044aa066239f0103512519bb50ae865b525。没有新正式结果或性能/数学质量结论。Host repo write fresh recheck 仍为 integration 403，正式 Host merged-source admission 尚未完成，不等待人工 review。

2026-10-14 论文/资格边界更新：公开/私有匿名稿均只用 Tectonic 重编，14 total / 12 body pages / 8 embedded fonts，自动 PDF audit 0 errors。R4 正文计数从完整冻结 archive 独立重放生成（56 native completion receipts、2 worker closes、261 full-prefix records），同步见 PR #202，head ee82207835c4585222d19ea837fe787de5a11cb3，CI406 精确 head 三项 green，已合并为 2c241dcdb52b24c0d1d5316ec6c1c4f9c12d63e4。新增生成数据/PDF/匿名输入与既有构建检查共 23 passed；私有匿名身份保持，路径与映射仅本地保存，implication anonymity 未证实。没有新增正式结果、性能或数学质量结论。

正式 tuple fresh primary-source audit：Host 04c0b191…、Ascend 92c7ab31…、KV MOD 5256d4b0… 的目标 GitHub 仓库精确 commit GET 均为 422 / No commit found；三仓 create-blob write 均为 integration 403。源码快照已封存，但这不满足 Host merged-main / Ascend+KV exact published-commit 准入。当前卡数不是阻塞，正式 H3/H4 不应启动/计分；source publication/admission 和正式语义 producer 仍缺。H1 9/9 falsified、H2 independent n4、formal H3/H4 0、NO-GO 保持。

完整历史（包括旧 main、0/9、全部失败及精确哈希）已原样封存于执行总账历史快照，source body SHA256 62a8e41c26b60a68a58107d2923883ff3e769d9a28d68532843a6b3eab4c29fc。历史状态不覆盖本节；原始实验输入和失败档不改写。

issue	已核验的当前证据	仍缺 / 状态
#59 / H1	r5 三臂×三次、五注册生命周期来源；formal batch PASS、9/9真实启动。各臂 false-effective=1.0 / process coverage=0.5	issue closed；预防假设被证伪，不声称保护真实流量
#60 / ExposureGate	#144 真实Qwen7B TP2/独立HTTP authority的503→200→503、95raw；#173 原生request/upload transport；#189 新真实KV metadata与完整时钟/ACK检查成功；#191 consumer 后的新 Tensor R1 完成 56 份真实选定逻辑字节及 HTTP/ACK 独立重放	有限非正式证据。formal semantic producer未注册；完整物理 KV、attention/full quality未知，不能开放正式effect gate
#61 / H3	#158 ECPA-only真实TP2 coordinator prepare→SIGKILL/restart、60冻结single-attempt请求，deadline loss0/admissiondup0/reusedIDs0；#166另冻结worker-crash/full-relaunch三臂资格	都是非正式资格，不替代原manager-crash matrix。execution duplication/full objective未知；Host source admission、匹配baseline和完整版本/故障/补偿矩阵不足
#62 / H4	已有真实预检与冻结runner准备；分阶段/整体watchdog和动态epoch已有实际验证	正式0。三臂同版本/硬件/模型/负载/暖态的startup与steady-state量化尚未完成；单次HTTP耗时不是性能结果
#63 / H2	#160 排除预诊断report消费case后n=4、TP=2/TN=2/FP=FN=0；原n5/raw/oracle/prediction完整保留。真实compression两加载顺序1201semantic→1024physical、两个worker ACK	compression冻结UTC不准确，非正式且不计score/quality/performance。PP2×TP2未实跑；CLI/config、外部authority独立检测、process/communication等表面仍不足。#175仅CPU/source pair、unknown、不计score
#64 / 研究论证	已有source-bound corpus/related-work/negative H1与有限H2的明确边界	系统novelty、最接近机制/已知baseline、external validity仍需完成；不能以qualification数量替代研究贡献
#65 / 匿名投稿产物	已有public/private隔离、Tectonic编译和PDF/身份审核，旧版12页正文	已合并#194，以完整#193归档重放生成有限tensor宏；72项相关检查PASS，public/private仅Tectonic，各14总页/12正文/8字体，所列PDF审核错误0。私有alias、title、路径与映射不发布；implication anonymity仍未证明

新真实 metadata 成功：#185 + #189（2026-10-14）

Add prospective source-clock final-prefix ACK contract for KV v2 #185 exacthead 143ea0d0260f9f0baf4d34f232c798e69ebda01b / merge 7fc5f8700452bc3b3d7b94e8cc2903ff1a05d453，CI371三个job SUCCESS。仅新cohort显式预注册 source-fact-in-http-final-prefix-ack-v1；旧strict-window失败不升级。sourcefact必须在HTTP内、accept TTL≤5s、真实source-issued/fsynced final ACK必须覆盖完整raw，并位于真实client authwindow；before-auth到after-auth总预算180s，另overall1200s。live/portable共享判据。CPU时钟fixtures不是NPU证据。
r1 /root/ecpa-kv-postack-metadata-qualification-20261014-r1：Host clean 46763abda1ad34e03b6137cb8a7a8a3911897fe0 / wheel a90f4db72bd68dc09e7f604d883122eddaaeb205a937faceb73d3176826c6401，只换exact6b3e collector3line。全Host2653与Ascend/Torch/NPU/Triton/Manager/KV七wheel/source/installed、14model、真实tokenizer闭包独立通过。
cfg 062a2cace2bb6e444bdacb40e7884ea8670c7b2b9fdfb419704b58e29b1fb329 / recipe 4de00afc3283cb79d7fadba3284f0c33672a4f056e94545f19f20911deb8e92b；strict-system-copy-v1，新nonce，1201input、oracle tokenizer76；实际HTTP200 / exact双nonce PASS / 1201prompt、77completion、stop。32.35s仅单次观测。
native launch 37055c14-c2e1-41d0-ba97-d2c732eb2f07：Manager953808/API953875/TP0 954190卡3/TP1 954191卡6，独立实查kernel epoch/NPU。raw160=1start+1mapping+2materialized projections+156uploads；seq158/159在HTTP read后5.233954/13.161606ms接收，完整保留。source finalACK 10976821480325490 在真实client authwindow内；actualphase≤180、两个watchdog均未触发。
live+exact6module portable PASS，manifest 8d6afc88d42ba6dbd346d5e516f7d3655fa26bca154caf53c1f35ece59029943。四owned sessions gone、29503关闭、NPU3/6无running、cleanup errors0、首跑exit0。独立observer原matcher漏捕及修正后duringRPC观察原样保留，均不冒充beforelaunch预注册证据。
#189 exacthead 619f6162e2a21265d51d1c7bb84701a35fb1b323 / merge 5cffbb42ab64aab5ba27044053c3086d9faee967，CI379三job SUCCESS，root独立核验。201regular members / archive SHA 996a889521ef81d71802824720efa1e8421b3cf96f136f2891923cdd97b333ce，15checks含14完整重hash语义反例；root/独立agent便携复算均PASS。
REAL_TP2_RECORDED_KV_METADATA_UPLOAD_BINDING_NONFORMAL ONLY；tensor equivalence/attention/full quality/lost-dup/full objective仍NULL，performance=false、formal=false。完整offline serving/model/wheels与private Triton cache不是这个公开档案的范围。

Tensor 构建与协议阶段历史（已完成，真实结果见后续节）

Add private selected-KV artifact digest ACK source candidate #187/Add explicit unqualified runtime tensor contract and executable wheel handoff #188 已合并，188 merge 9d5bfaa883d78325f4b341215c98d0f42a164f11 / CI377三job SUCCESS。显式REAL_RUNTIME_UNQUALIFIED tensor source契约，CPU设备与反向CPU误标拒绝；原CPU档不改、formal guard仍closed。仅selected logical tensor bytes，不等于完整NPU physical storage/padding等价。
新独立Host/KV source、genuine wheel构建、新venv安装/pipcheck/七wheel逐字节审计已通过（Host实际wholewheel2657.py，source-filter2656含generated-version边界另记录）。旧环境不动。mixed journal包含tensor事件，旧185generic reader不可复用；新typed fullchain+actualUnix/HTTP/clock consumer正在补齐，并要求payload实际source/readback时间在HTTP内、2rank×28layer完整、与真实materialized row/后续upload联结。完成来源闭包后直接新nonce真实TP2，不等attention hook或人工review。
随后验证actual PA/FIA operator参数/真实cache pointers格式/table/seqLens及native stream完成，与source-owned transaction联结；forward返回不能冒充attention消费。继续H2完整oracle、H3原故障/版本矩阵、H4匹配测量、论文与go/no-go。

外部来源 gate（不阻止可完成的本地实验）

2026-10-14T03:02:18Z 实际重试Host GitHub App blob仍403 Resource not accessible by integration。本机管理员不代表App repository access；Host source未发布/合并，不能伪造MergedSource或绕过formal guard。Ascend PR #50 最新仍open、head 54d31aaf204c77df8102cf30f8111c5baf3acadd / base e5870e657a2add3182551c70bbad5919fc96d899 / mergeable=false。测试使用的本地Ascend fcbb827af84f793939bf03d01a1dfe0338a0164c 不冒充其已合并。

两张已分配910B2（NPU3/6）足够推进TP2，卡数不是当前阻塞。仅用logical0/1，不继承ASCEND_RT_VISIBLE_DEVICES=3,6；唯一设备owner避免并发实验。遵循已授权exacthead/CI-green合并，不等待人工review。

投稿时点

OSDI ’27 官方 CFP：Research Track；摘要2026-12-01 22:59 UTC，论文2026-12-08 22:59 UTC，正文最多12页，参考文献另计。当前NO-GO，完整目标保持；资格预检、历史、模拟、报告消费或单次运行耗时都不能填为正式/性能结果。

2026-10-14 论文与执行总账同步

#189 merge 5cffbb42ab64aab5ba27044053c3086d9faee967 / CI379三job SUCCESS，root另独立原201file stdlib replay PASS。#190（head 687eb970ad1a476782ea229e9ae81f47f470d54d，tree 48e11e4b54056e553030bc9bbb4ecbeb9768c239）已发布并附加：新metadata事实由完整#189归档/六冻结模块重新生成宏；不提升formal/tensor/attention/quality/performance。重复历史与限制文字精简，协议要求与H1实测失败分开叙述，保留全部实验边界。

67项现有相关tests PASS、Ruff/diff PASS；public/private overlay各仅Tectonic编译，14总页/12正文、8嵌入字体、所列identity错误0；private生成宏与public一致，路径/alias/title/映射不公开。public页10/12灰度实看无裁剪。#190已由root按exacthead合并 dbefccfc0cb22ab66ae70a55d761d9b20d416158；CI381 wheel/3.10/3.12三job SUCCESS，已FF主线。首次扩写正文溢出13页及旧fixture输入未含新档案的失败已通过实质压缩/补全依赖修正，没有改版式或隐藏失败。

Tensor R1 启动前闭包历史（已完成）

#191 已发布/附加，immutable head 0666cf001db4f2a6247f6da6b2c12ad0b97e5560 / tree 2ac8af48560de482e5fabffc02abae07de4801c8 / consumer SHA ca425825cd92d49f105687a912e97792e01f7b8f57d18f9f69259aa126e4a0fb。实际CPU HTTP/Unix四进程、63完整records/56typed payloads/2projection/2laterprefix/mapping及全部2rank×28layer联结通过；独立12tests+6subtests及五个完整重hash协议反例均PASS，4CPUepochs gone。此为CPU协议fixture、假model/tokenizer/NPU字段显式标记，不计硬件结果。isolated -I/-S搬迁CLI/完整sealed source-map也通过，原recipe不改；此前漏映射的严格拒绝原件保留。

sole owner已在immutable191 source checkout执行新tensorR1 CPUfreeze（不启动GPU），计划 /root/ecpa-selected-kv-tensor-qualification-20261014-r1 / port29504。新source/七wheel/真实tokenizer/model/private directories闭包完成且191 CI三job全绿后直接actualTP2；不等人工review或attention hook。此时还未产生新NPU tensor证据。

2026-10-14 首次真实 selected-logical tensor R1 成功（仍非正式）

#191 exacthead 0666cf001db4f2a6247f6da6b2c12ad0b97e5560 / merge db887cc2e160dab815c5cac0ca0e7dcf71b6afde；CI382三个job SUCCESS，root另独立核验并FF。新R1 /root/ecpa-selected-kv-tensor-qualification-20261014-r1 首次完整运行exit0，原cfg 98aefd628a2978947b084b0208b5de84118523985eb2b5cee2088aa9c30a30d1 / recipe 16caee7502597297e197a9587005351dc3e1765a08cb25a0c9ea0c915ddc51ce / owner e473a0df3421ffe5d2bf1e911791958c03c215124d4621de8fe187470c7d724a，70sources/39unique native文件、七wheel与真实model/tokenizer/mode700/28×2/180phase/1200overall全冻结。source/wheels不重写，不从mutable worktree GPU。

native plan ac3ab8b8a85fe177f4e105d7c434203111ed85e32ca54df5fff51655b371d498 / launch b825e942-5284-4d50-9dc1-85c1c672c27f，真实Manager975325/API975375/Engine975608/TP0 975719 onNPU3/TP1 975720 onNPU6。root提前只读observer实际捕获API和后代、kernel epoch及实际NPU进程；source assigned角色由原始Host journal提供。消息中误写API975385仅转录typo已纠正，原始journal/owner未改。
HTTP200 / exact双nonce task PASS / 1201prompt、69completion、stop（实际oracle tokenizer68，与实际69不同）；约51.54s仅本次观测，不是performance。新运行完整 raw201=2start+1mapping+2projection+140uploads+56tensor.artifact.accepted；每rank70uploads，69条属于effect/projection后的实际fullrow9 prefix。
2rank×28layer=56 actual typed receipts；本轮选定逻辑K/V数据58720256B（56MiB）actual-source-selected→workspace→实际destination readback字节相等、source immutability和实际cache format/storage/rank/layer/nativeplan/worker epoch联结通过。typed transaction 232e85f56922386b2479376a6ba08397c8aaece2f466d040ebc263be976d7bfd 与两个worker实际CPU materialized projections→后续matching GPU rows联结通过；不混淆typed与projection各自不同preimage hash。
201原记录完整保留，seq199/200在HTTP read后5.277364/13.368667ms接收，全部payload四读写时钟与envelope时钟在HTTP内，maxacceptTTL266.697ms<5s，source finalACK 10980000326702694覆盖全finalprefix201并在client实际authwindow内。旧generic run_rpc_only的missingevidence/native_join状态原样保留，独立typed消费路径通过，不伪造generic资格。
root exactimmutable0666 standalone CLI独立EXIT0，observed_typed_HTTP_ACK_join=true / materialization_read_write_clocks_inside_HTTP=true / 56 receipts / durable_artifact_join_complete=true / modeltask=true，wholejournal SHA 51fe6aec74a7a60774a46656cde1021148920fbef6a2bd64d591242109eb1ff1，response SHA 83a95389722c20571e259e22e713598ff9af962934604191045dfe239ec22e29。独立agent另isolated -I/-S source-map CLI+56 actual payload SHAs复算PASS。四owned sessions清空、五核心kernel epochs gone、29504closed、NPU3/6无running、watchdog未触发/cleanup errors0，未重启。
REAL_RUNTIME_UNQUALIFIED / FINITE SELECTED LOGICAL BYTES ONLY：不是完整physical NPU storage/padding或full-KV equivalence，也不是actual attention consumption、完整质量、lost/duplicate/完整目标或formal producer registration。GPUqualification/attention/fullquality/fullobjective仍NULL、formal=false、H3/H4正式0、NO-GO保持。

正在保留全部真实payload/原始source/HTTP/ACK/cleanup归包以供离线复算（优先stdlib xz或按体积分chunk+整体SHA，不能仅hash替代payload）。下一actual eager PA/FIA nativeOP hook另源准备，不碰本轮输入/wheels：InputBatch实际runtime/table/cache binding，已validatedUnix layer ACK→OP实参/pointers/format/seqLens→同native stream completion；generic forward返回不算attention。不支持branch明确unknown。

完整 Tensor R1 归档独立重放（2026-10-14）

Root 已只读重放准备中的完整归档：13 个顺序分片重组 SHA256 f704e8d1e7bd35d99ecf0ebfbe6671d2e8baf8133a326b5df5dc935447846548（76,364,712 bytes）；额外源码归档合计 279 个逐文件哈希成员。56 份原始 receiver payload、完整 201 行混合 journal、真实 HTTP/model task、最终 ACK 和 2×28 layer join 全部通过；helper SHA256 ec22dd92a976dabd93ba5bcd101310fb5d17c1c925050ecfeaaeed812c8bae53。重复 worker publication 文件排除有显式说明，全部 receiver 字节保留。此为本地准备版重放；公共完整归档已发布为 PR #193，head ae1670eae581265c354379bc545cc0a56a558b4a / tree 8e1055b05f9c701e3b382674deafb602ad9c9f48 与本地 immutable 归档一致；CI run 38513918051 三项均 SUCCESS，root 核对 remote exact head/tree 后按 expected head 合并 28178e5575cce55fd937a8ede257b918bb560e14。formal_result=false、attention/full model quality=null、performance=false。H2 README 陈旧 n=5 独立检测宣称已在 PR #192 修正为审计后的 n=4；现有 scoring-input audit 已重跑通过，三项 CI（run 38512625077）成功，已合并 90a62818c8d2b13bb4c74015c943dd1b7a7d7ef1。

最终公开 helper SHA256 841e009511a4d2417be480123eb3960399d5ba4a46fd26119bd69724bcac83cc 在 archive 安全路径检查定稿后，由 root 再次完整重放成功（原始 archive/201raw/56payload 未改）；本地 root-public-final-replay-report.json 绑定 manifest/helper/stdout 的 SHA256。Host upstream main 仍为 2454e5289e0442c0f93794b4a05a7a478f4b06ce；Ascend PR #50 仍 open/head 54d31aaf204c77df8102cf30f8111c5baf3acadd、mergeable=false。资格 cohort 不冒充当前 upstream main/source admission。

论文有限张量证据同步（2026-10-14，#194 已合并）

本地 generator 已执行完整 #193 archive/source-map 重放再取数：1 个非正式试验、56 份选定逻辑 K/V records、每 rank 28 named layers、201 raw rows、69 completion tokens。公开及隔离私有版本均仅用 Tectonic 0.15 编译，14 页总长 / 12 页正文 / 8 embedded fonts，PDF audit errors=0，private 宏与 public 宏变换完全一致；implication anonymity 仍未证明。首次正文 13 页失败的 audit 保留，压缩重复结论后通过，无字体/边距放宽。72 项现有论文检查全部 PASS（460.61s），evidence-summary --check / Ruff / diff check 均通过。完整归档 #193 已 exact-head CI 成功并合并；论文同步 PR #194 已发布，head d8702e7439b0ff9a1a6185aad3a82d42d75023c0 / tree bb93a1e75809aa01878586654e6b990418e3f341 与本地测试树一致，CI run 38514736905 三项 SUCCESS；root 按 exact head 合并 c116b127734bd6a63b86c9937ce187a94e381824。正式 H3/H4 仍 0，NO-GO 不变。

Attention R1 构建阶段历史（已完成；实际运行失败见下节）

PR #195 head 54b2d16e604e83a582d9899ebc154c13c9d810de / remote tree 7eddc6aa55d996b0006a3eafda6890f5f58ffbd4 已由 root 与本地冻结树核对；CI390/run38515172859 三项 SUCCESS，expected-head 合并为 ee0ca991b0f175d5c28de989d76701b46e273998。这只交付 CPU/source 候选的真实 PA/FIA 接点、入口 K/V prefix digest、stream completion、新collector/full-chain consumer；没有 attention NPU 结果或正式晋升。Root 用新环境精确 Torch2.13 独立重跑4个 byte-reader案例与冻结报告一致；默认Torch2.10首次版本断言失败记录保留。
唯一设备 owner 已准备新的普通复制环境，57,490 regular files/0 inode aliases；Host clean b02672dba79d2446d4da889bc436f12226ed6dba genuine wheel SHA256 d412be5f47acec68237bf300752b265e0ce7fcbaebb35f784e1e146fe0cc43da、2658 source/wheel/installed字节项一致。Ascend clean 92c7ab31996708e0c425f991707b387c8d3de8f3 真实 empty-target native build 同一 session54334 进行中，424/651；quiet interval 已实际核 /proc 有23matching processes（4R/19S/0D），不按观察超时重启。首次 backend source-import失败保留，同clean源码第二次build修正构建PYTHONPATH。实际 OPC Ascend910B1 与 requested ascend910b2 分开记录，物理卡3/6为910B2；不以编译标签或CPU fixture宣称运行兼容。新 wheel、准确tuple/source closure 完成后才冻结新recipe/nonce并launch；只读动态epoch observer已准备提前于API启动。原成功TensorR1与 #193完整raw不改。正式H3/H4仍0，NO-GO。

SOC 差异已按 pinned92c7/fcbb 七个未变 routing files 源审及分支复现确认：setup转交完整 ascend910b2，custom build shell按 ^ascend910b 折叠为 ascend910b family，const_var.py映射为 Ascend910B1 OPC；top-level kernel另收完整B2参数。不是简单忽略env，当前pinned路由无env-only精确B2 custom knob。保留actual compiler argv，运行兼容仍未知。Root随后只读 /proc 确认同构建29matching进程、4R/25S，不把quiet interval视为停止。

最新实际 Attention R1：HTTP500，原始失败保留；R2 修复正在执行

真实 Ascend empty-target native build 已完成全部 651 targets、exit0，clean source 92c7ab31996708e0c425f991707b387c8d3de8f3；wheel SHA256 bc31f0ebb37454809441dffdf6a1d4e0647625011aa97f9d5b0ccff180d9f16e，18,269,305 bytes。安装后 757 Py/ELF 项与 wheel 一致、750 source-owned Python 项与源码一致，五个 base wheel 与 Host/KV 的独立字节审计通过。首次 build 失败和实际 B1/B2 路由事实仍保留；build 成功不等于正式运行资格。

新 cohort /root/ecpa-selected-kv-attention-qualification-20261014-r1 在 2026-10-14T06:00:10.239671+00:00 冻结，cfg bcb1e2a6f3b6c4992d1ba2f87c8dde988b50f5b645e1e33d2390c4213b6a4379 / recipe 88852a70b63e46866144c0919796c05ccb2c852f904032f415553c89fb5f0da0 / owner d4a66109b5661050a691cf6edff4b1b4af49447bf2ef31a3dfc03b35720b3dcc。实际 NPU3/6 TP2 首次启动、port29505，原始 owner terminal exit1：HTTP500 / raw68 / typed tensor56 / native operator receipts0。response153B SHA256 21868750e8634ce54c6bfe07dff1b8b5dba67bf4f62c6186081d55af17694629；没有成功 response-metadata 文件，不能补造。五个 source kernel epochs gone、四 captured sessions 无残留成员、端口关闭、两卡无 running、watchdogs 未触发、cleanup_errors=[]。root 提前独立 observer 捕获 API/两个 worker 的匹配实际 kernel epochs；其诊断不代替 source role assignment 或预注册证据。

实际 worker traceback 在 FIA observer 报 native metadata/layer source binding changed。源码确认 pinned Host/Ascend builder 把同一个 metadata 对象分配给 28 层，而 #195 registry 仅按 id(metadata) 存储，最后一层覆盖此前层的绑定。此为源码归因；没有伪造运行时未采集的具体覆盖层调试值。原 CPU fixture 每层对象独立，未覆盖此真实 alias 行为。失败的56张量记录不升级为 attention 成功。

完整原始失败包本地已封存：287 members / 442,900,643 original member bytes，xz 75,342,984 bytes，SHA256 2a34eb69202c09605f476293295a057722272ff651b3df51494658988eeb8d2d。全部56 receiver payload、68 mixed rows、HTTP500、84source闭包、kernel/terminal、首次 missing-SHA CPU CLI 失败及两次真实 build 日志保留；公共归档发布正在推进，不能以哈希取代 payload。

修复 PR #197 immutable head 2e2e6b6bca493860ca016c9d308c1ada378701f2 / tree 62e85eda6e62b188c10bdeab544cafb9447f3920：binding 改为 metadata对象+实际 layer，仍保留 exact object/runtime/typed ACK/cache/clock guards，wrong-layer/object/clock 反例拒绝。实际 pinned builder 的 shared28layers×两 fixture ranks、完整 Unix/HTTP source regression 与独立复验通过；这些是显式 CPU fixture，不是硬件证据。CI396/run38547080539 尚进行中。sole owner 已构建独立 clean Host a222df060a364a4cce88f39b583f50ea87ef2749 的新 genuine wheel，安装2658字节项 audit PASS；R2 普通复制环境57,797文件/0 inode alias。Ascend全部 postimage 与92c7一致，复用真实bc31 wheel并复审字节，不重编未改变的651targets。待 exact-head CI 三项全绿合并、新完整 source freeze、新 nonce，直接 R2 两卡实际运行；旧 R1 和成功 Tensor R1 都不改。

正式 H3/H4 source-policy 与 semantic gate

#196 final head bcf571820e3293dc2449db90550303f1e45a9433 / CI394三项 SUCCESS，已合并 583168bf7e1842a5ba05613463d62bfa27ef89b0。新 campaign 必须提前显式声明完整 source tuple/policy；Manager/Host 保留 merged-main admission，Ascend/KV 显式 published-commit 或 merged-main；独立空 bare object store 从 canonical GitHub remote 验证 SHA/tree，不能把本地未发布 object 的 fetch 成功当 remote publication。旧 sealed receipts 不回填或追溯升级。

原 H3 25 cells×3 arms×3 starts=225 与 H4 4×9=36 的 prospective manifest 均 UNVERIFIED/executable=false/formal0。source-policy 修复不开放 semantic gate：现 formal Plan obligation、controller generation/lease/worker replacement 与新 typed/operator producer 尚未联结，formal traffic observer 仍拒绝 unverified semantic evidence。H1 正式9/9且 falsified、H2独立n4、H3/H4正式0、NO-GO保持。

R2 actual CPU freeze/preflight 已 exit0：/root/ecpa-selected-kv-attention-qualification-20261014-r2 / port29506，cfg 8ed09986fcadb98047e4edd9320a02f9c5222a85905bd43e0078a287675f37ec / recipe e63c0f77f6ad1567663756993050550ed7e2396b065494b5ea2cd05cf4075c6d / owner b40b2d427daa7049ad26a0e5fc8e37d043c6b05bb5ebe3435ae22ad16895ccee；84 source /43 native，new1201 prompt、oracle72 tokens。独立模型审计再次确认新 Host2658和复用 Ascend757安装项逐字节一致；root 独立冻结哈希核验通过，并已在API启动前运行只读29506 kernel observer。此时仅CPU前检，GPU尚未启动；仍待#197 exact CI绿自动合并，没有人工review等待。

R2 最新真实终态：新 source guard 拒绝，继续修复（2026-10-14）

#197 exacthead 2e2e6b6bca493860ca016c9d308c1ada378701f2 / CI396三项 SUCCESS 已合并 58a50adfcfdaa2154c10d661c449c5faee101d46。唯一 owner 以原 R2 freeze/new nonce 实际首次两卡运行，outer handle43004 terminal exit1；Manager1096055/API1096122/TP0 1096507/TP1 1096508/collector1097864，实际 native plan 8ce4a62d3352d15dfa4e448be05ac91bed9ac19df8149ec08a04ef08d25d5509 / launch 165397eb-9b29-47c9-955f-525d020bb5d1。Root 在 API 启动前运行独立 watcher，原 source 角色的三个 API/worker kernel epoch 均与实际捕获 PID/start_ticks/boot/session 匹配。

原 R2 HTTP500 / raw68（3start+9native+56typed）/ operator accepted0 / taskfalse / runnerfalse，response SHA同原153B错误body 21868750e8634ce54c6bfe07dff1b8b5dba67bf4f62c6186081d55af17694629，不是HTTP成功证据。共享metadata检查已越过；实际两worker traceback 到 observer verify_observation line367：native cache view fields/types unsupported。源码此校验在 native_call 返回与同stream synchronize之后，但原 native descriptor未发布入 journal，故不能伪造descriptor具体值或称已获得成功OP完成资格。原56typed payload和68raw均保留；cleanup_errors=[]、端口关闭、watchdogs未触发，没有重试或timeout重启。Root独立只读R2 failure report已保存、formalfalse/attentionNULL。

源码线索：KV witness.cache_view显式 int(torch_npu.get_npu_format(tensor))，而当前attention observer直接保存 vendor返回值并要求Python exact int。实际原typedref npu_format=2；nativeflatten的真实值/类型尚未落原记录，不能先验归因。sole owner正执行另一个预冻最小NPU tensor descriptor诊断（无model、无native OP资格、无formal role），采真实vendor callback Python类型/原observer返回字段；其结果不能升级旧R2。确定接口修复后使用新 source/wheel/nonce/cohort继续实际运行。

#198 head 145d2ef7bc75509a41c3d9c3234ff4daa495c944 更新内部 related-work/novelty audit的过期证据表，补真实 invocation-only HTTP authority、H2独立n4和完整selected logical KV archive，明确原H1 falsified、attention失败边界和NO-GO。不改变submission TeX/既有文学比较，不把有限资格当正式或性能结果；CI398进行中。正式producer桥继续实现prospective managedPlan identity、authority-held request enrollment、controller generation/lease/currentmembership验证，不后验改R2 native Plan。

最小真实双卡类型诊断 /root/ecpa-native-attention-descriptor-diagnostic-20261014-r1 已 terminal exit0，owned PID1100286 gone/sessionempty、NPU3/6 terminalclean。两个logicaldevices ×K/V/flatten 共8cases实际 torch_npu.get_npu_format 类型均为 torch_npu.npu._format.Format（IntEnum），exact type is int false、isinstance(int) true；witness显式int规范化，而attention原cache_view保留enum。诊断tiny5D backing实测Format.NCDHW=30，不冒充旧R2真实nativeview格式=2；原R2未采native descriptor值仍unknown。无model加载、无native attention调用、无formal producer注册，不算attention结果。Root逐项独立核验8cases、source observerbb11、终态/无资格边界，报告bind实际result SHA 4fc906732671e47c9e3e0d0c35049566da30cb31136241f934721199c2820936。authority正修prospective严格vendorenum→int接口，并保留错误类型/格式/指针/时钟拒绝；下一次仍需newHost source/wheel/closure/nonce/freeze。

#198 已核 exact head 145d2ef7bc75509a41c3d9c3234ff4daa495c944，CI398/run38548757378 wheel/3.10/3.12三项 SUCCESS，由root expected-head 合并 ed8a60820535cee86bce0095012d9428d6081726。Root另读取merged commit的 paper/related-work-audit.md blob 80fc9b8df0d000d7cea4dc022e219251ff24d2ca 与本地已检查/已提交文件一致；仅1个内部Markdown审计文件，不改submission TeX，无新增论文编译结果。#64 comment6166258402明确仍NO-GO/open，faithful baselines和完整formal semantic/matrix尚缺。

#199 严格格式接口修复与真实 ND2 前检（2026-10-14，第三轮尚未启动）

PR #199 immutable head 8f9066749bfa6f0a68685b16c7ee5b86343dfd83 / tree eedfd0c22d768ff1693091acd2b2b83e549529e9，parent为已合并#198；final observer SHA dfc01a62aa931bc998dba59133574a78130cbfe00ee29df980a5049db6c5bd28。只接受exact Python int或exact pinned vendor Format→plainint，已知格式码按vendor源绑定，拒bool/float/string/foreignenum/UNDEFINED/未知码；reference format/ptr/storage/hash/ACK/rank/layer/clock guards保留。vendor源码 _format.py SHA 8abe7bea6817f25d2360aee783afae16fe7fe2aaa46a04e7b7b865e7f2039488 实际字节另核，不把known codes当任意layout支持。新拒绝包含有界实际字段type/repr，仅exception log定位，不是atomic/fsynced OP fact或source ACK。58项source/fullUnix/portable、13vendor/patch回归、实际TorchCPU reader audit/Ruff通过；root对冻结源独立重跑13vendor测试PASS0.76s，显式CPUfixture。

sole owner已构建独立clean Host 5fff5ca734206b477b9bd1592cafdfec53054552 / genuine wheel SHA 9e4e2558a1b42161fbc9c150eeb6d54b1ab46127c857287e6361b978a2398555，2658source/wheel/installed项完全一致。Ascend92c7/bc31全部postimages/ELF未变，复用原真正empty-target wheel并审计，不重复651target编译。R3draft源闭包明确加入实际vendor file，新85source/44native，不仅改报告字段。

新独立真实接口诊断 /root/ecpa-native-attention-descriptor-diagnostic-20261014-r2：冻结新script/recipe，actual PID1105012 / start1100317862，双logicaldevice×K/V/flat=8cases，显式ND2 shared backing。真实getter仍返回vendor Format枚举，但新observer输出exact plainint2；全部8case完整descriptor与实际witness相等；6 synthetic bad callback负例均拒（不是6个NPU OP）。terminal exit0、owned epoch gone/sessionempty、3/6无running。没有model加载、nativeattention调用或producer注册，DIAGNOSTIC ONLY。root独立复核8case/6负例/源dfc/终态，actual result SHA 59052fa232668b17a048b8bc48ae0959737de542e4679e0ab338fa5bf2d8ac74 / terminal 6f7f4a5ba402feaa9d7aeb36cc64e3a5bc7e5f3893137bef49337bc577f8a3c6。原R2native descriptor值未补造。

旧完整 R2 失败档已封存并由root逐file独立核验：279members / 439,536,327 member bytes，xz76,471,368B SHA 05012f9ce15485ecbb7957a30277c6782bef818645d90d74b96fd27d2ed7ab18 / manifest a5e9257f306bdfb0fdd276ef07a0700a6739ae851b58ca137eed154ae815b816；56原始receiver payload、68raw、HTTP500、source/kernel/terminal全保留。旧R1 archive2a34与R2 archive0501都不能升级为成功。#199 CI400/run38551307615在运行，精确三job绿后expected-head合并→freshR3冻结nonce/recipe→唯一owner真实两卡运行，不等人工review。

第三轮完整 TP2 已实际启动（2026-10-14 10:52 UTC，尚无结果判定）

#199 head 8f9066749bfa6f0a68685b16c7ee5b86343dfd83 / CI400/run38551307615 wheel/3.10/3.12三项 SUCCESS，authority expected-head 合并 9f3cf909737946bdcf9625d2b47eb798dd81d2b5；root另fresh API复核merged/head/三job成功。Root独立读取该remote head五个关键模块的Git blob与local90a字节完全一致（observerdfc/consumerd5/collectorf86/Host-onlyCLI4e05/format-binding93bf）；local snapshot90a完整tree9276与remote199treeeedf不同，因#198paper审计文件，不伪称sameTREE。

新 R3 /root/ecpa-selected-kv-attention-qualification-20261014-r3 / port29507，实际冻结cfg 7dffd66750d8986f6e631e7822c7c8a338ce5ff8f13fade6b106b212eba34330 / recipe 5591bde636fa47344b35bf5a96b5f25f0f418b3433608fc581cfe3ffaee2527e / owner ccbd39a110638a65c89f0bed022c089d0196ca74804ca3be6d10bab0add54749。最终91source=原84+vendor1+6真实ABI输入；native44；七wheel/14model/真实tokenizer、SDK/vendor/ND2前检原件、180phase/1200overall、mode700 initially-empty private cache均提前冻结与独立审计。此前85source是draft，不冒充最终数量。root cfg/recipe实际哈希核对，并在API启动前实际启动只读kernel observer75333；不mint source角色。

sole owner singleouter实际handle60048已启动，同原冻结参数/新nonce/首次尝试，禁止旧R1/R2重新封装或超时重启。此时没有完整HTTP/56 OP/finalACK成功判定；新的ND接口前检仅诊断，完整Host模型运行尚待终态。H3/H4正式0、整体NO-GO保持，下一阶段继续真实managedPlan/source-owned request enrollment/controller-gen/lease/currentmembership桥，不将该资格候选当正式矩阵。

[OSDI '27] Submission-readiness epic and evidence gate #66

Description

当前主线：真实 MOD 组合（2026-10-19）

Actual next H3 execution

Actual Host fix, isolated runtime, and current r16 execution

Actual r12 failed attempt, unchanged

Actual H4 original order

Original scope and decision

当前执行总账（2026-10-17；Manager c7d873ee6224d93a95f95b5824f1ee6e69d551b7）

当前真实执行队列（2026-10-17 10:58 CST / 02:58 UTC）

H3 完整identity修复与后续实际队列（2026-10-17 11:14 CST / 03:14 UTC）

H2 证据范围复核（2026-10-17）

新进展：真实双MOD TP2功能已跑通；H3 native接线已合并，注册实跑定位剩余缺口（2026-10-17 03:12 CST）

H3/H4 接线的最新实跑状态（2026-10-17 03:57 CST）

当前纠错终态与下一运行（2026-10-16 21:58 UTC）

当前现场：旧超时已封存；新H3已注册并启动runner，H4已注册（2026-10-16 21:25 UTC）

首个冻结runner当前现场（2026-10-16 20:50 UTC）

H3 native注册成功，首个真实故障runner已启动（2026-10-16 20:27 UTC）

H3真实签发与H4全绿进展（2026-10-16 20:22 UTC）

最新真实运行终态：r12 第一次公开200，第二次503，整体仍FAIL（2026-10-16 16:49 UTC）

真实双 MOD 输入与 H3 接线当前状态（2026-10-16 17:13 UTC）

当前终态与新运行（2026-10-16 15:34 UTC）

当前进展：r11 已封存失败；仓库归属恢复；两项新 PR 待 CI（2026-10-16 15:20 UTC）

#223 已合并；r10 真实失败，r11 新组实际启动（2026-10-16 14:48 UTC）

正在发布的 runner / consumer 修复（2026-10-16）

用户质询后的正式 H3/H4 推进重点（2026-10-16）

#221 已合并：最终head完整CI通过；r17/source完成，r9终态FAIL已封存

当前主线与真实进展

原阶段时钟、CPU定位和下一步

当前固定运行范围与结果边界

#59–#65 逐项验收（2026-10-16 fresh GitHub读取）

#59 [OSDI '27][P0] Admit and execute the first formal-real three-arm study (H1) — closed

#60 [OSDI '27][P0] Validate a real authority-owned ExposureGate and process membership — open

#61 [OSDI '27][P0] Complete the version-skew, failure, and rollback campaign (H3) — open

#62 [OSDI '27][P0] Run the matched startup and steady-state overhead study (H4) — open

#63 [OSDI '27][P0] Replace the synthetic composition seed with a real multi-MOD oracle (H2) — open

#64 [OSDI '27][P1] Strengthen the systems novelty, baselines, and external-validity argument — open

#65 [OSDI '27][P1] Produce the anonymous, reproducible Tectonic submission artifact — open

Activity

ShuhaoZhangTony commented on Oct 12, 2026

ShuhaoZhangTony commented on Oct 12, 2026

ShuhaoZhangTony commented on Oct 12, 2026

ShuhaoZhangTony commented on Oct 12, 2026

ShuhaoZhangTony commented on Oct 12, 2026

ShuhaoZhangTony commented on Oct 13, 2026

2026-10-13 H2 source-bound candidate advanced (no formal scoring)

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

ShuhaoZhangTony commented on Oct 13, 2026

54 remaining items

ShuhaoZhangTony commented on Oct 14, 2026

ShuhaoZhangTony commented on Oct 14, 2026

ShuhaoZhangTony commented on Oct 14, 2026

Archived execution ledger snapshot (2026-10-14)

当前执行总账（2026-10-14；Manager f87bb29f3c5322d65d732055df9ea78f16d577bb）

最新 runner / 论文收口（#145–#147）

最新真实模型恢复与论文检查点（#148–#152）

持续窗口执行工具与模型论文（#153–#154）

最新真实连续模型窗口（#158 已合并）

当前发布检查点（#157–#158）

H2 独立计分纠正（当前审计，优先于历史 n=5）

原生身份交接及 H2 独立计分修正（#159–#160）

三臂真实 worker 故障进展（#161–#163；当前运行检查点）

封存发布与真实语义接口（#165–#167 已合并）

原生请求关联与收集通道（#168–#169；尚未硬件资格化）

原生 collector 验证修复与可执行请求链（#170–#171 已合并）

最新新 wheel 安装及真实 native 启动失败（2026-10-13 23:18 UTC）

KV 效果候选合并与新 r2 冻结（#172）

真实 native request/upload 第二轮终态（2026-10-13 23:27 UTC）

原始证据发布检查点（#173）

#173–#175 已合并与下一真实 KV 校准

当前论文与真实 7B 校准产物（2026-10-14）

新真实 KV 效果运行 r3/r4 与实际 hook 缺陷（2026-10-14）

#177–#178 合并、新 v2 硬件部分证据与下一请求预算

历史执行检查点（保留审计过程；旧状态不覆盖上方当前总账）

当前执行总账（2026-10-17；Manager `c7d873ee6224d93a95f95b5824f1ee6e69d551b7`）

当前执行总账（2026-10-14；Manager `f87bb29f3c5322d65d732055df9ea78f16d577bb`）

当前执行总账（2026-10-16；Manager `50dba4953d7ce17fc7c8f635dafe9321d6a5aa37`）