Skip to content

6 corpus cases added to baseline by the admission batch: 3 ranking, 1 missing k8s channel, 2 similarity-only gold #226

Description

@nikolay-e

The #211 admission batch traded 133 corpus fixes for 6 explained regressions (known_below_threshold.txt 195 -> 68). Each of the 6 is root-caused by the per-arm A/B and needs its own lever — none is fixable by gate tuning (all gate shapes were measured, see #211):

  1. config/yaml/yaml_003_logging_config, config/yaml/yaml_012_queue_config, infrastructure/terraform/terraform_070_coalesce_function — the greedy itself admits naming-reachable junk while the gold file's channel is weaker: recall 0 with forbidden hits present, so the zero-context rescue escape never triggers. Lever: relevance ranking (why junk outranks gold at equal reachability), not admission.
  2. infrastructure/kubernetes/kubernetes_001_selector_edge_pulls_workload — no edge channel carries the k8s selector -> workload relation at all (rel=0, so even an ungated rescue cannot pick it). Lever: a dedicated kubernetes selector edge in config_edges/kubernetes.rs.
  3. synthetic/balanced/suite-2/one-hop/bal2_1hop_064_csharp_dto_mapping_bugfix, bal2_1hop_067_csharp_entity_config_change — gold context reachable only via lexical similarity; every declared-relation gate shape blocks it, and their selections carry some context so the zero-context escape does not apply. Lever: a dedicated dotnet channel for the missing relation, or a measured similarity escape.

Close condition: each case either leaves the baseline via its named lever, or its lever is measured and rejected with data.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions