TAS-151: Declared universal substrate model (`TCM.v1`)

[AtlantisPleb]

Summary

Public Tassadar needs declared universal substrate model (tcm.v1) so the executor lane can widen honestly without collapsing profile boundaries, portability, or refusal posture.

Roadmap position

• Tranche: Tranche M | Universal-computation closeout
• Strategic phase: Phase 11 terminal closeout
• Tranche goal: Make Turing-complete support a benchmarked, challengeable terminal contract.
• Why this tranche exists: This is the theorem-to-product bridge that turns the universality path into an explicit end-state contract.
• Dependency context: Starts Tranche M after the earlier tranches establish the minimum prerequisites.

Problem

The roadmap now has many widening tracks, but no single declared machine model that the final "Turing-complete" claim refers to.

Hypothesis

A declared Psionic/Tassadar universal substrate model with explicit control, memory, continuation, checkpoint, spill/tape, and refusal semantics will make the terminal claim precise instead of rhetorical.

Public source anchors

• docs/ROADMAP_TASSADAR.md
• docs/ARCHITECTURE.md

Target surfaces

• psionic-ir
• psionic-runtime
• psionic-provider
• docs/

Claim class

• execution truth / claim-discipline

Initial scope

• implement the smallest honest subsystem changes across psionic-ir, psionic-runtime, psionic-provider, docs/ that close the named gap
• add deterministic fixtures, receipts, reports, or capability rows that make the new posture machine-legible
• update public docs and capability language only where the new bounded surface is actually supported
• keep unsupported shapes on explicit typed refusal paths rather than widening implicitly
• make the terminal claim refer to one declared substrate and explicit witnesses, not to broad or rhetorical universality language

Validation and benchmark expectations

• model-schema validation
• machine-step semantics
• refusal rules for out-of-model features
• and cross-reference checks against the named profile ladder
• add negative coverage for unsupported or out-of-profile behavior
• update any machine-readable receipt, report, capability row, or acceptance artifact touched by this lane

Claim-discipline requirements

• keep the capability bounded to named profiles or declared semantic windows
• do not let this issue imply arbitrary Wasm, broad internal compute, or broader served posture unless an explicit promotion gate is part of the task
• preserve explicit refusal reasons for unsupported module shapes, effects, portability envelopes, or semantic families
• keep theory-green, operator-green, and served-green verdicts separate; no terminal claim should silently widen public posture

Done when

• the named surfaces land with deterministic tests, fixtures, or reports that exercise the new bounded capability
• public docs reflect the new capability, limit, or refusal posture in bounded language
• the claim remains benchmarked or promoted only at the level explicitly supported by the landed evidence

Status

• seeded