6.4.15 · D2 · HinglishAI Safety & Alignment

Visual walkthroughResponsible AI deployment practices

2,510 words11 min read↑ Read in English

6.4.15 · D2 · AI-ML › AI Safety & Alignment › Responsible AI deployment practices

Hum har symbol khud kamayenge. Aakhir mein aap yeh line poori tarah samjhoge:

...aur aapko pata hoga ki har letter apni jagah kyun hai.


Step 1 — "Failure rate" ka matlab kya hota hai

KYA HAI. Hum ek single number se shuru karte hain: . Yeh ek request ka failure probability hai.

KYUN. Isse pehle ki hum poochhen "kitni requests mein failure pakdenge", humein clearly samajhna hoga ki failure kitni baar hoti hai. Woh samajh hai.

PICTURE. Ek lambi strip socho chhote boxes ki, ek box per request. Zyaadatar green hain (success). Kuch rare red hain (failure). Poori strip mein red ka fraction hi hai.

Strip dekho: sirf ek chhoti si sliver red hai. Woh sliver hai. Staged rollout ka poora point yahi hai ki agar hum sirf thode boxes dekhte hain, toh shayad koi red nahi dikhega — aur galti se yeh conclude karein ki model safe hai.


Step 2 — Ek single request ke fail NA hone ki chance

KYA HAI. Agar fail hone ki probability hai, toh nahi fail hone ki probability hai.

KYUN. Hamara goal kam se kam ek failure pakadna hai. Yeh seedha count karna awkward hai (ek, do, teen... failures ho sakti hain). Iska ulta count karna kaafi aasaan hai: zero failures dekhna. Toh pehle humein chahiye ek request ke succeed hone ki probability — yeh "sab succeed ho" ka building block hai.

PICTURE. Step 1 ki strip lo aur use ek single spinner mein compress karo: ek wheel jahan size ka red wedge matlab "fail" aur size ka baaki green matlab "succeed" hai.

Green wedge mota hai (kyunki tiny hai), toh ek spin almost hamesha green pe girta hai. Woh "almost hamesha" hi rare failures ko dangerous banata hai — aur issi liye ek request se aapko lagbhag kuch pata nahi chalta.


Step 3 — Multiply kyun karte hain: saari n requests ke succeed hone ki chance

KYA HAI. Wheel ko baar spin karo ( requests bhejo). Probability ki har ek green pe gire:

MULTIPLY KYUN, ADD KYUN NAHI? Kyunki requests independent hain — request 1 ka outcome request 2 ko nahi badalta. Jab aap independent events ke liye "yeh AUR yeh AUR yeh" chahte ho, probabilities multiply hoti hain. (Add karna "yeh YA yeh" ka jawab deta, jo alag sawaal hai.)

PICTURE. Ek branching tree: har request pe raasta green (success) ya red (failure) mein fork karta hai. Bilkul left edge pe neeche jaata ek all-green path hai jiska probability hai — aur tree gehra hone ke saath yeh tezi se chhota hota jaata hai.

Note karo: ek ek spin almost zaroor green hai, lekin greens ki lambi chain maangna kam aur kam likely hota jaata hai. Woh shrinkage hamara dost hai — iska matlab hai kaafi requests ke baad "all green" rare ho jaata hai, toh all green dekhna safety ka asli evidence ban jaata hai.


Step 4 — Apni wish ko ek inequality mein badalna

KYA HAI. Hum failure miss nahi karna chahte. woh risk hai jo hum tolerate karte hain miss karne ka — woh probability jitna hum accept karte hain ki sab requests green aayein jabki model buggy ho.

Hum insist karte hain ki "all green" probability se zyada badi na ho:

KYUN. Agar "bug hone ke bawajood all green" ki chance hamari tolerance se neeche squeeze ho jaaye, toh all green dekhna model par trust karne ke liye kaafi achha evidence hai. Yeh inequality hamara goal hai, symbols mein.

PICTURE. Ek vertical bar. Upar wala hissa hai (hamari tolerance ceiling). Curve badhne par neeche slide karta hai. Humein itna bada chahiye ki curve ceiling ke neeche chala jaaye.

Yellow ceiling fixed hai. Blue curve zyada requests ke saath girta hai. Hum woh sabse chhota chahte hain jahan blue yellow ke neeche jaaye.


Step 5 — Logarithm kyun? ko exponent se azaad karna

KYA HAI. Humara unknown ke exponent mein qaidi hai. Humein ek aisa tool chahiye jo exponent ko neeche ground level pe le aaye. Woh tool hai logarithm.

YEH TOOL KYUN AUR DOOSRA KYUN NAHI? Hum ko ke liye ordinary algebra se solve nahi kar sakte — dividing ya square-rooting exponent ko free nahi karengi. Logarithm woh ek operation hai jo "kis power?" ka jawab dene ke liye bana hai, toh yeh ek locked exponent ki natural key hai. Dono sides ka lena legal hai kyunki increasing hai (bada input → bada output), toh yeh direction preserve karta hai... abhi ke liye.

