← All lessons

Evals, safety & limits

~7 min read

Final lesson of module one: how the field keeps score, what the guardrails do and don't do, and the failure modes you must design around.

How models are measured

Read any single number with the recipe in mind: what task, what judge, what contamination controls? A 5-point gap means nothing without that context.

Safety: what guardrails are

Refusals, content filters, and safety fine-tuning shape which behaviors surface — they don't remove the underlying capabilities (recall the training lesson: manners, not brain surgery). Jailbreaks — prompts engineered to bypass refusals — work often enough that you should treat any safety property as probabilistic, never as a guarantee your system can rely on.

Never build a control that fails open on model obedience. If harm follows from the model complying, the control belongs outside the model — in code, permissions, and human review.

Limits to design around

Our position (plainly stated)

Bhaskara Labs trains on customer data only with visible opt-out, and our docs say so on the plans page. Sensitive-data customers should assume any vendor-hosted model sees what you send — route accordingly, and ask us (or anyone) for the no-training enterprise tier when it matters.

Check your understanding

Progress saves on this device only

  1. 1.A model leads a benchmark by 3 points. Before updating your priors, you ask…

  2. 2.Why can't refusal training be your only safety control for an agent with shell access?

  3. 3.Which scales worse with context length: finding a fact, or synthesizing an answer from many facts?