0.1 · Maximum-compatible admission
Cupel must accept ordinary TypeScript whenever the pinned reference build can ground and execute it. Native admission is decided per region, per compilation — never as a gate on the project.
0.2 · Reject promotion, not acceptance
A failed proof, unsupported mapping, or unavailable representation leaves the region in the capsule or an explicitly reported class. It never invalidates the reference application.
0.3 · Ceremony proportional to divergence
Where ordinary syntax is proved equivalent to the generated Go, it's accepted as-is. Explicit intrinsics are required only to establish invariants, select divergent behavior, express failure policy, or resolve what the toolchain can't certify automatically.
0.4 · Two categorical exclusions
Only class in the native closure and any (in any form) categorically block native admission — and they block admission only, not execution.
0.5 · No staged feature model
There is no "future language feature" category. Incomplete validator coverage is reported as implementation coverage — never described as a smaller language.
0.6 · Maximum legacy compatibility
Existing spelling, control flow, optionality, exceptions, iterators, generators, async, and built-ins are preserved wherever Go can reproduce grounded behavior. Rewrites are the last resort of six escalation steps.
[DEF]
True by definition or exact artifact identity
[CHECK]
Enforced by a deterministic checker
[CERT]
Established per compilation by a machine-checkable certificate
[TEST]
Supported by tests, differential execution, fuzzing, benchmarks — not a universal proof
[TCB]
Trusted from a pinned toolchain, runtime, OS, or checker
A [TEST] result must never be reported as [CERT]. The same discipline Lore applies to receipts, applied to compilation claims.
K1 · TRANSLATION-VALIDATOR SOUNDNESS
Production-grounded: if the validator accepts, the generated Go refines the grounded artifact.
K2 · SEMANTIC OPERATION ADEQUACY
Every primitive and representation used is covered by the installed certified kernel.
K3 · WIRE & INTEROP CORRECTNESS
The canonical value-only boundary round-trips; request/response contracts hold.
K4 · GUARDED CONTAINMENT
Guard failures roll back staged state — every failure path is contained and reported.
K5 · ACCEPTED-EFFECT PREFIX
On failure, observed effects form a declared, accepted prefix — no phantom writes.
K6 · HYBRID COMPOSITION
Native regions, capsule regions, facades, and the host compose into one refining system.
MAIN CERTIFIED RESULT
Run(⟨G, C, W, F, Nθ, H, Σ⟩) ≈ΩF RunNθ(Jprod)
When every executed native region is CEN or MN-CERT, every remaining region is exact capsule, and every selected profile is exact — the hybrid system refines the grounded production project. Small trusted validation kernel; no fully trusted optimizing compiler.
— that every source region becomes readable native Go
— that machine-generated state-machine Go is readable decomposition
— that passing tests proves universal equivalence
— that native Go is automatically faster than V8
— that native coverage is a measure of performance by itself
— that Go and JavaScript garbage collectors behave identically inside
— that stack traces, wall-clock timing, or exhaustion points always match
— that TypeScript's type checker is a proof of representation safety
— that rich shared object identity crosses the strict value-only boundary