Stable structured diagnostics for cumulative Core-1 previews.
Core-1 Diagnostics
Status: normative preview
Core-1 inherits the Core-0 structured diagnostic envelope and adds these fixed meanings:
| Code | Meaning |
|---|---|
ZL-EDITION-0001 |
stable Core-1 was selected without an active cumulative preview |
ZL-PREVIEW-0001 |
a declaration or artifact needs a later cumulative preview |
ZL-DOMAIN-0002 |
legacy workflow spelling used where Core-1 requires flow |
ZL-DOMAIN-0003 |
a callable was submitted without its required typed runtime admission or live authority |
ZL-DOMAIN-0004 |
a direct call crosses domains without a typed boundary |
ZL-EFFECT-0001 |
an effect set is missing, malformed, unknown, duplicated, or noncanonical |
ZL-EFFECT-0002 |
a caller does not contain every callee effect |
ZL-PORTABLE-0001 |
a portable set is empty, duplicated, invalid, or used with open/override semantics |
ZL-MODALITY-0001 |
a Core-1 message omitted its required interpreted or compiled modality |
ZL-MODALITY-0002 |
native/JIT/AOT admission reached an interpreted message in the dependency closure |
ZL-MODULE-0003 |
malformed, noncanonical, tampered, or unsupported ZLM2 artifact |
ZL-STATE-0001 |
an unknown or unsupported closed state intrinsic was used |
ZL-FLOW-0001 |
a durable flow definition has an unsupported shape or invalid node/schema/retry/deduplication facts |
ZL-FLOW-0002 |
a source flow boundary or restored history does not match its checked definition |
ZL-OPTIMIZE-0001 |
a finite optimization definition has an unsupported shape, signal signature, identity, or budget |
ZL-OPTIMIZE-0002 |
a source optimizer boundary does not match its checked problem definition |
ZL-DOMAIN-0001 retains only its Core-0 deferred-domain meaning. It is not
reassigned by Core-1.