Stable failure meanings and admission order.
Core-2 Diagnostics
Status: normative preview; incremental diagnostic producers available (see below)
C2-DIAG-001 — Envelope and meanings. Inherit the Core-0 structured diagnostic envelope, source spans, related locations, severities and stable ordering. The following codes have fixed meanings within Core-2. Existing codes are not reassigned. Artifact/provider errors without source positions identify the offending record/request and related subject identities.
| Code | Meaning | Governing clauses |
|---|---|---|
| ZL-C2-EDITION-0001 | bare stable Core-2 selected before activation | C2-PREVIEW-001, C2-GATE-001 |
| ZL-C2-PREVIEW-0001 | feature requires physics-preview or a later supported tranche | C2-PREVIEW-001 |
| ZL-C2-UNSUPPORTED-0001 | valid specified feature/provider/encoding is not implemented | C2-SRC-002, C2-ART-004 |
| ZL-C2-SYNTAX-0001 | malformed Core-2 declaration | C2-SRC-001, C2-SRC-002 |
| ZL-C2-ELAB-0001 | nonfinite/recursive elaboration or invalid instance binding | C2-HW-001, C2-HW-002 |
| ZL-C2-DRIVER-0001 | missing/conflicting driver, direction mismatch or invalid resolution | C2-HW-003, C2-LOGIC-003 |
| ZL-C2-LOGIC-0001 | invalid width/type, X/Z conversion, zero divisor or invalid resolution law | C2-LOGIC-001, C2-LOGIC-002, C2-LOGIC-003, C2-LOGIC-004 |
| ZL-C2-CLOCK-0001 | invalid clock/reset/state ownership or ambiguous clock event | C2-CLOCK-001, C2-CLOCK-002 |
| ZL-C2-CDC-0001 | missing/incompatible clock or discipline bridge | C2-HW-004, C2-CLOCK-003, C2-BRIDGE-003 |
| ZL-C2-ASYNC-0001 | unadmitted feedback, delay, hazard or progress assumptions | C2-ASYNC-001, C2-ASYNC-002 |
| ZL-C2-INTRINSIC-0001 | device/target/environment/measurement envelope mismatch | C2-INTRINSIC-001 |
| ZL-C2-DIMENSION-0001 | inconsistent physical dimensions, shape or frame | C2-PHYS-002, C2-PHYS-004 |
| ZL-C2-MESH-0001 | invalid mesh/connectivity/orientation/support or projection | C2-PHYS-003, C2-PHYS-007 |
| ZL-C2-MODEL-0001 | invalid equation, condition, analysis or constitutive assumptions | C2-PHYS-001, C2-PHYS-004, C2-PHYS-005, C2-LIB-001 |
| ZL-C2-BRIDGE-0001 | invalid mixed-signal transfer, uncertainty or coupling law | C2-BRIDGE-001, C2-BRIDGE-002 |
| ZL-C2-REALIZATION-0001 | incompatible refinement, observation map, profile or claim latitude | C2-REAL-001, C2-REAL-002, C2-REAL-003 |
| ZL-C2-EVIDENCE-0001 | failed, stale, unsupported, inconclusive or incomplete required evidence | C2-REAL-004, C2-EVID-001, C2-EVID-002, C2-EVID-003 |
| ZL-C2-CAPABILITY-0001 | missing/expired/mismatched operation authority | C2-CAP-001, C2-ADAPTER-005 |
| ZL-C2-BOUNDARY-0001 | forbidden crossing, effect omission or unrecorded irreversible action | C2-EFF-001, C2-BOUND-001, C2-BOUND-002, C2-BOUND-003 |
| ZL-C2-ARTIFACT-0001 | malformed/tampered/noncanonical graph, byte transport, identity or projection | C2-ART-001, C2-ART-002, C2-ART-003, C2-ART-009, C2-ID-001, C2-IFACE-001 |
| ZL-C2-ADAPTER-0001 | malformed protocol/result/report or target-tool incompatibility | C2-ADAPTER-001, C2-ADAPTER-002, C2-ADAPTER-003, C2-ADAPTER-004 |
| ZL-C2-SOLVER-0001 | incompatible plan, missing numerical facts or failed solve criteria | C2-SOLVER-001, C2-SOLVER-002, C2-SOLVER-003, C2-SOLVER-004, C2-PHYS-006 |
| ZL-C2-CONVERGENCE-0001 | event, step, coupling or numerical convergence bound exhausted | C2-ASYNC-002, C2-BRIDGE-002, C2-SOLVER-003 |
| ZL-C2-INDETERMINATE-0001 | physical action may have occurred without reconcilable receipt | C2-BOUND-003, C2-ADAPTER-005 |
C2-DIAG-002 — Admission order. First validate transport/framing and
edition/preview support, then syntax/typed graph integrity, elaboration and
model constraints, boundary/capability admission, execution, and evidence
promotion. Within a phase, report independent failures in inherited stable
diagnostic order; do not invent later-phase results after a prerequisite fails.
When an implementation cannot analyze a valid requested feature, report
unsupported instead of pretending to have checked its deeper semantic errors.
Checked two-state conversion failures are owned runtime errors with the
indeterminate bit index; illegal implicit conversions are static diagnostics.
The discovery surface emits ZL-C2-EDITION-0001,
ZL-C2-PREVIEW-0001, and ZL-C2-UNSUPPORTED-0001 today. Source inspection
also emits ZL-C2-SYNTAX-0001 with parse-phase byte spans and independently
recovers at subsequent top-level declarations. It retains inherited lexical
diagnostics and newline-delimited structured transport. Structural hardware
inspection additionally produces ELAB, DRIVER, LOGIC, CLOCK and CDC failures
with the offending construct’s span; its current unsupported subset remains
explicit. Native authority guards produce CAPABILITY and BOUNDARY failures;
the owned action journal reports INDETERMINATE when an outcome or its durable
receipt cannot be established. Its typed views retain the request, attempt,
scope and uncertainty reason. The native combinational simulator additionally
reports CONVERGENCE for binding step/sample limits and DRIVER/LOGIC/CLOCK for
invalid typed input batches, without partially publishing settled state or trace.
The pure physical quantity layer reports DIMENSION for incompatible dimensions,
shape/frame mismatches and invalid affine arithmetic, and UNSUPPORTED for its
finite carrier/rank bounds. It grants no model or solver authority.
The canonical mesh layer reports MESH for invalid topology, orientation,
ownership and support; DIMENSION for incompatible coordinate units or field
spaces; and UNSUPPORTED for its geometry and resource bounds. An unresolved
interface-law identity is retained as an obligation, never a validity result.
The native model typing layer reports MODEL for invalid equations, material
dependencies, conditions, test spaces, analyses and structural constraints;
DIMENSION for incompatible operator/norm units or field spaces; MESH for invalid
support; and UNSUPPORTED for finite profile bounds. Well-posedness, function
domains, symbolic compatibility and composed-derivative regularity can remain
inspectable obligations on a successfully constructed definition.
The native conservative transfer layer reports MESH for incompatible maps,
changed geometry/support and broken lineage; DIMENSION for field/error type
mismatches; SOLVER for negative or exceeded numerical error bounds; and
UNSUPPORTED for transfer profile/resource limits. Its measured errors are
relative to supplied finite reference coefficients, not physical validation.
Static solver-plan construction reports SOLVER for incompatible dependencies,
spaces, methods, resources, incomplete analysis closure, weakened tolerances or
invalid shared generation budgets. UNSUPPORTED covers finite construction limits
and generated-code requests without ordinary language admission. A checked plan
does not imply numerical convergence, execution authority or physical validity.
Other codes specify future implementation
behavior. None implies source execution or physical validity.