Skip to content
Sprint projectJun 20, 2026Jamundí, Colombia

JurisGuard-LATAM

Jhon Harvey Tejada Tabares · Team JurisGuard-LATAM

Submitted to Global South AI Safety Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

A reproducible benchmark testing whether jurisdiction checks and matched official-source grounding reduce unsafe specificity in high-stakes Spanish and Portuguese LLM advice across Latin America.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. The project addresses a meaningful and practical AI safety problem, particularly for multilingual and jurisdiction-dependent advice. The evaluation is careful and transparent, but the proposed locality gate is a relatively straightforward intervention and the observed improvements are not entirely surprising. The work would benefit from stronger evidence that this approach generalizes beyond the current benchmark and from a more compelling and clearer discussion of its broader implications for AI safety.

  2. Temperature 0 and variance estimates

    Running at temperature 0 is a reasonable choice for reproducibility, but it means all outputs are deterministic and the bootstrap confidence intervals and McNemar tests have nothing to estimate. A simple fix for a follow-up version would be to run each condition across 3–5 seeds at a low but nonzero temperature (e.g., 0.3), which would make the statistical machinery actually meaningful without sacrificing much reproducibility.

    Human auditor

    The decision to include a human audit at all is a genuine strength that most hackathon papers skip entirely. The issue is that describing the reviewer only as "Spanish-speaking" leaves the validation ungrounded, especially for the legal and medical criteria where the weak kappa scores (0.19 for locality-gate, 0.08 for uncertainty) suggest the rubric may need clearer operationalization. Recruiting even one domain-adjacent reviewer (e.g., a law student, a public health worker) and piloting the rubric with a calibration round would substantially strengthen this component.

    Read full reviewShow less
  3. This is a genuinely well built evaluation for a weekend project. Preregistration, paired bootstrap tests, McNemar tests, and a blind human audit with Cohen's kappa show real methodological maturity, well beyond raw percentages. The core finding, that a locality gate placed before retrieval sharply reduces unsupported jurisdiction specific claims, is a useful and underexplored angle on a real safety problem in multilingual high stakes advice.

    The headline number deserves more scrutiny than it currently gets. Locality gate compliance, the mechanism the whole story rests on, is exactly the criterion where human and judge agreement is weakest, with a kappa close to zero. That should be flagged prominently in the results section itself, not folded quietly into limitations, since it directly affects how much weight the main effect can carry. The two evaluated models also share the same family and host, so this tests robustness within one lineage rather than across genuinely different systems. Related work on jurisdictional defaults in multilingual chatbots is close enough to this idea that a sentence positioning JurisGuard LATAM against it would strengthen the novelty claim.

    Overall, a careful and honest piece of work that already knows where most of its own weak points are. The main thing left to do is give the kappa weakness the same prominence in the writeup that it already gets in the data.

    Read full reviewShow less

Cite this project

@misc{tabares2026jurisguardlatam,
  title = {{JurisGuard-LATAM}},
  author = {Jhon Harvey Tejada Tabares},
  year = {2026},
  month = jun,
  note = {Submitted to Global South AI Safety Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/jurisguardlatam-sadx}},
  url = {https://apartresearch.com/sprints/projects/jurisguardlatam-sadx}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026