Prove one exact-main single-instrument mission with immutable readback

[proerror77]

Parent

#580

What to build

Run one bounded exact-main instance of alpha-harness mission execute for one approved venue, symbol, and horizon using fresh content-bound CEX materialization and event-replay inputs.

Publish the result once, independently read it back, and verify every artifact and hash in the complete first vertical slice. This is runtime evidence, not code implementation or authority to activate Paper, Shadow, or LiveSmall.

The issue must remain needs-info until every Runtime control field below is replaced with a concrete value and all native blockers are closed.

Runtime control

Target: Pending — exact environment, namespace/job, venue, market, symbol, horizon, dataset/snapshot, and result destination must be supplied.

Candidate: Pending — exact origin/main SHA, immutable image digest, configuration hash, Mission hash, collector/source revision, and rollback image/configuration identities must be supplied.

Controller: Pending — one named human or automation controller must be supplied.

Stop rule: Pending — bounded resource/time limits, holdout-open limit, data/replay failure conditions, publication conflict, and LiveSmall prohibition must be supplied.

Rollback: Pending — exact prior image/configuration or job-stop identity, procedure, cleanup boundary, and immutable-evidence retention rule must be supplied.

Acceptance criteria

• Before transition to ready-for-agent, every Runtime control field contains a concrete, non-placeholder value and all native blockers are closed.
• Candidate code and image are built from the recorded exact origin/main SHA.
• The run uses a fresh CEX materialization and replay input bound to the recorded exact collector/source revision; stale snapshots are not treated as current evidence.
• One typed Mission selects exactly the approved venue, market, symbol, and horizon.
• The bounded run emits GP accepted/rejected evidence, Factor Bank, both baselines, MCTS subset/checkpoint, fixed weights, four-stage strategy, combination walk-forward, L2 replay receipt, precommit, and zero-or-one sealed receipt.
• Replay readback reports queue position, partial fills, market impact, and true capacity honestly and makes no full-L3 claim.
• The holdout is opened at most once for the exact precommit, with retry/conflict evidence recorded.
• Any promotion and bundle hashes validate independently against the precommit and sealed receipt.
• The result destination is create-once and refuses overwrite.
• Independent readback verifies source SHA, image digest, Mission, input manifests, configuration, artifact identities, result bundle hash, and terminal state.
• No Paper, Shadow, or LiveSmall activation occurs without a separate explicitly authorized runtime contract.
• LiveSmall remains rejected.
• The named controller records exact target, candidate/configuration identity, rollback identity and procedure, stop rules, terminal result, and cleanup evidence.
• Closure uses the repository runtime-evidence process and records Acceptance checks: and Result: passed.

Blocked by

#605

[proerror77]

Exact-main readiness readback — 2026-08-17

Code predecessor #605 is complete: PR #906 was squash-merged and independently read back at origin/main@828ada8021b3ebdc30639d04c6adb1f152e1cefd. This is Code/Merge evidence only.

