{"slug":"failure_case_registry","filename":"failure_case_registry.csv","schema_markdown":"# failure_case_registry.csv\n\n**Purpose:** declares the failure modes you have observed in practice on\nthe live system, so Bridge can analyze whether your evaluation evidence\ncovers the failure space honestly.\n\n**Required columns:**\n\n| Column | Type | Required | Description |\n|---|---|---|---|\n| `failure_id` | string | yes | stable identifier for this failure mode within your incident registry |\n| `failure_description` | string | yes | what happens when this failure mode occurs (≤500 chars) |\n| `severity` | enum | yes | one of: `low`, `medium`, `high`, `critical` |\n| `frequency_estimate` | enum | yes | one of: `once_observed`, `rare_weekly`, `regular_daily`, `frequent_hourly`, `continuous` |\n| `affected_variants` | string (semicolon-separated) | yes | semicolon-separated list of `variant_id` from `unified_variant_comparison.csv` that exhibit this failure |\n| `affected_slices` | string (semicolon-separated) | no | semicolon-separated list of `slice_id` from `current_slice_metrics.csv` (omit if cross-slice) |\n| `first_observed_date` | ISO-8601 date | yes | when this failure mode was first documented |\n| `mitigation_status` | enum | yes | one of: `none`, `partial`, `complete`, `accepted_risk` |\n| `notes` | string | no | free-form notes including reproduction recipe |\n\n**Minimum row count:** ≥1 (zero-failure systems are either too new to evaluate or hiding evidence; Bridge will flag)\n\n**Example:**\n\n```csv\nfailure_id,failure_description,severity,frequency_estimate,affected_variants,affected_slices,first_observed_date,mitigation_status,notes\nF001,Pipeline timeout under high concurrency >200 RPS,high,rare_weekly,v_pipeline,geo:us-east;geo:eu-west,2026-04-12,partial,added circuit breaker\nF002,Verifier agent hallucinates approval on adversarial input,critical,once_observed,v_pipeline,,2026-05-03,partial,prompt-hardening in progress\nF003,Token cost spike when planner+executor enter retry loop,medium,regular_daily,v_pipeline,tenant:enterprise,2026-03-22,accepted_risk,cost monitoring in place\n```\n\n**What this CSV is NOT:**\n- Not a bug tracker export (Bridge wants failure-mode taxonomy; not every ticket)\n- Not a post-mortem document (post-mortems are useful but not the structured shape Bridge consumes)\n- Not aspirational (must be failures actually observed; hypothetical/planned-for failures should NOT appear)\n\n**Canonical source:** `bdc-bridge-passport` repository at frozen SHA recorded in `PASSPORT_REPO_PIN.md`.\n","page_url":"/passport/schemas/failure_case_registry","template_url":"/passport/template/failure_case_registry","canonical_source":"https://github.com/malishomen/bdc-bridge-passport"}