TAS-183: Single-run no-spill million-step closure

[AtlantisPleb]

Summary

• prove the article's long-horizon story without resumable scaffolding

Roadmap Position

• Phase: Phase 7. Close single-run posture, state discipline, and weight ownership
• Sequence: article-gap closure after TAS-156A
• Owned-route boundary: any canonical article route referenced here means the psionic-transformer-based route established by TAS-156A / TAS-160, not a reintroduced mixed implementation spread across model or runtime crates.
• Claim posture: necessary for article-equivalent closure, but not sufficient by itself to widen public capability claims

Description

• freeze the no-resume article operator envelope:
  • no checkpoint restore
  • no spill/tape extension
  • no external persisted continuation
  • one uninterrupted Transformer execution path
  • no hidden re-entry
  • no implicit segmentation
  • no runtime-controlled loop unrolling outside the model
  • no teacher forcing or oracle leakage
  • no dependence on oversized context windows as implicit external memory
• define:
  • token-stream continuity contract
  • step-to-compute consistency contract
  • allowed scheduling behavior
  • disallowed scheduling behavior
• require:
  • deterministic mode exactness
  • stochastic mode robustness without retry farming or lucky sampling
• constrain:
  • max context length relative to problem size
• run the selected fast route on the declared long-horizon workloads and
  require exactness, throughput floors, and explicit no-resume receipts
• perturb execution boundaries and require cheating routes to fail

Why This Matters

• this is where the current substrate and the article story diverge most

Primary Surfaces

• psionic-transformer (canonical owned article-route base for this issue)
• psionic-runtime
• psionic-serve
• psionic-eval
• psionic-research

Validation

• no-resume envelope declaration
• single-run horizon report
• execution-boundary perturbation tests
• step-to-compute consistency report
• context-length sensitivity report
• negative tests for checkpoint or spill markers
• negative tests for hidden re-entry or segmentation markers
• negative tests for teacher forcing or oracle leakage
• deterministic-exactness check
• stochastic-robustness check

Claim Discipline

• Keep machine-legible boundaries explicit; partial progress must not be presented as full article equivalence.
• Preserve typed refusal, fallback, blocked, and suppressed posture where closure is still incomplete.
• Keep public language bounded to the declared article envelope rather than implying generic arbitrary-program closure from a partial green result.

Done When

• the article no-spill operator gate is green