TAS-101: Cross-machine portability envelopes and broad-internal-compute acceptance gate

[AtlantisPleb]

Summary

Publish cross-machine portability envelopes and a broad-internal-compute acceptance gate so wider profile publication stays tied to reproducibility instead of one lab setup.

Problem

The article-closeout tranche is necessary, but it is not enough for broader internal-compute claims.

Current starting point:

• docs/TASSADAR_WASM_RUNBOOK.md is now the canonical bounded-Wasm operator runbook for the article-closeout flow.
• The current queue already has the article-closeout machine-facing issues: TAS-092 (cross-machine CPU reproducibility and floor matrix), TAS-093 (Rust-only article acceptance gate v2), and TAS-094 (Rust-only article closeout audit).
• crates/psionic-runtime/src/lib.rs already carries explicit effective-backend and backend-mismatch surfaces in the broader runtime substrate.
• fixtures/tassadar/reports/tassadar_exact_compute_market_report.json still marks the current execution-unit registration as runtime_backend=cpu and settlement_eligible=false.

That is enough for honest article closure. It is not yet enough for broad internal-compute profile publication across multiple backends, toolchains, or machine classes.

Hypothesis

Portability envelopes plus a general-compute acceptance gate will keep wider profile publication tied to reproducibility, operator receipts, and explicit backend-sensitive refusals.

Source Papers / Docs

• Can LLMs Be Computers?
• docs/ROADMAP_TASSADAR.md
• docs/TASSADAR_WASM_RUNBOOK.md
• docs/ARCHITECTURE.md

Target Surfaces

• psionic-eval
• psionic-runtime
• psionic-provider
• psionic-serve
• psionic-environments
• docs/
• fixtures/tassadar/reports/

Initial Scope

• Define portability envelopes keyed by profile id, backend family, toolchain family, and machine class.
• Add a broad-internal-compute acceptance gate that extends beyond the article-closeout gate.
• Publish operator-facing portability and drift reports for named profiles.
• Suppress capability publication when a profile drifts outside its declared portability envelope.
• Keep backend-sensitive and toolchain-sensitive refusals explicit instead of treating them as minor implementation details.

Benchmark / Tests

• Cross-machine and cross-toolchain matrix tests for named internal-compute profiles.
• Effective-backend mismatch and drift-suppression tests.
• Acceptance-gate tests that fail when portability, receipts, or refusal suites are incomplete.
• Operator runbook drills on the declared portability matrix.
• Regression tests ensuring the article-closeout gate remains separate from the broader acceptance gate.

Claim Discipline

This issue is about deployment closure. It must not be closed by the article-only reproducibility matrix, by one green machine run, or by treating backend drift as an operator footnote.

Done When

• Tassadar publishes portability envelopes for named post-article profiles.
• Wider profile publication is blocked when portability evidence is incomplete or stale.
• The acceptance gate for broad internal compute is green only when reproducibility, receipts, and refusal suites all pass.