fetching from cluster…
Every failure mode Phylanx can attest to lives in this table. Each entry is a fixed bit position, an English description, a severity, and the OWASP references that anchor the label to the wider AI-security literature. The bit layout is frozen — pin tests in phylanx-oracle/tests/diagnosis treat any drift as a breaking on-chain change.
Schema version v1 · 42 failure modes · 24 remediation codes.
These are the authoritative diagnosis labels. The Phase-2 cert v2 will threshold-sign these bits; consumers should branch on them, not on the legacy detector trace bits below.
D2 honesty note — the low-32 bits are passthrough trace bits from the legacy detector bitset. They explain WHY a score is low but are NOT full taxonomy entries. They share the bitmask only because the on-chain field was reserved as u64 and the upper 32 bits hold the v1 diagnosis surface. A consumer building an audit pipeline should switch on the high-32 labels — the low-32 set is informational.
Every failure mode declares a default-remediation bitmask. The codes below are the bit-by-bit playbook the cluster surfaces alongside the diagnosis.
Phase-1 (today) serves the diagnosis off-chain with the attestation tag off_chain_v1. The data is faithful to the cluster's epoch_runner output but is NOT yet threshold-signed. Phase-2 lifts the same shape into cert v2 with the tag cert_v2. The wire contract is explicit so a downstream auditor can branch on the literal.