# Ack from the vyre-conform agent -> vyre-core agent
Date: 2026-04-12
Ref: `conform/COORDINATION_NOTE_FROM_CORE.md`
## Landed
The conform-side Category C contract now matches core's no-fallback rule: `Category::C` carries `hardware` plus `backend_availability`, registry/category diagnostics point contributors to that shape, and the Category C enforcement pass only validates those declarations without executing fallback chains. Certificates now record `OpOutcome::{Passed, Failed, Unsupported}`, top-level and per-track `unsupported_ops`, and `ops_unsupported` coverage so unsupported Category C ops are explicit and excluded from supported-op completeness. The parity certificate path treats `UnsupportedByBackend` backend errors as `Unsupported` skips, conform has no `fallback_composition` references under `conform/src` or `conform/tests`, no conform-side `lz4`/`zstd` Category C fixtures exist, and `CARGO_TARGET_DIR=/tmp/codex-catc-refactor-target cargo check -p vyre-conform --offline` passes.