Read-only runtime preflight against context monday-research-apne1 found one Ready node labeled workload=system and no node labeled workload=backtest. Attempts 001–003 (#612, #630, #635) already terminated EVIDENCE_REJECTED under the same ResourceNotMatch / no matching backtest nodepool condition. The relevant runtime input has not changed, so no attempt 004 was created.

The issue correctly remains needs-info: a concrete schedulable target (or separately authorized nodepool change), exact new image/configuration/mission/rollback identities, and named controller/stop rules must be supplied and read back before transition to ready-for-agent. No Job, Secret, image, OSS object, Paper, Shadow, LiveSmall, collector, order, or trading mutation occurred.

[proerror77]

Fresh exact-main preflight correction — 2026-08-17

The earlier ResourceNotMatch note is no longer the complete current blocker.

• Code/CI/Merge: PR fix(research): remove LiveSmall bootstrap cycle #908 is merged at origin/main@3da03f455479a76e9b86377f5a03edcc5fde1601.
• Release: exact-source research image is research-runner@sha256:0f0aa6ec20d216ca70ccfdceadadf95615c35f67c3f1618ef212550e75dc394d and its publish/readback workflow passed.
• Data: fresh USD-M reference triplets are being produced and uploaded, but the required account-bound fee lane is not deployed and no fee artifact exists; Binance fee dataset never lands in OSS #887 now records the missing credential and Runtime stop.
• Capacity: nodepool npa509e34c913c45a59a33b805a66267e5 is active with autoscaling 0..1, exact labels workload=backtest and research.monday/node-pool=cex-research, but currently has zero nodes. Its latest scale-out attempts failed with InvalidAccountStatus.NotEnoughBalance, not ResourceNotMatch.
• Namespace quota is empty; there are no Pending or Running research Pods.

Terminal result: still needs-info; no attempt 004 created. The next valid attempt requires both an authorized fee credential producing a fresh bracketed fee triplet and restored Alibaba postpaid capacity, followed by concrete Mission/config/result/rollback identities. No Job, Secret, Paper, Shadow, LiveSmall, order, or trading mutation occurred.

[proerror77]

Current-main research release readback — 2026-08-17

• Code/Merge source: origin/main@b23097a350e6f3a0b03bfdba8ee272711570523b.
• Authenticated source CI: Prediction Markets CI run 31997836663 completed success; the Research image binaries job produced the source-bound artifact.
• Automatic ACR release: run 31999570741 completed success from workflow_run for the same head SHA.
• Immutable image: crpi-ygobwehhof7qs9m3.ap-northeast-1.personal.cr.aliyuncs.com/wildcard0923/research-runner@sha256:f63d9e5a9a2b862a811e9fba0fb20c39994d3ef1aed0c6c77e52e9f92d247415.
• Release readback pulled that digest, required org.opencontainers.image.revision == b23097a…0523b, verified alpha-harness reports the same source, and confirmed hft-backtest, alpha-harness, lob-pit-materializer, binance-replay-parquet-materializer, monday-prediction-research, monday-prediction-evaluator, and monday-prediction-snapshot are executable.

This advances Release only. No attempt 004 is created: issue #887 still lacks the authorized Binance account credential and fee triplets, and the exact backtest nodepool npa509e34c913c45a59a33b805a66267e5 remains active/autoscaling 0..1 with desired/healthy/total 0/0/0. The cluster still has no workload=backtest node and no Pending/Running research Pod. Paper, Shadow, LiveSmall, order, and trading state remain untouched.

[proerror77]

Attempt 004 preconditions re-read — 2026-08-17T06:15Z

The exact current-main research image remains:

crpi-ygobwehhof7qs9m3.ap-northeast-1.personal.cr.aliyuncs.com/wildcard0923/research-runner@sha256:f63d9e5a9a2b862a811e9fba0fb20c39994d3ef1aed0c6c77e52e9f92d247415

ACK readback for cluster c4d1db514b47a4c40995d2ec4bcc8c0ca and nodepool npa509e34c913c45a59a33b805a66267e5 is unchanged:

• nodepool state active, autoscaling 0..1, desired/healthy/total 0/0/0;
• instance type ecs.u1-c1m4.xlarge, charge type PostPaid, spot strategy SpotAsPriceGo;
• cluster has only the system node; no workload=backtest node and no research Pod;
• QueryAccountBalance still fails with AuthSiteFail (request 01A00E5C-D248-32C9-BD65-8F28228D939D), so there is no new balance/capacity evidence.

The authorized Binance fee input is also still absent per #887. Because neither failed input changed, no unchanged scale retry and no attempt 004 were created. Paper, Shadow, LiveSmall, orders, and trading remain untouched.

[proerror77]

Release prerequisite readback (2026-08-17):

• Code/Merge: PR fix(research): package market tape slicer in runner #913 merged as 369fcffde72324fffd236c56eea457de8f5a3088.
• CI: Prediction Markets CI run 32009660207 completed success for that exact SHA. Research image binaries, Research image smoke, and the final gate all passed.
• Release: automatic Publish ACR Images run 32010578020 completed success, sourcing artifact run 32009660207 with both authenticated source jobs successful.
• Immutable image: crpi-ygobwehhof7qs9m3.ap-northeast-1.personal.cr.aliyuncs.com/wildcard0923/research-runner@sha256:d7e0376340be6f5351d78607701e14edeb7a7175e4abfaac195114ee3a9f2c9e.
• Direct image verification: source label equals 369fcffd...; all eight entrypoints are executable; binance-market-tape-slicer --help and binance-replay-parquet-materializer --help both succeeded.

This closes only the release-packaging prerequisite. It is not ACK Runtime or Mission readback. No Mission attempt is created until current ACK capacity and the real Binance fee triplet are independently proven.

[proerror77]

Attempt 004 preconditions refresh — 2026-08-17T08:32Z

• Exact release remains origin/main@369fcffde72324fffd236c56eea457de8f5a3088 and research-runner@sha256:d7e0376340be6f5351d78607701e14edeb7a7175e4abfaac195114ee3a9f2c9e.
• QueryAccountBalance now succeeds (RequestId 01A00ED9-6BFC-5C21-8780-9EAF799B8A83) with CNY 99.83 available. This is a changed capacity input, not proof of a schedulable node.
• Nodepool npa509e34c913c45a59a33b805a66267e5 is still active/autoscaling 0..1, desired/healthy/total 0/0/0; the cluster has only the system node and no research Pod. No scale retry was made because the required fee credential is still absent.
• Cloud Assistant invocation t-jpn6u90obcxqqkg confirms the fee credential, binaries, units, spool, and therefore the real fee triplet are absent. The USD-M reference collector and upload timer are healthy with fresh success at 2026-08-17T08:32:26Z.

No attempt 004, node scale, Job, Secret, Paper, Shadow, LiveSmall, order, or trading mutation was created. The next bounded action is provision the existing credential contract, deploy the authenticated fee release, read back a fresh bracketed fee triplet, then test the changed capacity input.