Manuscript Oai280-C@1 · Oai280-C.tex · section · 7d44b8c0

Operational maps and interpretation

Operational maps and interpretation · lines 2009–2059

Back to manuscript

A reported map should contain, for each tested task:

AccessTargetIdeal benchmarkAudit/resourcesIntervalDecision
Declared registersEffect, code, subsystem, or algebraTheorem and modelSupported contract and scoped budgetsCertified, specified-decoder excluded, or inconclusive

An all-decoder exclusion is a separate annotation supported by Proposition prop:optimal, not by failure of a sufficient certificate. With unsupported transfer or calibration assumptions, the result is inconclusive rather than certified.

-dependent access. The connected model in Section sec:patch is a finite two-cell perfect-tensor code. Its graph specifies contractions and accessible legs. We do not identify its regions with continuum entanglement wedges. A comparison is called geometry-dependent only when changing the graph or contraction pattern is shown to change the channel, the attainable recovery, or a resource-constrained recovery class.

gravitational obligations. This paper does not construct a gravitational dictionary, establish a semiclassical regime, identify a continuum boundary algebra, or derive a metric from its recovery map. The source notes report additional same-model endpoint obligations in En07-B but do not supply their full statements CheungEn07B. No such obligation is treated as proved or as a premise here.

recovery problems. The internal identifiers OpenAI 280, 283, 290, and 365 are described in the supplied notes as involving, respectively, conformal-net extensions, unitary synthesis, bicentralizer questions, and geometric inverse recovery. None is used to infer a decoder, an implementation certificate, a radiation history, or a gravitational metric. Coincidence of the word “recovery” is not an interface theorem.