{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "name": "wave-coordination routing accuracy corpus",
  "version": "1.0.0",
  "purpose": "Routing-eval corpus for wave-coordination (adia-ui-factory plugin). Each phrase declares whether wave-coordination SHOULD be the routing target. Scored by the estate's TF-IDF routing-eval runner against the skill's description (heuristic token overlap).",
  "scoring_notes": "Heuristic signal, not ground truth. Treat misroutes as a prompt to tighten the skill description, never as a reason to keyword-stuff it. Real harness routing is LLM-driven. The fence exercised throughout: wave-coordination owns GEAR-2 TEAM-PATTERN MECHANICS (parallel-branch integration, PR mechanics, shared-file conflict rules, wave sizing) for a multi-screen build already under ui-architect; project-scaffolding owns the project's on-disk SHAPE decision the conflict rules build on; screen-composition owns composing one screen's markup.",
  "license": "internal",
  "scope": "wave-coordination routing \u2014 does this phrase activate wave-coordination?",
  "phrases": [
    {
      "id": "p01",
      "phrase": "how do two parallel screen-composition-agent branches come back together",
      "expected": "trigger"
    },
    {
      "id": "p02",
      "phrase": "who merges the wave's branches, and into what",
      "expected": "trigger"
    },
    {
      "id": "p03",
      "phrase": "how big should a build wave be before we gate it",
      "expected": "trigger"
    },
    {
      "id": "p04",
      "phrase": "two screens in this wave both need to touch the shared app/shared file \u2014 what's the rule",
      "expected": "trigger"
    },
    {
      "id": "p05",
      "phrase": "what does a GEAR-2 wave's PR actually look like",
      "expected": "trigger"
    },
    {
      "id": "p06",
      "phrase": "pick the on-disk shape for this new app \u2014 single surface or shared foundation",
      "expected": "no-trigger",
      "owner": "project-scaffolding"
    },
    {
      "id": "p07",
      "phrase": "compose the markup for this one screen from primitives",
      "expected": "no-trigger",
      "owner": "screen-composition"
    },
    {
      "id": "p08",
      "phrase": "classify this brief into an Orientation Record",
      "expected": "no-trigger",
      "owner": "app-planning"
    }
  ]
}