Dono sides ka lo:

PICTURE. Curve : yeh bade exponents ko ek straight-line playground pe le aati hai jahan sirf ek plain multiplier hai.


Step 6 — Sign trap: inequality FLIP kyun hoti hai

KYA HAI. Ab hum isolate karne ke liye dono sides ko se divide karte hain. Lekin ka sign dekho.

Kyunki aur ke beech hai, ki value se kam hai. Aur se kam kisi bhi number ka negative hota hai:

Dono sides ko negative quantity se divide karne par flip hokar ban jaata hai:

Har symbol kamaaya gaya:

  • — ek negative number (kyunki ), "main kitna strict hun?"
  • — ek negative number (kyunki ), "ek failure kitni rare hai?"
  • negative ÷ negative = positive, toh sensibly positive nikalta hai.
  • — humein kam se kam itna chahiye; zyada theek hai, kam theek nahi.

KYUN. poora punchline hai: yeh humein minimum sample size batata hai. Flip bhool jaao aur aap kuch compute karoge — yeh conclude karte hue ki aap jitne strict ho utni kam requests chahiye, jo nonsense hai.

PICTURE. Ek number line jismein dono values negative territory mein hain, aur division ko positive side pe safely land karata hai, ek arrow ke saath "tumhe itni ya zyada" mark karta hua.


Step 7 — Real numbers daalna

KYA HAI. failure rate ko confidence ke saath detect karo: , .

Upar round karo (aap fraction mein request nahi chala sakte, aur neeche round karne ki ijazat nahi deta):

KYUN. Yahi number parent note quote karta hai. Iska matlab hai: naye model ko ~3000 real requests pe chalao. Agar koi fail na ho, toh aap confidence ke saath keh sakte ho ki iska failure rate se kam hai. 1000 users/day par yeh 3 din ka 1% traffic hai.

PICTURE. Girta hua curve jisme ek vertical marker par hai jahan woh ceiling cross karta hai.


Step 8 — Edge cases (reader ko koi unseen scenario nahi milna chahiye)

KYA HAI & KYUN & PICTURE, case by case:

Figure ko uske range mein sweep karta hai aur dikhata hai par explode hota hai aur par collapse hota hai — poora behavioural map ek plot mein.


Ek-picture summary

Ek flow, left to right: ek spinner ( green) → spins ke liye multiply () → tolerance ke neeche cap karo () → free karne ke liye lodivide karo (sign flip hota hai!) → final .

Recall Feynman retelling — kisi dost ko batane jaisa bolo

Mere paas ek naya model hai. Yeh rare mein galti karta hai — us rare-mistake chance ko kaho. Toh har try mein yeh cheezein sahi karta hai chance ke saath. Agar main ise baar test karun aur yeh genuinely buggy hai, toh chance ki yeh ittefaqan perfect lagta hai (all green) woh hai apne aap se baar multiply, yani . Main nahi chahta ki mujhe zyada se zyada, maano, time fooled kiya jaaye — woh hai . Toh main demand karta hun . Problem: exponent mein qaidi hai. Logarithm woh ek tool hai jo exponent ko plain multiplier ke roop mein neeche le aata hai, toh main dono sides ka leta hun aur paata hun . Lekin se neeche hai, toh uska log negative hai — aur negative se divide karna sign flip karta hai — giving . Dono logs negative hain, toh unka ratio ek achha positive number hai: minimum requests jo mujhe chahiye. -in- bug ke liye confidence ke saath, woh lagbhag requests hain. Aur edges make sense karte hain: rarer bug → bahut zyada tests chahiye; stricter confidence → bahut zyada tests chahiye; kabhi koi free lunch nahi hota.

Recall

mein exponent kya role play karta hai? ::: Yeh count karta hai ki kitni independent requests ko ek row mein succeed karna hai — kitne green spins hum demand karte hain. Logarithm kyun lete hain? ::: Yeh woh ek tool hai jo unknown ko exponent se neeche kheenchta hai, ko mein badalta hai taaki hum ke liye solve kar sakein. Inequality mein flip kyun hoti hai? ::: Kyunki negative hai (kyunki ), aur inequality ko negative number se divide karne par uski direction reverse ho jaati hai. Jab , required ka kya hota hai, aur iska kya matlab hai? ::: — ek extremely rare failure detect karne ke liye enormous traffic chahiye; yeh long-tail problem hai. ke liye kya hai? ::: Lagbhag requests ( se upar round up).

Yeh bhi dekho: 6.3.2-MLOps-principles (jahan yeh staged rollout pipeline ko gate karta hai), 5.2.4-A-B-testing (do models compare karne ke liye wahi sampling logic), 6.4.1-Adversarial-examples (woh rare failures jinhein pakadne ki koshish yeh math karta hai), aur parent Responsible AI deployment practices.