AI ke Daur Mein Sochna: Working Day Crash Course

6 Disciplines · 6 AI Failure Modes · Aik Rule

Monday subah do log aik hi AI tool kholte hain. Task same hai: kya budget ek experienced person hire karne par lagana chahiye, ya usi paisay se AI tools khareedne chahiye jo team ke har member ko faster kaam karne mein help karein? Dono ke paas Claude, ChatGPT, aur Gemini ka access hai. Dono ke paas decide karne ke liye aik hafta hai.

Person A Friday ko clear recommendation ke saath finish karti hai jo woh explain kar sakti hai. Us ne likha ke AI ke kaun se claims se woh agree karti hai, kin par push back karti hai, aur kya cheez us ka mind change karegi. Person B Friday ko polished document ke saath finish karti hai jo zyada tar Monday ko AI ki baat repeat karta hai. Jab boss poochta hai "tum ne yeh recommend kyun kiya?" to woh apni reasoning explain nahin kar sakti. Us ne bas woh forward kar diya jo acha lag raha tha.

Same tools. Same problem. Different outcomes.

Farq thinking hai. Person A ne AI se poochne se pehle apni opinion banai. Person B ne AI ka pehla answer apni opinion bana liya.

Yeh crash course isi gap ko close karta hai. Chhe thinking habits, teen short parts, koi code nahin. Har habit AI ke us specific tareeqe ko handle karti hai jis se AI aap ko mislead karti hai jab aap usay apni jagah sochne dete hain. Mil kar yeh AI ko magic answer machine se thinking partner banati hain: pehle aap predict karte hain, phir AI answer deta hai, phir aap compare aur decide karte hain.

Woh force jis ke khilaf yeh course train karta hai

Person B lazy nahin hai. Woh careless bhi nahin. Usay aik aisi force kheench rahi hai jiska ab naam hai.

MIT Sloan ke professor Eric So isay AI gravity kehte hain: woh constant pull jo aap ko apni thinking ka zyada hissa AI ko dene par majboor karta hai. Seedhi baat: har din AI se sochwana thora easy hota ja raha hai, aur apni soch chhorna bhi thora easy.

Isay gravity kyun? Kyun ke yeh real gravity ki tarah kaam karti hai. Aap isay dekh nahin sakte. Yeh kabhi off nahin hoti. Aur yeh sab ko, har waqt, teen directions se aik saath kheenchti hai:

Aap ka dimagh energy bachana chahta hai. Dimagh hard work se bachne ke liye bana hai. Yeh normal hai. Magar AI jitni smarter hoti hai, usay aik aur task dena utna easy lagta hai, aur apna answer pehle likhna extra kaam lagta hai.
Aap chahte hain kaam expert-level lage. AI seconds mein aisi cheez likh deti hai jo expert ki lagti hai. Us ke baghair kaam karna aik jootay ke saath race karne jaisa lagne lagta hai.
Aap dekh nahin sakte ke doosre AI kitna use kar rahe hain. Classmates aur coworkers announce nahin karte. To har koi assume karta hai ke baqi log zyada AI use kar rahe hain, aur race khud tez ho jaati hai.

Ab Monday morning wali Person B ko phir dekhein. Teenon forces ne usay aik hi easy move ki taraf dhakela: AI kholo, poochho, accept karo. Usay mehsoos hi nahin hua ke woh decision le rahi hai. Gravity well andar se aisa hi lagta hai.

Teen forces, aik pull. Person A ko bhi wohi gravity lagti hai. Farq counterweight ka hai.

Is pull ki cost. MIT Media Lab ke researchers ne is par early study ki. Logon ne ChatGPT ki madad se essays likhe. Submit karne ke turant baad 100 mein se 83 apne essay ki aik bhi sentence repeat nahin kar sake. Alfaaz screen se homework tak gaye, writer ke dimagh se guzray hi nahin. Study preliminary hai, magar warning clear hai.

Professor So is loss ko cognitive capital kehte hain. Isay apni thinking muscle samjhein: problem par kaam karne, wrong answer pakarne, aur confident answer ne kya chhoda hai yeh notice karne ki ability. Is page ki har discipline isi muscle par chalti hai.

Pull ki cost. Left par card "AI's answer on the screen." Right par card "the submitted essay." Beech mein writer khara hai. Aik mota arrow "copy, polish, forward" writer ke sar ke upar se jump karta hai. Writer ki taraf dotted path cross out hai aur label "never enters." Badge: MIT Media Lab finding, 83% could not quote a single sentence. Alfaaz screen se submission tak gaye, writer ke dimagh se nahin.

Teachers bhi desk ke doosri taraf se wohi pull feel kar rahe hain. June 2026 mein Madrid ke IE School of Science & Technology ki dean ne kaha ke school mein AI ka asal danger yeh nahin ke woh worse summary likhti hai; danger yeh hai ke students woh mental muscle banana chhor dete hain jo summaries likhne se banta tha. Advice simple thi: hard thinking karte raho, aur AI us ke upar add karo. (BusinessWorld, June 2026)

Professor So push back ke chaar tareeqe bhi dete hain. Aap inhein pehchan lein ge, kyun ke yeh page yehi sikhata hai:

Push back ka tareeqa	Yahan kahan practice hota hai
Hard thinking khud karte rahen	Exercises aur neeche caution box
Janein ke AI ke baghair aap kya kar sakte hain	Prediction Lock aur Discipline 6 ka Solo path
AI se bacha waqt harder thinking par lagayen	Part 3, Origination
AI ko coach banayen, answer machine nahin	Har AICheck exercise

Yeh section yeh nahin keh raha ke AI kam use karein. Six disciplines diet nahin hain. Yeh counterweight hain. Gravity sirf un cheezon par jeetti hai jo apna weight rakhna chhor deti hain. Baqi page yeh batata hai ke aap heavy kaise rehte hain.

Prerequisites. Yeh page assume karta hai ke aap pehle wali Foundations courses complete kar chuke hain, khaas taur par mental model ke liye What AI Actually Is aur 2026 mein AI Prompting. Us course ne mechanics sikhaye thay: AI ko context kaise dena, web search aur deep research kaise use karna, images aur audio ke saath kaise kaam karna, aur AI desktop apps kaise use karni. Yeh course woh thinking discipline sikhata hai jo un mechanics ko payoff deta hai. Abhi dusre tab mein Claude, ChatGPT, ya Gemini ka free account khol lein. Practice sections mein aap usay use karein ge.

AI models par note. Practice exercises mein AI-graded feedback hai. Yeh strong, current AI model ke saath best kaam karte hain (Claude, ChatGPT, ya Gemini apne best reasoning level par). Older ya weaker models aksar vague ya overly positive feedback dete hain, chahe aap kya submit karein. Jis best model ka access hai use karein. Brand matter nahin karta; matter yeh karta hai ke model carefully reason kar sake.

📚 Teaching Aid

Poori Slideshow Kholein

Poori Presentation Dekhein, AI ke saath Thinking

Rule aik line mein

Deliverable kabhi answer nahin hota. Deliverable thinking ka documented evidence hota hai.

Isay do claims ke taur par parhein. Pehla, deliverable, yani jo cheez aap boss, professor, ya client ko dete hain, ab sirf answer nahin hai. AI seconds mein polished answer bana sakti hai; answer banana ab hard part nahin. Doosra, deliverable ko trustworthy banane wali cheez ab written record of how you thought hai: woh prediction jo aap ne AI se pehle lock ki, woh row jahan aap ne AI ke claim ko REJECT mark kiya aur kyun bataya, aur woh cascade map jo side effects trace karta hai. Agar koi poochay "aap ne yeh decide kyun kiya?", aap evidence dikhate hain.

Practice mein evidence aksar deliverable ke andar hota hai: footnote, "considered and rejected" paragraph, figure ke taur par cascade map, ya end ke paas "what would change my mind" sentence. Kabhi yeh deliverable ke saath working doc mein hota hai. Dono cases mein jab koi kyun poochay, aap point kar sakte hain. Agar point karne ko kuch nahin, to aap ke paas answer hai jise defend nahin kar sakte; 2026 mein yeh deliverable nahin.

Kya chat link khud evidence hai?

Kabhi kabhi. Chat session AI ki har baat aur aap ka har sawal capture karta hai, jo kisi reasoning receipt se zyada complete ho sakta hai. Low-stakes work, jaise debugging, quick research, ya exploratory brainstorm, mein chat link akela kaafi hota hai. Serious deliverables ke liye chat link ki teen limits hain: yeh dikhata hai AI ne kya kaha, yeh nahin ke aap ne har claim par kya decide kiya; busy reader ke liye bohat lamba hota hai; aur yeh nahin dikhata ke AI ne kya ghalat kiya. Chat link ko raw material samjhein. Reasoning receipt ya memo woh deliverable hai jo audience ko dete hain; chat link appendix ya footnote mein jata hai.

Practice mein yeh kaisa lagta hai. Opening ki Person A aur Person B yaad karein: same problem, same AI, different outcomes. Friday morning un ka boss dono se poochta hai: "tum ne yeh recommend kyun kiya?" Person B ke paas point karne ko kuch nahin. Woh AI-helped document forward karti hai aur kehti hai yeh right laga. Boss do claims par disagree karta hai, aur ab pata lagane ka tareeqa nahin ke Person B ne un claims ko examine kiya ya bas accept. Person A apna working doc kholti hai aur kehti hai: "Monday ko meri prediction thi ke experienced hire better choice hogi. AI analysis ne woh prediction flip ki, aur yeh reason hai ke main ne mind change kiya: teen claims jo main ne check kiye, aik jo reject kiya, aur woh assumption jo recommendation wapas badal degi." Same problem. Do bilkul different conversations.

Is deliverable mein evidence aap ko abhi kya deta hai? Do cheezen. One: writing thinking ko force karti hai. Specific prediction likhne se pehle aap ko decide karna padta hai ke aap waqai kya believe karte hain, aur claim ko REJECT mark karne se pehle explain karna padta hai kyun. Writing ke baghair thinking skip karna bohat asan hai. Two: written record working tool hai, sirf audit trail nahin. Bank manager ne likha "meri recommendation yeh hai ke branches band kar dein, kyun ke mujhe lagta hai zyada tar customers app-only hain" aur AI aisa data le kar aaya jo dikhata tha ke sirf 45% app-only hain; us ne sirf aik disagreement document nahin kiya, balke us ki position aur data ke darmiyan gap us ki report ki opening line aur recommendation ki spine ban gaya. Record woh surface hai jahan second pass of thinking hota hai, aur second pass mein deliverable improve hota hai.

Badla writing-down habit nahin. Badli usay skip karne ki cost hai. Jab polished output expensive tha, hard part cheez banana tha. AI ne polished output free kar diya. Bottleneck producing work se evaluating work par shift ho gaya, aur written evidence evaluation ka tareeqa hai. Tools har chhe months badalte hain; yeh nahin.

Essentials: paanch bullets

Ab aap rule seekh chuke hain. Yeh page baqi mein chhe habits mein se paanch sikhaye ga: pehle short version, phir full sections. Bullets batate hain kya karna hai; sections batate hain kaise. Chhatti habit, common advice kahan break hoti hai test karna, bullet se zyada setup mangti hai aur apna section leti hai.

AI se poochne se pehle sochain. Koi AI tool kholne se pehle likhein ke AAP ko kya lagta hai answer hai. Kyun? Kyun ke AI ka answer parhte hi woh aap ki thinking le leta hai. Agar AI ki baat reasonable lage, aap use apni soch bana lete hain. Pehle apna answer likhna independent judgment protect karta hai.
Jo accept aur reject kiya us ka written record rakhein. Jab AI claims ya recommendations de, har aik par likhein: kya main agree karta hun? disagree? kya AI ne kuch important miss kiya? Har claim ke liye aik sentence kyun ka. Agar aap AI ki har baat se agree karte hain aur push back nahin karte, shayad aap ne enough nahin socha.
Polished writing correct writing nahin hoti. AI confident aur professional lagti hai, ghalat hoti tab bhi. Smooth AI output mein chhe specific error types chhupi hoti hain. AI ki likhi hui koi cheez send, publish, ya act karne se pehle har type ko naam se check karein.
Obvious answer complete answer kabhi nahin hota. AI decision analyze karte waqt us cheez par focus karti hai jo aap ne poochi, side effects ignore karti hai. Important decision se pehle affected logon aur groups ke across trace karein ke next kya hota hai. Dhoondhein kahan side effects wapas aa kar original decision ko undo karte hain.
Best results AI ke WITH kaam karne se aate hain, wheel usay dene se nahin. Alone kaam slow hai. AI ko sab kuch dena generic output deta hai. Winning approach: aap thinking aur deciding karte hain, AI research aur drafting karti hai. Agar aap flip kar dein (AI thinks, aap bas edit), aap unnecessary ho jate hain. Jo log bas AI ke answers aage pohanchate hain, woh aakhir-kaar khud AI se replace ho jayein ge.

Poora framework: chhe disciplines

Upar ke paanch bullets working summary hain. Yahan poora architecture hai: chhe disciplines, har ek apne us AI failure mode ke saath one-to-one paired jise woh answer karti hai, teen parts mein grouped.

Figure 1: Chhe disciplines chhe AI failure modes par map hoti hain, teen parts mein arrange ki gayi.

Teen parts order mein chalte hain. Part 1, Foundations, AI se poochhne se pehle sochne ke baare mein hai: pehle apna position lena, phir track karna ke har answer ke baare mein aap kya decide karte hain. Part 2, Detection, woh pakarne ke baare mein hai jo AI ghalat karti hai: confident prose mein chhupi ghaltiyan, aur woh side effects jo woh kabhi trace nahin karti. Part 3, Origination, woh thinking hai jo AI aap ke liye nahin kar sakti: dhoondhna ke common advice kahan toot-ti hai, aur jab AI control lena chahe to apna judgment in-charge rakhna. Har part apne se pehle wale par depend karta hai.

Is page par chaar terms baar baar aate hain. Discipline woh thinking habit hai jo aap practice karte hain, yani jo aap karte hain. Failure mode woh specific tareeqa hai jis se AI aap ko gumrah karti hai, yani jo AI karti hai. Har discipline us failure mode ke saath one-to-one paired hai jise woh answer karti hai (figure mein har discipline name ke neeche italic line ke taur par dikhaya gaya). Course ka part un disciplines ko group karta hai jo aik job share karti hain; teen parts hain (Foundations, Detection, Origination), har ek mein do disciplines, aur har part agle ko enable karta hai. Deliverable woh hai jo aap boss, professor, ya client ko dete hain: 2026 mein, woh answer plus thinking ka woh documented evidence jis ne usay produce kiya (figure ke neeche wala banner).

Figure mein har numbered box aik discipline hai. Neeche wali small caps line action line hai: woh aik specific action jo woh discipline aap se karne ko kehti hai, sticky note par fit hone ke liye likhi gayi. Discipline name aap ko batata hai ke habit ka naam kya hai; action line batati hai ke asal mein kya karna hai.

Start here. Part 1 ki do disciplines AI ko aap ke liye sochne se rokti hain. Inhein skip karen ge to baqi chaar apna kaam nahin kar sakti.

Is page ko kaise parhna hai

Aap ke paas waqt	Kya parhein	Kya skip karein
45 minutes	Habits 1, 2, 3, aur 6 (sirf read, exercises nahin)	Habits 4 aur 5 (baad mein wapas aayein)
90 minutes	Sab chhe habits + worked examples, read-only	AICheck submissions
A working day (recommended)	Sab kuch, har exercise apne week ke real decision par run karein	Kuch nahin

Yeh habits tab stick hoti hain jab aap unhein apne week ke real problems par try karte hain. Page ko 90 minutes mein parhna moves dikhata hai. Real decisions par exercises karna unhein aap ka banata hai.

Yeh page maan kar chalta hai ke aap pehle se soch sakte hain. Yeh aap ko sochna nahin sikhata.

Yahan har habit ko kaam karne ke liye kisi cheez ki zaroorat hai. Prediction Lock aap se pehle apna answer likhwati hai, magar aap yeh sirf tab kar sakte hain jab aap pehle se itna jaante hon ke aap ke paas aik answer ho. Error Taxonomy aap se aik fake number pakarwati hai, magar aap usay sirf tab pakar sakte hain jab aap jaante hon ke aik real number kaisa dikhta hai. Yeh habits aap ke judgment ko use karti hain. Woh usay banati nahin.

To agar aap abhi bhi student hain, hard work skip na karein. Summary khud likhein. Problem set bina AI ke solve karein. Haan, AI yeh tezi se kar sakti hai. Lekin khud karna hi woh tareeqa hai jis se aap ka dimagh itna mazboot hota hai ke baad mein AI ghalat ho to usay pakar sakein. Agar aap kabhi hard work karte hi nahin, to aap ki Prediction Lock bas aik guess hai, AI aik answer deti hai, aur aap ke paas us se compare karne ko apni koi cheez nahin hoti. Habit kaam karti lagti hai, magar woh khaali hoti hai.

Saadah rule: AI ko aisi skill stretch karne ke liye use karein jo aap pehle se rakhte hain, usay seekhna skip karne ke liye nahin. Bees saal ke tajurbe wala accountant AI par kaafi bharosa kar sakta hai, kyun ke usay pehle se pata hai ke aik achha answer kaisa dikhta hai. Aik first-year student jis ne kabhi haath se kaam nahin kiya, woh nahin kar sakta, abhi nahin.

Part 1: Foundations (posture, yani woh stance jo aap start se pehle lete hain)

Agar baqi sab skip karein, yeh do habits skip na karein. Yeh AI ke saath logon ki do sab se bari mistakes fix karti hain:

Mistake 1: AI aap ke liye sochti hai. Aap sawal poochte hain, AI smooth answer deti hai, aur aap apni opinion banane se pehle use accept kar lete hain. Habit 1 (Prediction Lock) isay fix karti hai: aap AI kholne se PEHLE likhte hain ke aap kya sochte hain.
Mistake 2: AI ka first draft finished lagta hai. Writing itni polished hoti hai ke aap check kiye baghair send kar dete hain ke kya woh actually correct hai. Habit 2 (Reasoning Receipt) isay fix karti hai: aap har claim ko dekhte hain aur likhte hain ke agree, disagree, ya verify karna hai.

Mil kar yeh do habits thinking aap ke paas aur typing AI ke paas rakhti hain. Parts 2 aur 3 mein har cheez in par build karti hai.

Discipline 1: Prediction Lock

Goal sirf aik cheez hai: AI ka answer aane se pehle aap ke paas apni aik likhi hui position ho. Neeche sab kuch, chaar lines, sticky note, confidence percentage, isi liye hai ke woh aik cheez waqai ho jaye. Agar aap chaaron lines likh dein aur phir bhi na bata sakein ke AI kholne se pehle aap ki position kya thi, to discipline ne kaam nahin kiya. Agar aap ki position clear hai aur aap chaar ke bajaye do lines mein wahan pohanch gaye, to discipline ne phir bhi kaam kiya. Chaar lines aik recipe hain, dish nahin.

Lock ke baghair aam tor par yeh hota hai. Aap AI se aik important sawal poochte hain. AI aap ko aik confident, achhi likhi hui answer deta hai. Aap sochte hain ke "yeh theek lagta hai" aur usi par chal padte hain. Do din baad koi poochta hai "aap ne yeh decide kyun kiya?" aur aap ko ehsaas hota hai: woh AI ka answer tha, aap ka nahin. Aap ne kabhi apni opinion banai hi nahin.

Fix teen minutes leta hai. AI kholne se pehle kaaghaz par chaar lines likhein. Pehle kisi aur ke decision par mil kar try karte hain.

Maya 13 saal ki hai. Us ke school ne email ki: aik summer activity choose karo. Option 1: debate camp (do haftay, us ke saare dost ja rahe hain). Option 2: coding bootcamp (aik hafta, woh curious hai magar nervous bhi hai). Us ke dad kehte hain "bas ChatGPT se pooch lo, usay pata ho ga."

AI se poochne se pehle, Maya chaar lines likhti hai:

Figure: Prediction Lock ki chaar lines, Maya ke jawabon ke saath aik worked example ke taur par.

Line 1: Yeh decision asal mein kis bare mein hai?

"Debate ya coding" nahin. Woh sirf surface hai. Neeche asal sawal yeh ho sakta hai: "Main woh karun gi jo mere dost karte hain, ya woh jo main tab choose karti jab koi dekh nahin raha hota?" Ya: "Coding miss karne ka regret debate miss karne se zyada ho ga?" Asal sawal aik sentence mein likhein.

Line 2: Woh AIK fact kya hai jo sab se zyada help karega?

"Kaunsa behtar hai?" nahin. Yeh bohat vague hai. Kuch specific jo aap check kar sakein: "Kya coding bootcamp Python padhata hai?" Yeh is liye matter karta hai ke us ka school pehle se 9th grade mein Python padhata hai. Agar bootcamp wohi cheez padhaye, to coding ka woh time zyada tar wohi repeat karega jo usay waise bhi seekhna hai. Agar woh aisi cheez padhaye jo us ka school cover nahin karta, to bootcamp aisi skill de raha hai jo usay kahin aur nahin milti.

Line 3: Aap ka decision kya hai, AI ke bolne se pehle?

Aik position lein. "It depends" nahin. "Dekhte hain AI kya kehta hai" nahin. Debate chunein ya coding, aur likhein kyun. Maya ki reasoning: woh jaanti hai ke us ka school 9th grade mein Python cover karta hai, bootcamp bhi zyada tar Python hi padhayega, aur doston ke saath do haftay aisi cheez seekhna jo usay kisi school course se nahin milti, agle saal ke curriculum ke repeat se zyada qeemti hai. To us ka decision debate hai.

Yeh woh hissa hai jise har koi skip karna chahta hai. "Main AI se pehle decide kaise karun?" Aap kar sakte hain. Aap pehle se bohat kuch jaante hain: aap ka school kya padhata hai, kya miss karne ka aap ko regret ho ga, aap ke dost kya kar rahe hain. Jo aap jaante hain us se position banayein. Aik minute mein AI ka kaam us position ko confirm ya overturn karna hai, usay banana nahin.

Line 4: Aap kitne sure hain, aur AI ka kaunsa specific answer aap ka decision flip karega?

Aik percentage chunein: 60%, 75%, kuch bhi. Exact number matter nahin karta. Matter yeh karta hai ke aap ne commit kiya. Phir woh aik AI answer likhein jo aap ka mind change karega. Maya: "70% sure ke debate sahi call hai. Agar bootcamp aisi cheez padhaye jo mera school nahin padhata (Rust, embedded programming, game development), to coding jeet jata hai kyun ke woh aisi skill hai jo mujhe kahin aur nahin milti."

Agar aap woh specific AI answer name nahin kar sakte jo aap ka decision flip karega, to aap ne abhi tak kisi real position par commit nahin kiya. "It depends" position nahin hai. "Main X karun ga jab tak AI mujhe Y na bataye" position hai.

Aap ko kaise pata chalega ke lock ne kaam kiya?

Aik test hai, aur woh lines count karne ke bare mein nahin:

Kya aap loud keh sakte hain ke AI kholne se pehle aap ki position kya thi, aur kaunsi cheez aap ka mind change karti?

Agar haan, lock ne kaam kiya. Line count matter nahin karta.

Agar nahin, yani aap khud ko yeh kehte paate hain ke "AI ne X kaha to main X ke saath chala gaya" ya "maine socha aur jo AI suggest karega wohi decide kiya," to lock ne kaam nahin kiya. Line count phir bhi matter nahin karta.

Chaar lines training wheels hain. Yeh goal skip karna mushkil banati hain. Kuch hafton ki practice ke baad aap chaaron ko aik paragraph ya kuch mental notes mein compress kar sakte hain, aur lock phir bhi kaam karega. Lekin pehli 10 dafa yeh chaar lines explicit likhein. Yahi jaanne ka tareeqa hai ke aap ne waqai position commit ki, sirf yeh nahin socha ke commit ki hai.

Chaar lines asal mein kya kar rahi hain

Maya ke liye chaar lines is liye kaam karti hain ke us ka decision simple hai: aik binary choice, aik fact jo usay settle kar de. Har decision aisa nahin hota. Is liye template copy karne se pehle dekhein ke har line andar se kya kar rahi hai. Maya ki lines aik process ki example hain; decisions badalte hain, process nahin.

Prediction Lock ke chaar parts hain, aur har decision mein yehi chaar parts rehte hain:

Real decision surface karein. Label hata dein. Maya ka surface decision "debate ya coding" tha. Real decision tha "doston ko follow karna ya apni choice karna." Bank manager ka surface decision "do branches close karna" tha. Real decision tha "aise customer base ke saath kya karna jo app par shift ho chuka hai." Label actual question chhupata hai. Actual question name karein.
Woh cheez identify karein jo isay settle karegi. Kaunsi information mil jaye to decision obvious ho jaye ga? Maya ke liye aik fact tha: kya bootcamp Python padhata hai? Hiring decision mein shayad 3 facts hon: kya har candidate mein woh specific skill hai jo sab se zyada chahiye? Budget allocation mein comparison ho sakta hai: marginal dollar par kis category ka return sab se kam hai? Facts itne specific likhein ke verify ho saken.
Position commit karein. Jo aap pehle se jaante hain, AI se check karne se pehle, us base par aap kya karein ge? Isay reasoning ke saath likhein. Maya ke liye: debate, kyun ke school already Python padhata hai. Hiring mein: specific candidate ka naam aur wajah. Budget cut mein: line items aur wajah. Position sirf what nahin; what plus why hai.
Reversal condition name karein. Kaunsi specific finding position badal degi? Maya: agar bootcamp school se bahar kuch padhata hai, coding wins. Hiring mein: agar second candidate ka reference top candidate se significantly stronger ho to switch karein. Budget cut mein: agar Category X ka projected revenue 30% se zyada off ho, to doosri category cut karein. Agar aap flip condition name nahin kar sakte, aap ke paas commitment nahin; sirf preference hai.

Maya ki sticky note chaar lines mein fit ho jaati hai kyun ke decision chota hai. Bara decision, jaise hiring round, strategic pivot, ya major purchase, har part ke liye aik paragraph le sakta hai. Chota decision, jaise lunch order jab aap waqai care karte hon, aik index card par fit ho sakta hai.

Different shape wala worked example: sochiye aap 3 software engineers mein se aik hire kar rahe hain aur decide karne ke liye aik week hai.

Real decision: "paper par kaun best hai" nahin, balke "in teeno mein se kaun 12 months baad bhi productive ho ga jab codebase do dafa badal chuka ho ga."
What would settle it: Aik nahin, 3 things. Har candidate ka long projects par track record, unfamiliar tools seekhne ki willingness, aur previous manager ka reference jis ne tough quarter mein usay dekha.
Your position: Candidate B, kyun ke previous job par 2-year stint durability suggest karta hai, aur side project dikhata hai ke woh bina kahe new tools pick kar leti hai.
What flips you: Agar Candidate A ka reference kahe ke us ne past year ka hardest project ship kiya, A par switch karein. Agar Candidate C ka reference communication issues flag kare, B stays.

Yeh Maya wala hi Prediction Lock hai. Decision different, har part mein written amount different, chaar parts same.

Chaar lines kyun? Sirf aik kyun nahin?

Yeh sawal taqreeban har reader poochta hai, aam tor par Line 3 par: "kya main sirf decision nahin likh sakta?" Jawab no hai, aur samajhna useful hai ke kyun.

Har line aik failure mode pakarti hai jo baqi nahin pakar saktin. Inhein aik line mein compress karein ge to specific cheezen kho dein ge:

Line 1 skip karein ge to wrong question ka answer dein ge. Maya ka surface decision "debate ya coding" hai. Real decision "doston ko follow karna ya apni choice karna" hai. Dono ke answers different ho sakte hain. Line 1 isay surface karti hai.
Line 2 skip karein ge to AI prompt lock ko collapse kar dega. Specific question ke baghair reader default tor par "which should I pick?" poochta hai. Yeh AI ko decision de deta hai. Line 2 closed, verifiable question force karti hai: "kya bootcamp Python padhata hai?" checkable hai. "Kaunsa camp behtar hai?" nahin.
Line 3 skip karein ge to AI answer ke muqable ke liye kuch nahin ho ga. Yehi lock hai. Lines 1 aur 2 setup hain; Line 4 isay specific banati hai. Line 3 woh position deti hai jise aap AI ke confident answer ke samne defend karte hain.
Line 4 skip karein ge to commitment nahin, hope ho gi. "Main debate pick karta hun" decision lagta hai. Lekin jab tak aap specific AI answer name nahin karte jo isay flip karega, aap nahin jaan sakte ke waqai commit kiya ya AI ki first suggestion par abandon kar dein ge. Line 4 commitment ko specific banati hai. Yehi line months later calibration bhi dikhati hai: "maine 70% kaha tha aur opposite nikla." Judgment isi tarah improve hoti hai.

One-line version try karein: "Mere khayal mein Maya ko debate pick karna chahiye" casual preference hai, Prediction Lock nahin. Yeh nahin batata real stake kya hai, AI se kaunsa question poochna hai, ya mind change kya karega. Aisi single line likhne wala reader AI ka two-paragraph answer parhe ga aur usay adopt kar le ga, kyun ke resist karne ke liye line mein kuch hai hi nahin.

Chaar lines surface par similar lagti hain, magar different cheezen pakarti hain. Discipline chaar is liye maangti hai ke experience batata hai: jo bhi aik line skip karta hai, usi line ka failure mode aata hai.

Pedagogical wajah bhi hai. Chaar lines itni short hain ke reader waqai kare, teen minutes, sticky note par fit. Magar itni long hain ke writing ka act thinking force kare. Aik line bohat short hai; aap usay soche baghair likh sakte hain. 10 lines bohat long hain; aap exercise skip kar dein ge. Chaar woh floor hai jahan thinking ko happen karna padta hai, aur woh ceiling hai jahan busy reader Tuesday morning meeting se pehle bhi karega.

Is liye: appearance chahiye to aik line. Actual Prediction Lock chahiye to chaar lines.

Maya ki sticky ab yeh kehti hai:

Kya ho raha hai: Woh apne doston wali cheez karegi ya woh jo akeli hoti to choose karti.

Jo sawal madad karega: Kya bootcamp Python use karega (jo us ka school pehle se 9th grade mein padhata hai)?

Decision: Debate. Doston ke saath do haftay, aisi cheez seekhna jo school offer nahin karta, agle saal ke curriculum ke aik-haftay repeat se behtar hai.

Confidence + kya flip karega: 70%. Agar bootcamp Rust, embedded systems, ya koi aisi cheez padhaye jo us ka school cover nahin karta, to coding jeet jata hai.

Ab woh apna sawal ChatGPT mein type karti hai. Yeh woh actual prompt hai jo woh paste karti hai:

My school's summer program runs a one-week coding bootcamp. I'm trying
to figure out one thing: will it teach Python? My school already teaches
Python in 9th grade, so I want to know if there's overlap. Just answer
the question. Don't recommend which camp I should pick.

Lock ne sawal badal diya. Sticky note par chaar lines ke baghair, Maya AI se poochti "main debate pick karun ya coding?", aik open sawal jo decision AI ke hawale kar deta. Lock ke saath us ke paas pehle se decision hai; usay sirf aik fact chahiye jo usay confirm ya overturn kare. To woh us ke bajaye aik closed sawal poochti hai. AI ka role decision-maker se fact-checker mein shift ho jata hai. Yehi shift discipline produce karti hai. Chaar lines ne sirf Maya ki thinking clear nahin ki, unhon ne dobara taqseem kiya ke is conversation mein kaun kya karega.

ChatGPT yeh le kar aata hai: "Most one-week coding bootcamps for middle schoolers cover Python basics in the first two to three days." Maya isay apni sticky note ke saath rakhti hai. AI ka answer (Python) us answer se match karta hai jis ke liye woh tayyar thi. Us ka decision (debate) hold karta hai, us wajah se jo us ne likhi, is liye nahin ke AI ne usay kaha.

Dinner par us ke dad poochte hain kyun, aur Maya ke paas aik real answer hai: "Bootcamp Python cover karta hai aur mera school agle saal wohi padha raha hai. Main do haftay apne doston ke saath debate seekhne mein lagana chahti hun, jo school bilkul offer hi nahin karta." Yeh us ki reasoning hai. AI ne us ke andar aik fact confirm kiya.

Isay lock ke baghair wali version se compare karein. Maya ChatGPT kholti hai, poochti hai "main debate camp pick karun ya aik-haftay coding bootcamp?" ChatGPT aik balanced do-paragraph answer likhta hai jo is par khatam hota hai "dono qeemti hain; dekhein kis cheez se aap ko sab se zyada energy milti hai." Maya parhti hai, debate pick karti hai kyun ke wahan us ke dost ja rahe hain, aur dinner par kehti hai "ChatGPT ne kaha dono achhe hain, to main ne debate choose kar liya." Decision wohi hai. Reasoning gayab hai. Do din baad woh explain nahin kar sakti ke jo choose kiya, kyun choose kiya.

Yeh chaar lines Prediction Lock hain. Teen minutes ki writing, AI ka confident answer aap ke dimagh mein woh jagah lene se pehle jahan aap ka apna answer aata.

Aik dafa aap ne AI ka answer parh liya, to aap usay un-read nahin kar sakte. Aap yeh bhi nahin bata sakte ke us ke baghair aap kya sochte. Bas do din baad aap notice karte hain ke aap theek se explain nahin kar pa rahe ke jo decide kiya, kyun kiya. Aap ne AI ka answer absorb kar liya. Apna answer earn nahin kiya.

Do flows compare kiye gaye hain. Lock ke baghair: problem se AI ka answer se "Makes sense" agreement se inherited position. Lock ke saath: problem se sealed prediction se AI ka answer se compare se decide. Answer se pehle seal kiya gaya, warna woh prediction nahin.

Yehi discipline bare decisions par bhi kaam karti hai. Aik bank manager ko decide karna tha ke do branches band kare ya nahin jo paisa lose kar rahi thin. AI se poochne se pehle us ne apni chaar lines likhin:

Line 1 (yeh asal mein kis bare mein hai): Branches paisa is liye lose kar rahi hain kyun ke zyada tar customers ab in-person aane ke bajaye app use karte hain. Asal sawal yeh hai ke kya itne customers ab bhi andar aate hain ke branches khuli rakhna justify ho.

Line 2 (woh aik fact jo isay settle kare): In branches ke customers mein se kitne percent app-only hain (kabhi branch nahin aate)?

Line 3 (AI ke bolne se pehle mera decision): Branches band kar do. Customer-service team ke saath kaam karne ka mera tajurba batata hai ke in mein se zyada tar customers ne saalon pehle aana chhor diya. Do saal pehle main yeh predict na karti, lekin app launch hone ke baad se pattern clear hai.

Line 4 (confidence + kya flip karega): 60% sure. Agar aadhe se kam customers app-only hain, to iska matlab aik real walk-in base ab bhi mojood hai, aur branches band karna un customers ko poori tarah kho dega. Us soorat mein branches khuli rakho.

Phir us ne apne bank ka customer data nikala aur Claude se poocha:

I have transaction data for two branches we're considering closing.
For each customer who used these branches in the last 12 months,
I need to know what percentage NEVER walked into a branch and
only used the mobile app. Just give me the percentage. Don't
recommend whether to close the branches.

Claude 45% le kar aaya. Yeh us ke 50% threshold se kam hai, jiska matlab us ki Line 4 flip ho gayi: branches band karna ab sahi call nahin tha.

Lekin zyada dilchasp cheez woh gap thi jo us ke andaze (zyada tar customers app-only) aur data (sirf 45%) ke darmiyan thi. Us gap ne usay bataya ke us ne overestimate kiya tha ke customer base kitni door shift ho chuka hai. Us ne dono findings apni report mein use kiye: data ne us ki recommendation "band karo" se "khuli rakho" par flip ki, aur gap us ki opening line ban gaya, "mujhe lagta tha in mein se zyada tar customers app-only hon ge; data dikhata hai sirf 45% hain, jo recommendation badal deta hai." Us ne aakhir mein aik middle path tajweez kiya: branches khuli rakho magar staff ke kam ghante ke saath, kyun ke 55% customers ab bhi andar aa rahe the lekin full-day levels par nahin.

Prediction Lock ke baghair woh bas jo AI kehta usay accept kar leti aur kabhi notice na karti ke us ki apni assumption off thi, aur middle path (kam ghante) surface hi na hota, kyun ke us ke paas notice karne ke liye koi gap na hota.

Maya ki chaar lines aur bank manager ki chaar lines surface par different lagti hain. Woh aik hi Prediction Lock hain, aik hi chaar parts, mukhtalif sizes ke decisions par lagaye gaye.

Khud try karein

Aap pehle hi Maya ke liye chaar lines likh chuke hain. Aap wohi lines neeche boxes mein paste kar sakte hain. Ya, agar aap ke paas apna koi decision hai, to chaar lines us par try karein. Maslan: koi cheez jo aap khareedna chahte hain, do plans jin mein se aap chunaav kar rahe hain, koi conversation jise aap baar baar avoid karte hain, ya koi class jis ke bare mein aap sure nahin.

Pehle apni chaar lines likhein. Phir is prompt se AI se apni Line 2 wala sawal poochein:

I'm trying to decide [describe your situation in 1-2 sentences].

My question is: [paste your Line 2 question here].

Just answer that one question. Don't make the decision for me.

Yahan usi prompt ka Maya wala version hai, us ki sticky note se bhara hua:

I'm trying to decide between two summer camps. One is a one-week
coding bootcamp; the other is a two-week debate camp where all my
friends are going.

My question is: does the bootcamp teach Python? My school already
teaches Python in 9th grade, so I want to know if there's overlap.

Just answer that one question. Don't make the decision for me.

ChatGPT ka response:

Most one-week coding bootcamps for middle schoolers cover Python
basics in the first two to three days, then move on to a small
project using those basics. Some bootcamps add light JavaScript or
web concepts later in the week, but Python is almost always the
core language.

Maya isay apni Line 4 ke saath rakhti hai. Us ki Line 4 kehti thi ke coding sirf tab jeetegi jab bootcamp aisi cheez padhaye jo us ka school cover nahin karta. AI ne confirm kiya ke Python hi core hai, bilkul wohi jo us ka school pehle se 9th grade mein padhata hai. Yeh us ki flipping condition nahin. Us ka decision waisa hi rehta hai: debate.

Prompt mein sirf Lines 1 aur 2 jaati hain. Line 3 (aap ka decision) aur Line 4 (jo aap ka mind change kare) us page se bahar rakhein jo AI dekhta hai. Agar AI ko pata ho ke aap ne kis par commit kiya hai, to woh aksar aap se agree kar leta hai, aur aap woh comparison kho dete hain jis ke liye lock banaya gaya tha.

Phir AI ka answer apni Line 4 se compare karein. Aap ne aik specific finding likhi thi jo aap ka mind change karti. Kya AI ne woh finding di, ya nahin?

Agar AI ka answer woh nahin jo aap ko flip karta, aap ki Line 3 decision hold karti hai. Aap usay apni likhi hui wajah se defend kar sakte hain. Maya ka case (jo asal mein hua): us ki Line 4 kehti thi ke coding sirf tab jeetegi jab bootcamp Rust ya koi aisi cheez padhaye jo us ka school cover nahin karta. AI ne kaha bootcamp Python padhata hai, jo us ka school pehle se padhata hai. Yeh flipping condition nahin. Us ka decision waisa hi rehta hai: debate.
Agar AI ka answer bilkul wohi hai jo aap ko flip karta, aap ka decision badal jata hai, us wajah se jo aap ne pehle se set ki thi, is liye nahin ke AI confident laga. Maya ka case agar AI ne kuch aur kaha hota: farz karein AI yeh le kar aata "bootcamp embedded systems padhata hai, Python nahin." Yeh Maya ki Line 4 par bilkul theek baithta (school embedded systems nahin padhata). Woh coding par switch kar jaati, us wajah se jis par us ne Monday ko commit kiya tha, is liye nahin ke AI ne usay raazi kar liya.
Agar AI ka answer beech mein kahin hai, apni Line 3 reasoning par wapas jayein. Kya nai information usay waqai weak karti hai? Agar haan, decision badlein aur likhein kyun. Agar nahin, aap ka decision phir bhi hold karta hai. Maya ka case agar AI ambiguous hota: farz karein AI ne kaha "bootcamp pehle teen din Python cover karta hai aur phir React introduce karta hai." React aisi cheez hai jo us ka school nahin padhata, lekin yeh bootcamp ke sirf do din hain. Maya apni Line 3 dobara parhti hai: case yeh tha ke "doston ke saath do haftay debate seekhna, aik hafta zyada tar Python repeat karne se behtar hai." Do din React isay nahin badalta, bootcamp ab bhi zyada tar repeat material hai. Us ka decision waisa hi rehta hai.

Agar AI answer dene ke bajaye hedge kare, aik aur sentence ke saath dobara poochein: "Just give me the specific information; don't qualify it." Agar AI koi clarifying sawal poochay to answer dein magar add karein: "Then answer the original question." Maqsad aik concrete answer hai jise aap apni Line 4 ke saath rakh sakein, "it depends on several factors" wala paragraph nahin. Agar aap ki doosri koshish par bhi usable answer na mile, to aap ka Line 2 sawal shayad bohat broad hai. Usay zyada specific likhein, phir dobara try karein.

Lock ko revise karne par aik note. Agar AI ka answer aap ko ehsaas dilaye ke aap ki Line 4 ghalat thi, yani aap ne ghalat flipping condition name ki, to yeh aik real signal hai jise honor karna chahiye, magar dhyaan rakhein ke aap kab revise karte hain. Line 4 ko us se pehle revise karna jab aap ne abhi decide nahin kiya ke AI ke answer par kaise react karna hai, theek hai; aap ne koi cheez notice ki jo miss ki thi aur apni thinking update kar rahe hain. Line 4 ko AI ka answer aa jaane ke baad revise karna, taake answer flip count na ho, lock ko defeat kar deta hai. Test yeh hai ke kya aap nai Line 4 AI ka answer dekhe baghair bhi likhte. Agar haan, revise karein. Agar nahin, aap ki purani Line 4 qaaim rehti hai.

Check karein ke lock ne kaam kiya. Yeh sentence loud poora karne ki koshish karein: "main ne yeh is liye decide kiya..." Agar aap yeh "AI ne kaha" alfaaz use kiye baghair kar sakte hain, to lock ne kaam kiya. Agar nahin, to woh line dhoondein jo aap ne skip ki.

Woh sentence, jo aap loud poora kar sakte hain, documented evidence of thinking ka sab se chhota tukra hai jo aap bana sakte hain. Yeh wohi cheez hai jis ke bare mein is page ki shuru wali rule hai: koi polished answer nahin jo AI ne aap ke haath mein diya, balke aik wajah jis ki taraf aap point kar sakte hain. Neeche har discipline isi aik evidence ke tukre par build karti hai. Isay kaam karwa lein, baqi asaan ho jaate hain.

Neeche wali exercise yeh check nahin karti ke aap ka decision "sahi" hai ya nahin. Woh sirf yeh check karti hai ke aap ki chaar lines clear hain ya nahin: Kya aap ne asal decision name kiya? Kya aap ka sawal specific hai? Kya aap ki position committed hai ("it depends" nahin)? Kya aap ne woh specific AI answer name kiya jo aap ko flip karta? Agar aap ki pehli koshish messy hai to koi baat nahin.

1Your Work

Boxes mein kya daalna hai, is ke do options hain. Option 1: Maya ke liye chaar lines likhein, us ka decision (debate camp banaam coding bootcamp) use karein aur har line kya kehni chahiye us ka apna version. Grader check karega ke aap ki lines clear hain ya nahin. Option 2: apne week ke kisi real decision ke liye chaar lines likhein, koi cheez jo aap ko waqai figure out karni hai. Grader wohi cheez check karega. Dono options chalte hain; discipline aik hi hai.

Agar aap Option 1 le rahe hain, yahan reference ke taur par Maya ki lines hain:

Line 1 (kya ho raha hai): Woh apne doston wali cheez karegi ya woh jo akeli hoti to choose karti.

Line 2 (jo sawal madad karega): Kya bootcamp Python use karega (jo us ka school pehle se 9th grade mein padhata hai)?

Line 3 (decision): Debate. Doston ke saath do haftay, aisi cheez seekhna jo school offer nahin karta, agle saal ke curriculum ke aik-haftay repeat se behtar hai.

Line 4 (confidence + kya flip karega): 70%. Agar bootcamp Rust, embedded systems, ya koi aisi cheez padhaye jo us ka school cover nahin karta, to coding jeet jata hai.

Chaaron boxes bharein aur submit par click karein. Grader har line ko score karta hai aur batata hai kya behtar karna hai, jaise koi teacher foran aap ka homework check kar raha ho.

Prediction Lock: Four Lines

Line 1: Yeh decision asal mein kis bare mein hai? (Label ke neeche asal decision name karein.)

Line 2: Woh aik sawal jiska answer aap ko decide karne mein madad de. (Closed aur verifiable, open-ended nahin.)

Line 3: Aap ka decision aur aap ne yeh kyun kiya. (Reasoning ke saath aik committed position, guess nahin.)

Line 4: Aap kitne sure hain, aur AI ka kaunsa specific answer aap ka decision flip karega?

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Pehli dafa is mein taqreeban 8 minutes lagte hain. Score milne ke baad aik jagah dhoondhein jahan aap ko lagta hai ke AI grader ghalat hai. Yeh exercise ka sab se useful hissa hai.

Yeh Discipline 1 ka aadha hissa cover karta hai. Doosra aadha (AI jo kehta hai us ka track rakhna aur decide karna ke aap kin parts se agree, disagree, ya unhein change karna chahte hain) Discipline 2 hai.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

Prediction Lock koi nayi idea nahin. Yeh teen purani techniques ka AI-era version hai, jin mein se har aik decades se study ho rahi hai.

Premortem (Gary Klein, 2007). Project shuru hone se pehle, team tasawwur karti hai ke woh pehle hi fail ho chuka hai aur saari wajuhat likh deti hai ke kyun. Failure ki wajuhat pehle likhne ka amal, project ki optimism qaaim hone se pehle, woh risks samne le aata hai jo warna dabe rehte. Deborah J. Mitchell, Jay Russo, aur Nancy Pennington ki research ne paaya ke "prospective hindsight" (yani yeh tasawwur karna ke koi event pehle hi ho chuka hai) future outcomes ki wajuhat theek pehchanne ki salahiyat 30% barha deti hai. Jo discipline aap ne abhi seekhi woh choti shakl mein wohi karti hai: AI ke bolne se pehle aap apna decision aur woh specific finding likhte hain jo aap ka mind change kare. "Pehle likhna" load-bearing hissa hai.

Klein ka asli article parhein: Performing a Project Premortem, Harvard Business Review, September 2007.

Forecasting calibration (Philip Tetlock, Good Judgment Project, 2011-2015). Tetlock aur us ke saathiyon ne kayi saal ka aik tournament chalaya jahan hazaaron forecasters duniya ke events ke bare mein probabilistic predictions karte the. Behtareen forecasters, jinhein Tetlock "superforecasters" kehta tha, aik khaas aadat rakhte the: woh apni predictions confidence percentages ke saath answer aane se pehle record karte the, phir baad mein prediction ko outcome se compare karte the. Likhi hui prediction ke baghair aap bata nahin sakte ke aap ka andaza calibrated tha ya off, kyun ke aap apne "prior beliefs" ko us ke mutabiq bana lete hain jo bhi hua. Prediction Lock ki Line 4 (confidence percentage) is practice ka sab se chhota mumkin version hai. Mahinon aur saalon mein, apni locked-in confidence ko actual outcomes se compare karna hi woh tareeqa hai jis se judgment behtar hoti hai.

Project ke bare mein parhein: The Good Judgment Project (Wikipedia). Kitab ki shakl mein tafseel: Tetlock aur Gardner, Superforecasting: The Art and Science of Prediction (2015).

Anchoring (Amos Tversky aur Daniel Kahneman, 1974). Jab koi confident answer aap ke dimagh mein woh jagah le leta hai jahan aap ka apna answer aana tha, to woh confident answer aap ka reference point ban jata hai, aur aap phir bata nahin sakte ke us ke baghair aap kya sochte. Tversky aur Kahneman ke asli kaam mein numerical examples thay (logon se kaha gaya ke aik arbitrary number dekhne ke baad percentage ka andaza lagayein, to un ke andaze us number se anchored thay), lekin usool aam hai: koi bhi confident answer jo aap ke apna answer banane se pehle aap ke dimagh mein utar jaye, woh anchor ban jata hai jis se aap ki aagey ki thinking adjust hoti hai. AI ke answers by default confident hote hain. Yeh unhein powerful anchors banata hai. Prediction Lock woh move hai jo anchor ko banne se rokti hai: aap apna anchor pehle, likh kar, rakhte hain, AI ka anchor utarne se pehle.

Asli paper parhein: Judgment under Uncertainty: Heuristics and Biases, Science, Vol. 185, No. 4157, September 27, 1974, pp. 1124-1131. (Agar aap ke paas Science journal ka access nahin to is mirror par open-access mojood hai.)

Prediction Lock teeno ko jamaa karti hai. Pehle apna decision aur apni flipping condition likhein (premortem). Apni confidence record karein taake baad mein calibration check kar sakein (Tetlock). Aur dono kaam AI ka answer parhne se pehle karein, taake AI ki confidence woh anchor na ban jaye jis se aap adjust karte hain (Tversky aur Kahneman). Sticky note par chaar lines teen decades ki research ko teen-minute ki aadat mein samet deti hain.

Is exercise ka full version (10 ranked questions plus Reasoning Receipt template; 45-60 minutes) Part 0 Chapter 1, Lesson 1 mein hai. Yeh page discipline sikhata hai. Woh page isay system banata hai.

Discipline 2: Reasoning Receipt

Aap ne subah Claude ke saath aik report par kaam kiya. Nateeja achha lagta hai. Aap usay bhej kar aage barh jaate hain. Do haftay baad koi poochta hai: "Is mein se aap ne waqai kaun se parts check kiye? Kaun se parts badle?" Aap ke paas koi answer nahin. Aap ne parha jo AI ne likha, theek laga, to use kar liya. Kaam ho gaya, magar aap ne us ke bare mein kabhi waqai socha nahin.

Yeh AI ko apni jagah sochne dene (Discipline 1) ke baad doosra sab se aam AI failure mode hai. Tab bhi jab aap ki apni position lock ho, AI ke drafts bare polished blocks mein aate hain: paanch suggestions, chhe-paragraph memo, das-row plan, aur aap baad mein un mein se kisi ko defend nahin kar sakte kyun ke aap ne kabhi track nahin kiya ke har piece ke bare mein aap ne kya decide kiya.

Isay theek karne ka tareeqa yeh hai. Har dafa AI aap ko koi claim, recommendation, ya writing ka tukra de jo aap ke final kaam mein jata hai, aap aik aik-line note banate hain jo batata hai ke aap ne us ke saath kya kiya aur kyun. Poori cheez nahin, bas har piece ka aik note. Yeh notes mil kar Reasoning Receipt kehlate hain.

Aik row aisi dikhti hai. Farz karein aap ne Claude se aik group presentation plan karne mein madad maangi, aur us ne suggest kiya: "Presentation aik chhote video clip se shuru karein taake tawajjo mile." Aap soch-bichaar karte hain. Aap ke teacher ne is semester pehle kaha tha ke visual openings ko behtar grades milte hain, to yeh suggestion us se match karti hai jo aap is class ke bare mein pehle se jaante hain. Aap isay rakhne ka decide karte hain.

Woh decision aap ki receipt mein aik row ban jata hai:

AI ne kya kaha	Aap ne kya kiya	Kyun
Tawajjo ke liye aik chhote video clip se shuru karein.	ACCEPT	Hamare teacher ne kaha visual openings ko behtar grades milte hain. Yeh fit hota hai.

Teen columns. AI ne kya kaha (taake future aap ko yaad rahe kya decide ho raha tha), aap ne kya kiya (aik-lafz ka label), aur kyun (aik sentence taake row baad mein defensible ho).

Ab farz karein Claude ka agla suggestion tha "har banday ko bolne ke liye 5 minutes dein." Aap ke group mein chaar members hain aur kul 15 minutes. Hisaab nahin baithta. To aap isay reject karte hain:

AI ne kya kaha	Aap ne kya kiya	Kyun
Har banday ko bolne ke liye 5 minutes dein.	REJECT	Hamare paas 4 logon ke liye 15 minutes hain. Hisaab nahin baithta.

Yeh hai discipline. Har AI suggestion ki aik row, teen columns har aik mein.

Paanch labels. Aap ne kya kiya hamesha paanch categories mein se aik mein aata hai. Zyada tar waqt aap ACCEPT, REJECT, ya MODIFY use karein ge. Baqi do (SURFACED aur MISSED) woh cases pakarte hain jo warna skip karna aasan hai.

Label	Aap ne kya kiya	Aik sentence likhein jo why bataye
ACCEPT	AI ne jo kaha aap ne wohi rakha, koi tabdeeli nahin.	Aap ne us par kyun trust kiya.
REJECT	Aap ne tay kiya ke AI ghalat hai aur usay hata diya.	Kis cheez ne aap ko disagree karwaya.
MODIFY	Aap ne idea rakha magar us ka aik hissa badal diya.	Aap ne kya badla aur kyun.
SURFACED	AI ne aisi cheez uthai jo aap ne sochi nahin thi. Aap ne usay rakha.	Yeh kyun matter karti hai.
MISSED	Aap ne aisi cheez notice ki jo AI batana bhool gaya. Aap ne usay add kiya.	Kya missing tha aur kyun matter karta hai.

ACCEPT, REJECT, aur MODIFY basic moves hain. SURFACED un lamhon ke liye hai jab AI ne aap ko kuch sikhaya, woh track karne layeq hain kyun ke yeh woh cases hain jahan AI ne waqai aisi thinking add ki jo aap akele na karte. MISSED us ke liye hai jo AI ne kaha nahin magar kehna chahiye tha, yeh woh cases hain jahan aap ke apne judgment ne aisi cheez pakri jise AI ki drafting ne nazar-andaaz kar diya.

Achhi receipt mein waqt ke saath paanchon ka mix hota hai. Agar har row ACCEPT kehti hai, to aap waqai soch nahin rahe, aap bas us par dastkhat kar rahe hain jo AI ne likha.

"Lekin koi mere kaam ka audit nahin karta, to bother kyun?"

Yeh is discipline par sab se reasonable objection hai, aur isay aik real answer chahiye. Zyada tar readers, zyada tar waqt, audit nahin hote. Aap ka boss nahin poochta. Aap ka professor aage barh jata hai. Aap ka client sign off kar deta hai. Agar Reasoning Receipt ka waahid payoff "agar koi poochay" hota, to receipt zehmat ke qabil nahin hoti.

Receipt rakhna teen cheezen karta hai, tab bhi jab koi kabhi nahin poochta.

Pehla, likhne ka amal aap ka decision badal deta hai. Jab aap koi AI suggestion khamoshi se accept karte hain, aap ka dimagh usay "theek lagta hai, aage barho" ke tor par process karta hai. Jab aap ko aik-lafz label aur aik-sentence reason likhni padti hai, aap ke dimagh ko suggestion ko waqai jaanchna padta hai. Zyada tar readers, jab pehli dafa yeh try karte hain, har session mein kam az kam aik row dhoondte hain jahan woh "why" wala sentence poora nahin kar paate. Woh row aisi cheez thi jise woh soche baghair use karne wale the. Receipt usay ship hone se pehle pakar leti hai.

Doosra, receipt aap ke kaam ka hissa ban jaati hai, sirf us ka record nahin. Discipline 1 wali bank manager ne apni position aur data ke darmiyan gap ko apni report ki opening line bana diya. Neeche agle example wali student ne apni receipt ko apne group ke saath aik working document ki tarah use kiya, audit trail ki tarah nahin. REJECT label wali row aksar final document mein aik "considered alternatives" paragraph ban jaati hai. SURFACED label wali row aksar woh sab se dilchasp insight ban jaati hai jo aap meeting mein laate hain. Receipt aik working tool hai, filing cabinet nahin.

Teesra, future aap sab se aam auditor hai. Aaj se teen mahine baad, aap is kaam ko dekhein ge aur yaad nahin ho ga ke kaun se parts aap ke the, kaun se AI ke, ya aap ne jo decide kiya, kyun kiya. Receipt future aap ke naam aik note hai. Zyada tar dafa receipt jab kaam aati hai, sawal khud aap ki taraf se aata hai, kisi boss ki taraf se nahin.

Audit scenario sab se visible payoff hai, magar sab se rare. Pehle teen payoffs har dafa hote hain jab aap receipt rakhte hain, tab bhi jab koi usay kabhi nahin parhta. Page ki markazi rule ka amli matlab yahi hai: deliverable thinking ka documented evidence hai. Receipt aap ke kaam se alag nahin, woh kaam ko us waqt shape karti hai jab aap usay bana rahe hote hain, aur waqt ke saath woh wohi cheez hai jo aap ke paas rehti hai jab project ki yaad dhundli pad chuki hoti hai.

Reasoning receipt ki anatomy: teen columns jo har faisla-kun call ko annotate karte hain. AI ne kya kaha, Aap ne kya kiya (ACCEPT, REJECT, MODIFY, SURFACED, MISSED mein se aik), aur Kyun. Har row aik decision document karti hai jo insaan ne AI output ke aik piece ke bare mein liya. Receipt mein har row aik decision hai. Label batata hai aap ne kya kiya. "Why" future aap ko (ya kisi aur parhne wale ko) batata hai ke row par kyun trust kiya ja sakta hai.

Real life mein yeh kaisa dikhta hai.

Aik student ne Claude se class ke liye group presentation plan karne mein madad maangi. Claude ne poora plan diya. Use bas istemaal karne ke bajaye, student ne har suggestion par jaa kar likha ke us ne kya socha:

AI ne kya kaha	Label	Kyun
"Presentation aik chhote video clip se shuru karein taake tawajjo mile."	ACCEPT	Achha idea. Hamare teacher ne kaha visual openings ko behtar grades milte hain.
"Har banday ko bolne ke liye 5 minutes dein."	REJECT	Hamare paas kul sirf 15 minutes hain aur hum 4 log hain. Hisaab nahin baithta.
"Q&A session ke saath khatam karein."	MODIFY	Q&A theek hai, magar hum 3 backup questions tayyar karein ge agar koi kuch na poochay.
"Jo app aap ne banayi us ka live demo add karein."	SURFACED	Yeh maine socha nahin tha. Live demo hamari presentation ko numayan kar dega.
(AI ne yeh nahin bataya ke projector ke liye laptop aur adapter kaun laayega.)	MISSED	Yeh maine add kiya. Pichli dafa hamara group adapter bhool gaya aur 5 minutes zaaya hue.

Us ne receipt apne group ke saath share ki. Presentation ke baad, teacher ne poocha ke har banday ko 5 minutes kyun nahin diye. Us ne row 2 ki taraf ishara kiya: "Hamare paas 4 logon ke liye sirf 15 minutes the. Hisaab nahin baithta tha." Woh aik sentence kaafi tha. Receipt ke baghair, usay sab kuch scratch se yaad kar ke explain karna padta.

Receipt ke baghair kya hota hai:

AI ne kya kaha	Label	Kyun
"Aik chhote video clip se shuru karein."	ACCEPT	Sahi lagta hai.
"Har banday ko 5 minutes dein."	ACCEPT	Sahi lagta hai.
"Q&A session ke saath khatam karein."	ACCEPT	Sahi lagta hai.
"Live demo add karein."	ACCEPT	Sahi lagta hai.
(Kuch likha nahin gaya.)

All-ACCEPT aik warning signal hai

Agar har row ACCEPT kehti hai aur reason "sahi lagta hai" hai, to aap ne us ke bare mein waqai socha nahin. Aap ne bas wohi copy kiya jo AI ne kaha. Achhi receipt mein labels ka mix hota hai. Agar aap explain nahin kar sakte ke aap ne kisi cheez ko kyun accept kiya, to aap ne usay rakhne ka decision waqai nahin kiya. Aap bas us ke saath chal pade.

Khud try karein

Aap apni university ka saalana tech fest organize kar rahe hain. Aap ki team mein 10 members hain. Event 3 haftay mein hai. Aap ne abhi marketing shuru nahin ki. Aik aur university ne usi weekend par milta-julta event announce kar diya. Aap ne AI se poocha: "Kya hamein event aik hafta pehle kar dena chahiye, ya original date rakhni chahiye?" AI ne aap ko paanch suggestions diye. Har aik ke liye, aik label chunein (ACCEPT, REJECT, MODIFY, SURFACED, ya MISSED) aur aik sentence likhein jo why bataye.

AI ne kya suggest kiya

"Isay pehle kar do. Jab do events aik hi audience ke liye muqabla karte hain to pehla hona matter karta hai."
"Agar aap original date rakhte hain, students dono events compare karein ge aur shayad doosra pick kar lein."
"Aap ki social media posts Thursday ko sab se zyada engagement leti hain, to marketing isi Thursday shuru karein."
"Aik hafta pehle move karne ka matlab hai team ke paas 3 ke bajaye sirf 2 haftay tayyari hain."
"Zyada tar students decide karte hain ke kaun se events attend karne hain is bunyaad par ke un ke dost kahan ja rahe hain."

1Your Work

AI grader do cheezen check karega:

Kya aap ne apni reasoning explain ki, ya bas "sahi lagta hai" likh diya? 1-10 rate karega. Meri sab se kamzor explanation quote karega.
Kya aap ne aik se zyada label use kiya? Agar har row ACCEPT kehti hai, to aap ne us ke bare mein waqai socha nahin. 1-10 rate karega.

Mera kaam rewrite na karein. Agar koi box empty ya vague ho, bas seedha keh dein.

Claim 1: "Isay pehle kar do. Pehla hona matter karta hai."

Label (ACCEPT/REJECT/MODIFY/SURFACED/MISSED) + aik sentence mein why

Claim 2: "Students dono events compare karein ge aur shayad doosra pick kar lein."

Label + aik sentence mein why

Claim 3: "Marketing isi Thursday shuru karein kyun ke tab posts ko sab se zyada engagement milti hai."

Label + aik sentence mein why

Claim 4: "Pehle karne ka matlab 3 ke bajaye sirf 2 haftay tayyari."

Label + aik sentence mein why

Claim 5: "Students is bunyaad par decide karte hain ke un ke dost kahan ja rahe hain."

Label + aik sentence mein why

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Pehli dafa is mein taqreeban 10-15 minutes lagte hain. Score milne ke baad koi aisi row dhoondein jahan aap ne bina kisi real reason ke "sahi lagta hai" likha. Wohi row hai jahan aap ne apni thinking kiye baghair AI ki thinking accept ki. Wapas jaa kar us aik row ke liye aik real explanation likhein.

Aap ne jo abhi kiya woh har suggestion ko aik aik kar ke check karne mein madad deta hai. Lekin yeh har suggestion ke andar ki ghaltiyan nahin pakarta, jaise banaye gaye facts, purani information, ya AI ka kisi aisi cheez par confident lagna jo us ne ghalat ki. Yeh Discipline 3 ka kaam hai.

Aik good example dekhna chahte hain? (Apna submit karne ke baad isay kholein.)

Aik aur student ne wohi tech fest exercise kiya. Yeh waahid sahi answer nahin, magar yeh dikhata hai ke achhi receipt kaisi lagti hai.

Claim	Label	Kyun
1	REJECT	Yahan pehla hona matter nahin karta. Students events is bunyaad par chunte hain ke kya mazedaar lagta hai, yeh nahin ke kaun pehle announce hua.
2	MODIFY	Students compare kar sakte hain, magar sirf tab jab unhein dono ke bare mein pata chale. Agar hum behtar marketing karein, doosra event matter nahin karta.
3	ACCEPT	Pichle semester ka hamara Instagram data dikhata hai ke Thursday posts ko 2x zyada likes milte hain. Yeh durust hai.
4	SURFACED	Yeh maine socha nahin tha. Aik hafta prep time khona aik real masla hai kyun ke hum ne abhi venue book nahin kiya.
5	ACCEPT	Yeh sach hai. Pichle saal registration form mein "apna dost laao" option add karne ke baad sign-ups mein bara izafa hua.
6	MISSED	AI ne yeh nahin bataya ke hamare sab se bare sponsor ko 3 haftay notice chahiye. Pehle karne ka matlab hum sponsorship kho sakte hain.

Yeh achha kyun hai: Sirf do ACCEPT, aur dono ke peeche real reasons hain (pichle semester aur pichle saal ka actual data, sirf "sahi lagta hai" nahin). MISSED row (row 6) aisi cheez pakarti hai jo AI jaan hi nahin sakta tha (sponsor ka 3-haftay notice wala usool). Student ne aakhir mein original date rakhne ka decide kiya, magar aisi wajah se jo AI ne kabhi mention nahin ki: sponsorship.

Yeh kya karne ki koshish nahin karta: chalaak banna. Zyada tar rows aik sentence hain. Point real reasons likhna hai, lambi nahin.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

Reasoning Receipt bhi koi nayi idea nahin. Jo aap ne decide kiya aur kyun, usay likhna un sab se zyada study-shuda aadaton mein se hai ke experts asal mein kaise sochte hain. Teen tehqeeqi silsile bataate hain ke yeh kyun kaam karta hai.

Reflection-in-action (Donald Schon, 1983). Doctors, architects, engineers, aur teachers asal mein kaise kaam karte hain, is ka mutaala karte hue Schon ne paaya ke maahir professionals sirf act kar ke aage nahin barhte, woh aik chalti hui internal commentary rakhte hain, hairaaniyan notice karte hain aur tay karte hain ke un ke bare mein kya karna hai jab kaam ho raha hota hai, baad ke review mein nahin. Jo professionals sab se tez behtar hue woh wohi the jinhon ne us commentary ko tacit chhorne ke bajaye explicit kar diya. Reasoning Receipt wohi commentary likhi hui shakl mein hai: khamoshi se yeh sochne ke bajaye ke "yeh AI suggestion theek nahin lag rahi," aap label aur reason tab likhte hain jab aap abhi kaam mein hote hain, jahan woh badal sakti hai ke aap aage kya karte hain.

Mazeed parhein: Reflective practice (Wikipedia), jo Schon ki The Reflective Practitioner (Basic Books, 1983) ka khulasa karta hai.

Single-loop banaam double-loop learning (Chris Argyris, 1977). Argyris ne do qism ki correction ke darmiyan lakeer kheenchi. Single-loop learning foran wali ghalti theek karti hai: answer ghalat tha, to aap answer badal dete hain. Double-loop learning peeche hat kar poochti hai ke kya poora approach ya assumption shuru hi se ghalat tha. Us ki finding yeh thi ke zaheen, qaabil log by default single-loop mode mein phans jate hain; woh output tune karte hain aur frame par kabhi sawal nahin uthate. Aisi receipt jahan har row ACCEPT kehti hai woh single-loop thinking ki nazar aane wali shakl hai: aap outputs ko approve kar rahe hote hain bina yeh poochay ke approach sahi hai ya nahin. Har row par aik real "why" ki paabandi, aur yeh notice karna ke aap kab aik nahin likh pa rahe, wahi aap ko double loop mein dhakelta hai.

Argyris ka asli article parhein: Double Loop Learning in Organizations, Harvard Business Review, September 1977.

Elaboration aur generation effect (Brown, Roediger & McDaniel, 2014). Decades ki memory research aik saadah finding par jama hoti hai: aap kisi cheez ko us waqt kahin behtar yaad rakhte hain jab aap usay apne alfaaz mein dalte hain aur us se jorte hain jo aap pehle se jaante hain, bajaye is ke ke aap usay sirf dobara parhein. Explanation ko khud generate karne ka amal, chahe aik hi sentence ho, wohi paaedaar memory banata hai. Aap ki receipt mein har "why" bilkul yahi move hai. Teen mahine baad, jis row ke liye aap ne aik real reason likha woh wohi hai jo aap ab bhi samjhein ge; jis row par aap ne "sahi lagta hai" ki muhar lagai woh khaali ho gi.

Mazeed parhein: Make It Stick: The Science of Successful Learning (Belknap Press of Harvard University Press, 2014), kitab ke markazi findings ka khulasa.

Reasoning Receipt teeno ko jamaa karti hai. Aap har AI claim ke bare mein apna decision tab likhte hain jab aap abhi kaam mein hote hain (Schon), majboor kiya gaya "why" aap ko outputs par muhar lagane se approach par sawal uthane ki taraf le jata hai (Argyris), aur reason ko apne alfaaz mein dalna wohi hai jo aap ko baad mein yaad rakhwata hai (Brown, Roediger & McDaniel). Kisi ne Reasoning Receipt ko khaas tor par AI ke khilaaf test nahin kiya, magar is ke neeche wali aadat, apni choices likhna aur unhein explain karna, us ke sab se mustahkam nataij mein se hai ke log kaise sochte aur seekhte hain. Isay AI output par istemaal karna qudrati agla qadam hai.

Go deeper: Part 0 Chapter 1: Asking Better Questions. Full version (aik real AI conversation ke against 10-row receipt, plus Contradiction Challenge jahan aap aik doosri AI se apni reasoning par hamla karwate hain, 45-60 min) wahan foundational sequence ke hissay ke taur par hai. Yeh page discipline sikhata hai. Woh chapter isay aik aisi aadat banata hai jo aap har high-stakes AI conversation par chala sakte hain.

Part 2: Detection (jo AI miss karti hai usay catch karna)

Part 1 ne aap ko sikhaya ke AI use karne se pehle kaise sochna hai. Part 2 aap ko sikhati hai ke AI jo wapas deta hai us mein ghaltiyan kaise spot karni hain.

Masla yeh hai: AI utni hi confident lagti hai chahe woh sahi ho ya ghalat. Us ki sab se buri ghaltiyan aksar un jumlon mein chhupti hain jo sab se polished lagte hain. AI aksar us aik cheez par focus karti hai jo aap ne poochi aur side effects ignore kar deti hai.

Discipline 3 (Error Taxonomy) aap ko chhe aam AI ghaltiyon ki aik checklist deti hai taake output par trust karne se pehle aap unhein scan kar sakein. Discipline 4 (Thinking in Systems) aap ko sikhati hai ke poochein "agar main yeh karun, to aur kya badalta hai?" taake aap woh side effects pakar lein jo AI ne miss ki.

Discipline 3: Error Taxonomy

Yeh discipline AI Asal Mein Kya Hai, Idea 3 ka practical jawab hai: machine ke andar koi built-in truth-checker nahin, is liye checker aap hain. Neeche ke chhe error types practice mein "checker hona" kaisa lagta hai, yeh dikhate hain.

Aap ne shayad yeh tajurba kiya hai. Aap AI se aik sawal poochte hain, answer smooth aur professional lagta hua wapas aata hai, aap usay parhte hain, sab theek lagta hai, aap use kar lete hain. Teen din baad aap ko pata chalta hai ke aik number ghalat tha, ya AI ne jis source ka zikr kiya woh asal mein mojood hi nahin. Ghalti wahin baithi thi, magar aap miss kar gaye kyun ke writing itni achhi lag rahi thi.

Yeh hissa matter karta hai: us miss hui ghalti ki keemat aam tor par aap chukate hain, koi auditor nahin jo baad mein aap ko pakre. Agar AI ne aap ko bataya ke aik used car ke 32,000 miles hain jab us ke asal mein 58,000 the, to aap kisi meeting mein sharminda nahin hote, aap ghalat car khareed lete hain. Agar AI ne aap ki report ke liye koi statistic ghar se bana di, to aap sirf tab bure nahin lagte jab koi check kare; aap ne aik aise number ki bunyaad par decision liya jo kabhi real tha hi nahin. AI ki ghaltiyan us shakhs ko nuqsaan pohanchati hain jo un par pehle act karta hai. Woh shakhs aap hain.

"Taxonomy" kyun? Taxonomy bas aik naming system hai, labeled categories ka aik tay-shuda set jin mein aap cheezon ko chhantte hain, jaise biologists jeevit cheezon ko species mein chhantte hain. Taqat naming mein hai. "Check karo ke yeh achha hai ya nahin" act karne ke liye bohat vague hai; aap ki aankh page par phisal jati hai aur kuch usay rokta nahin. Lekin "check karo ke koi fabricated source to nahin" aik specific shikaar hai aik specific target ke saath, to aap waqai har citation par ruk kar dekhte hain. Error Taxonomy AI ghalti ki chhe named categories hain. Unhein naam dena hi woh cheez hai jo aik vague pareshaani ("kuch ghalat ho sakta hai") ko chhe concrete searches mein badal deti hai jo aap waqai chala sakte hain.

Unhein pakarne ka tareeqa yeh hai. AI ka output parh kar khud se "kya yeh theek lagta hai?" poochne ke bajaye, aik waqt mein aik specific qism ki ghalti dhoondte hue us mein se guzrein. Chhe types hain:

Ghalti ki qism	Kaisa dikhta hai	Pehle kahan dekhein
Factual error	Aik ghalat fact: ghalat number, ghalat date, ghalat naam.	Koi bhi sentence jisme specific number ho. Theek lagne wale numbers cheezon ko researched dikhate hain. Misaal: "73.6% log AI ke numbers check nahin karte." Yeh real lagta hai. Maine abhi bana diya.
Logical gap	Conclusion evidence se asal mein follow nahin karta.	"Is liye" ya "to" jaise alfaaz dhoondein. Phir poochein: kya evidence yeh waqai sabit karta hai, ya koi step missing hai?
False confidence	AI kisi ghair-yaqeeni cheez ko aise bayan kare jaise woh fact ho.	Sab se smooth lagne wale paragraphs. Agar AI "may" ya "could" use karta hai, to woh jaanta hai ke unsure hai. Agar AI koi debatable cheez bina kisi "may" ya "could" ke bayan kare, wahi warning sign hai.
Missing context	AI ne aik aham detail chhor di jo answer badal deti.	Sochein ke aik expert pehle kya poochega. Agar aap poochte "magar X ka kya?", to AI ne shayad us ke bare mein socha hi nahin.
Fabricated source	AI kisi aisi kitab, article, study, ya tool ka zikr kare jo asal mein mojood nahin.	Har source check karein jo AI naam le. Title Google karein. Agar nahin milta, to AI ne shayad usay ghar se bana liya.
Stale fact	Koi cheez jo kabhi sach thi magar ab sach nahin.	Koi bhi cheez jo waqt ke saath badalti hai: prices, rules, qawaneen, software versions, kisi company ko kaun chalata hai.

Aik scan kaisa mehsoos hota hai. Sirf pehli qism lein, Factual error. Hidayat kehti hai: koi bhi sentence dekhein jisme specific number ho. To aap AI ka output parhte hain aur har number par rukte hain, baqi sab nazar-andaaz kar ke. Farz karein AI ne likha "is car ke odometer par 32,000 miles hain." Yeh aik number hai, to aap rukte hain. Aap yeh nahin poochte ke "kya yeh theek lagta hai?", aik ghalat mileage bilkul utni hi maqool lagti hai jitni aik sahi. Us ke bajaye aap usay source ke against check karte hain: aap dashboard ki photo dekhte hain. Us par 58,000 likha hai. Pakra gaya. Aap ne isay dhyaan se parh kar nahin pakra; aap ne is liye pakra ke aap khaas tor par aik qism ki ghalti ka shikaar kar rahe the, aik ghalat number, aur number hi woh jagah hai jahan aap ruke.

Yeh poori technique hai, chhe baar dohrayi gayi. Har pass aik qism ka shikaar karta hai. Aap output ko chhe baar nahin parh rahe; aap usay aik baar parh rahe hain magar dimagh mein chhe mukhtalif sawal le kar, har sawal jis jagah ishara kare wahan ruk kar. Neeche wali exercise mein aap do passes (Factual error aur Fabricated source) practice karein ge taake rhythm seekh lein. Agla worked example chhron ko dikhata hai.

Aik confident lagne wala AI paragraph jis par chhe error types annotations ke taur par overlaid hain. Factual (ghalat fact), Logical Gap (chhoda gaya step), False Confidence (barha-charha yaqeen), Missing Context (mutalliqa constraint gira diya), Fabricated Source (banayi gayi citation), Stale Fact (kabhi sach, ab nahin). Chhe error types apna elaan nahin karte. Woh un paragraphs mein chhupte hain jo sab se professional parhe jate hain, isi liye naam se scan karna feel se parhne se behtar hai.

Real life mein chhron kaise dikhte hain.

Aik parent aik bharosemand used car dhoond rahe the. Unhein aik listing pasand aayi: 2021 Honda CR-V. Use dekhne ke liye aik ghante drive karne se pehle, unhon ne Claude se isay dekhne ko kaha. Unhon ne listing, photos, aur apne mechanic ka aik note paste kiya. Claude ne aik saaf, confident summary likhi: kam miles, clean history, mazboot engine, aik rebate jo lena chahiye. Achha parha gaya. Woh taqreeban apne partner ko "yehi khareed lete hain" ke saath forward karne wale the. Us ke bajaye, unhon ne chhe-row scan chalaya.

Error type	Write-up mein kya mila	Verdict
Factual error	Write-up ne kaha: "odometer par 32,000 miles." Listing mein dashboard ki photo saaf 58,000 dikha rahi thi. 26,000 miles ka farq.	Pakra gaya. Photo se theek kiya.
Logical gap	Write-up ne kaha: "is ki accident history clean hai, is liye is mein koi mechanical masla nahin." Clean accident record engine ke bare mein kuch nahin kehta. "Is liye" qaaim nahin raha.	Pakra gaya. Clean history clean engine nahin.
False confidence	Write-up ne kaha: "is engine se aap ko kam az kam 200,000 trouble-free miles milein ge." Koi "should" nahin, koi "likely" nahin, koi basis nahin. Flat waada sara kaam kar raha tha.	Pakra gaya. "agar service hoti rahe to bohat si CR-Vs lamba chalti hain" ke taur par dobara likha.
Missing context	Write-up ne timing belt ka kabhi zikr nahin kiya, jo 60,000 miles ke aas paas tabdeel hona hota hai. Parent ke apne mechanic ne usay flag kiya tha. Model ne woh note kabhi dekha hi nahin.	Pakra gaya. Belt ko pehli check ki cheez ke taur par add kiya.
Fabricated source	Write-up ne kaha: "jaisa Consumer Reports ne apne March 2026 reliability issue mein likha, yeh market ki sab se dependable small SUV hai." Parent ne Consumer Reports check kiya. Aisa koi note nahin.	Pakra gaya. Quote hata diya.
Stale fact	Write-up ne kaha: "yeh ab bhi dealer ke $1,000 loyalty rebate ke liye qualify karti hai." Parent ne dealer ko call kiya. Woh rebate pichle mahine khatam ho gaya.	Pakra gaya. Hisaab se rebate nikaal diya.

Aik chhoti si summary mein chhe mein se paanch mistake types samne aa gaye. Sab se mushkil pakarne wala woh nakli Consumer Reports quote tha, kyun ke woh bilkul aisa lagta tha jaisa koi asli magazine likhti. Kyun ke parent ne har mistake type ko naam se check kiya, woh car dekhne gaye to unhein real mileage, zaroori repair, aur asal qeemat ka pata tha. Dhyaan dein ke is ne kis ki hifaazat ki: kisi auditor ke saamne parent ki saakh ki nahin, balke parent ke apne wallet ki. Agar woh summary par bharosa kar lete, to woh aik ghante drive kar ke aisi car khareedne jate jise woh 32,000 miles wali samajhte the, aisi qeemat dete jo aik aise rebate ko maan kar thi jo ab mojood nahin tha, aur aik aisi repair skip kar dete jis ke aane ka unhein pata nahin tha. Scan ne unhein bura dikhne se nahin bachaya. Us ne unhein apne hi decision ke bare mein ghalat hone se bachaya.

Agar aap bas parhein bina qism ke hisaab se check kiye, to kya hota hai:

Aap kaise parhte hain	Kya miss hota hai	Kyun
Aap poori cheez yeh poochte hue parhte hain ke "kya yeh achhi lagti hai?"	Ghalat numbers. Jab sab smooth lagta hai to aap ki aankh numbers ke upar se guzar jati hai.	Ghalat mileage (58,000 ke bajaye 32,000) miss karna aasan hai. "Factual Error" ke liye check karna aap ko har number par rukne par majboor karta hai.
Aap kisi quote par is liye trust karte hain ke woh aik jaane-pehchane brand ka naam leta hai	Nakli Consumer Reports quote. Asli magazine ka naam, magar quote banaya gaya tha.	Yeh real lagta hai, aur yahi to trap hai. "Fabricated Source" ke liye check karna aap ko har quote look up karne par majboor karta hai.
Aap "is liye" ko bas aik jorne wala lafz samajh kar parhte hain	Logical gap. "Clean history, is liye koi masla nahin" theek lagta hai magar aik step chhod deta hai.	Jab aap "Logical Gap" ke liye check karte hain, aap har "is liye" par rukte hain aur poochte hain: kya yeh waqai woh sabit karta hai jo daawa karta hai?
Aap missing information sirf tab notice karte hain jab kuch ajeeb lage	60,000 miles par due timing belt ki tabdeeli. AI ne kabhi zikr nahin kiya, to page par koi cheez aap ko warn nahin karti.	Missing information kabhi khud nahin ubharti. Aap ko khud se poochna parta hai: jo car ke bare mein jaanta ho woh kya poochega jo AI ne nahin poocha?

Jis parent ne qism ke hisaab se check kiya aur jis ne bas casually parha, woh aik hi shakhs ho sakte hain. Farq sirf yeh hai ke unhon ne AI ka output kaise parha: aik ne har mistake type ko naam se check kiya, doosre ne bas parha aur umeed ki ke kuch ghalat na ho.

Bhari hui scan grid sirf chalane ki nahin, rakhne ki bhi cheez hai. Yeh wohi qism ka evidence hai jis ke bare mein page ki rule hai: deliverable thinking ka documented evidence hai. Jab aap kisi ko report dein aur woh poochein "kya aap ne AI ke numbers check kiye?", to grid aap ka answer hai. Aksar, yeh future aap ke naam aik note hota hai: aaj se chhe mahine baad, jab aap soch rahe hon ke aap ne woh statistic verify ki thi ya bas us par trust kiya, grid aap ko batati hai ke kya kiya.

Khud try karein

Aap is weekend aik used car khareed rahe hain. Seller kehta hai ke aik aur khareedaar pehle se interested hai, to aap ko jaldi decide karna hai. Aap ne AI se kaha ke do cars compare kar ke bataye kaunsi khareedni hai. Yeh hai jo AI ne wapas likha. Isay parhein, phir oopar di gayi chhron mistake types ke liye check karein. Factual Error aur Fabricated Source se shuru karein (in dono ko miss karna aap ko sab se zyada paisay ka nuqsaan deta hai). Neeche boxes bharein.

Aap ko kaunsi car khareedni chahiye?

2020 Toyota Corolla lein. Corolla 47 mpg combined deti hai, to aap apne size ki zyada tar cars ke muqable pump par bohat kam kharch karein ge. CarReliability Index 2026 rankings ke mutabiq, Corolla 10 mein se 9.4 score karti hai, apni class mein top spot. 2019 Honda Civic bhi aik achhi car hai. Civic ki mileage kam hai, is liye agar aap aage chal kar kam surprises chahte hain to yeh zyada reliable choice hai.

Dono mein se koi bhi car aik aur decade bina kisi bare repair ke chalegi, to aap price aur color par chunaav kar sakte hain aur achha mehsoos kar sakte hain. Dono ab bhi $2,000 state clean-vehicle rebate ke liye qualify karti hain, jo aap ki asal cost achhi tarah neeche le aata hai. Har soorat mein, aap ko aik bharosemand car mil rahi hai.

(Agar aap chahein, to car example skip kar ke apni life se koi bhi real AI output use kar sakte hain: koi homework answer, college application draft, ya research summary. Chhe mistake types kisi bhi topic par kaam karte hain.)

1Your Work

AI grader do cheezen check karega:

Kya aap ne waqai har type check ki, ya bas parh kar andaza laga liya? 1-10 rate karein. Achhe answer mein har row ke liye kuch likha hota hai. Agar aap ne koi type check ki aur kuch ghalat na mila, to khaali chhorne ke bajaye "check kiya, kuch nahin mila" likhein.
Kya aap ne aham ghaltiyan pakar lin, ya sirf aasan wali? 1-10 rate karein. Agar maine usi write-up mein koi bari ghalti miss ki, to batayein kaunsa sentence mujhe pakarna chahiye tha.

Mera kaam rewrite na karein. Agar koi row bina explanation ke khaali hai, bas seedha keh dein.

Chhron mistake types mein se har aik ke liye, AI ki write-up se woh exact sentence copy karein jisme ghalti hai, aur batayein kya ghalat hai. Agar aap ne koi type check ki aur koi ghalti na mili, to "check kiya, kuch nahin mila" likhein.

Factual error: [sentence paste karein] - [kya ghalat hai] Logical gap: [sentence paste karein] - [kya ghalat hai] False confidence: [sentence paste karein] - [kya ghalat hai] Missing context: [AI ne kya chhoda] Fabricated source: [sentence paste karein] - [kya ghalat hai] Stale fact: [sentence paste karein] - [kya ghalat hai]

Aap har aik ke bare mein kitne sure hain? (1-10 rate karein aur aik sentence mein why batayein.)

Misaal: 'Factual error: 9, maine asal mpg look up kiya. Fabricated source: 6, mujhe yeh index online nahin mila magar main 100% sure nahin.'

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Pehli dafa is mein taqreeban 8-15 minutes lagte hain. Practice se yeh tez hota hai. Score milne ke baad aik jagah dhoondein jahan AI grader aap se disagree karta hai. Wahi disagreement woh jagah hai jahan aap sab se zyada seekhte hain.

Aap ne jo abhi kiya woh AI ke answer ke andar ghaltiyan dhoondne mein madad deta hai. Lekin aik aur qism ka masla hai jo yeh nahin pakarta: AI ki advice par act karne ke baad kya hota hai? Agar aap ghalat car khareed lein, to aap repairs par paisa khote hain. Agar koi company buri AI advice follow kare, to customers chale jate hain. Aik decision doosra masla peda karta hai, jo aik aur. Discipline 4 aap ko sikhati hai ke un chain reactions ko hone se pehle trace karein.

Compare karne ke liye aik strong sample chahiye? (Apna submit karne ke baad kholein.)

Aik aur reader ne wohi used-car exercise kiya. Yeh waahid sahi answer nahin, magar yeh dikhata hai ke achha kaisa lagta hai.

Error type	AI ki write-up se sentence	Kya ghalat hai
Factual error	"Corolla 47 mpg combined deti hai."	Ghalat number. Asal rating taqreeban 33 mpg hai. Yeh badal deta hai ke aap gas par kitna kharch karein ge.
Logical gap	"Civic ki mileage kam hai, is liye yeh zyada reliable choice hai."	Kam mileage madad karti hai, magar yeh sabit nahin karti ke car reliable hai. Lafz "is liye" isay sabit-shuda dikhata hai jabke yeh nahin.
False confidence	"Dono mein se koi bhi car aik aur decade bina kisi bare repair ke chalegi."	Kisi used car ke bare mein koi yeh waada nahin kar sakta. AI ne isay aik fact ke taur par bayan kiya bina kisi "probably" ya "likely" ke. Yeh aik guess hai jo fact hone ka dhong kar raha hai.
Missing context	(Write-up mein nahin.) 2019 Civic ka aik open airbag safety recall hai.	AI ne is ka kabhi zikr nahin kiya. Safety recall bilkul woh cheez hai jo khareedne se pehle aap ko jaanni chahiye, aur AI ne usay chhod diya.
Fabricated source	"CarReliability Index 2026 rankings ke mutabiq, Corolla 10 mein se 9.4 score karti hai."	Yeh index mojood nahin. AI ne aik aisa source bana liya jo real lagta hai. Agar aap "CarReliability Index" search karein, to kuch nahin milega.
Stale fact	"Dono ab bhi $2,000 state clean-vehicle rebate ke liye qualify karti hain."	Woh rebate 2025 mein khatam ho gaya. Yeh kabhi sach tha magar ab nahin. Yeh us qeemat ko badal deta hai jo aap asal mein dete hain.

Yeh achha kyun hai: Har row mein aik answer hai, aur har quoted sentence wohi hai jo asal mein badal de ke aap kaunsi car khareedte hain. Missing Context row aik specific safety recall ka naam leti hai. Fabricated Source row aik aise index ki taraf ishara karti hai jo mojood nahin.

Yeh kya karne ki koshish nahin karta: sab kuch pakarna. Aap koi poori report nahin likh rahe. Pandrah minutes mein chhe rows goal hai. Teen real catches tees kamzor catches se behtar hain.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

Error Taxonomy is liye kaam karti hai ke insani judgment smooth writing ko aik ajeeb tareeqe se handle karta hai. Jab text parhne mein aasan ho, hum us par zyada trust karte hain, is se qata nazar ke woh sach hai ya nahin. AI bohat smoothly likhti hai, jo usay us bias ka taqreeban perfect trigger banati hai. Chaar findings bataati hain ke named type se scan karna feel se parhne se behtar kyun hai.

Processing fluency (Adam Alter & Daniel Oppenheimer, 2009). Decades ke experiments ka jaaiza le kar, Alter aur Oppenheimer ne dikhaya ke jis aasaani se hum kisi cheez ko process karte hain (saaf type, saadah alfaaz, smooth phrasing) usay dimagh ghalti se is signal ke taur par parh leta hai ke content sach hai. "Yeh achha parha jata hai" wala ehsaas is judgment mein ris jata hai ke "yeh sahi hai," halaanke dono ka aapas mein koi taalluq nahin. AI output ko intihai fluent banane ke liye engineer kiya jata hai, to yeh is lever ko zor se kheenchta hai. Kisi specific error type ke liye scan karna jaadu tor deta hai: aap yeh evaluate karna chhor dete hain ke text kaisa mehsoos hota hai aur yeh check karna shuru karte hain ke koi khaas qism ka claim qaaim rehta hai ya nahin.

Paper parhein (open access): Uniting the Tribes of Fluency to Form a Metacognitive Nation, Personality and Social Psychology Review, 13(3), 2009.

Cognitive ease (Daniel Kahneman, 2011). Kahneman ka framework is mechanism ko aik naam deta hai: jab information bina mehnat ke aati hai, to dimagh ka tez, khudkaar hissa (System 1) usay accept kar leta hai aur slow, checking wala hissa (System 2) kabhi jagta hi nahin. Smooth AI prose System 2 ko soya hua rakhti hai. Chhe-type scan System 2 ko dobara on karne ka aik jaan-boojh kar tareeqa hai: har named check aik aisa kaam hai jo khudkaar dimagh autopilot par nahin kar sakta, jo woh mehnat-talab nazar zabardasti karwata hai jis se fluent text aap ko bahla rahi thi.

Mazeed parhein: Thinking, Fast and Slow (Wikipedia); mutalliqa material cognitive ease wala chapter hai.

Confidence accuracy nahin hai (Nate Silver, 2012). Siyasat, finance, aur sports ke forecasters ka mutaala karte hue, Silver ne aik mustaqil gap document kiya: jo log sab se zyada yaqeeni lagte hain woh aksar sab se kam durust hote hain, kyun ke confidence aur calibration alag skills hain. AI is ka sab se bura hissa virasat mein leti hai, woh taqreeban har cheez usi pur-yaqeen lehje mein bayan karti hai chahe woh sahi ho ya ghar se bana rahi ho. Scan mein "False confidence" wali row theek isi liye mojood hai ke lehje ko sach se alag kare: aap flat, bina-hedge claim ko aik warning sign ke taur par flag karte hain, bajaye is ke ke us ke yaqeen ko evidence samjhein.

Mazeed parhein: The Signal and the Noise (Wikipedia).

Aik mujmal judgment ke bajaye chhe alag checks kyun. Gerd Gigerenzer ka risk par kaam dikhata hai ke kisi masle ko kaise pesh kiya jata hai woh tay karta hai ke log us par achhi tarah reason karte hain ya nahin: aik dhundle judgment ko saaf, concrete tukron mein torein to accuracy barh jati hai, halaanke neeche ke facts nahin badle. "Kya yeh AI output achha hai?" bilkul wohi dhundla, sab-aik-saath judgment hai jis mein log bure hain. Scan isay chhe concrete sawalon mein torta hai jin ka aap aik aik kar ke jawab de sakte hain, isi liye yeh woh ghaltiyan pakarta hai jin ke paas se aik mujmal read guzar jati hai.

Mazeed parhein: Gerd Gigerenzer (Wikipedia), jo Calculated Risks (2002) wali daleel ka khulasa karta hai.

Error Taxonomy chaaron ko jamaa karti hai. Fluent text sach mehsoos hota hai (Alter & Oppenheimer) aur checking wale dimagh ko soya rakhta hai (Kahneman), AI ka yaksaan confidence chhupa deta hai ke kaun se claims asal mein kamzor hain (Silver), aur aik vague "kya yeh theek lagta hai?" ghaltiyan pakarne ke liye ghalat representation hai (Gigerenzer). Chhe error types ko naam dena aur har aik ko check karna chaaron ko aik saath theek kar deta hai. Kisi ne is exact checklist ko khaas tor par AI ke khilaaf test nahin kiya, magar mechanism ka har hissa achhi tarah saabit-shuda hai. Isay AI output par lagana qudrati agla qadam hai.

Go deeper: Part 0 Chapter 2: Detecting Broken Reasoning. Full version (8 mistake types, aik doosri AI ke saath cross-check, aur waqt ke saath apni accuracy track karna; 60-75 min) isay aik mukammal system bana deta hai.

Agar aap ke paas check karne ke liye kaafi knowledge na ho to?

Chhe-type scan tab sab se behtar kaam karta hai jab aap topic jaante hain. Magar un topics ka kya jo aap ke liye naye hain? Teen tarkeebein madad karti hain:

AI se exact source maangein. "studies show" accept na karein. Poochein: "mujhe author ka naam, title, saal, aur kahan publish hua bataayein." Agar AI aap ko koi real source na de sake, to claim par trust na karein.
Bina source ke theek lagne wale numbers par shubha karein. "Sales 47.3% barhi" bohat precise lagta hai. Magar agar AI yeh na bataye ke woh number kahan se aaya, to precision aik warning sign hai, saboot nahin.
Jab aap sure na hon, to usay MODIFY label karein. Agar aap kisi claim ko do minute mein check nahin kar sakte, to usay ACCEPT na karein. MODIFY likhein aur "abhi tak check nahin kiya" add karein. Aap use karne se pehle baad mein look up kar sakte hain.

Discipline 4: Thinking in Systems

Aik university ne kuch in-person tutoring ko AI chatbot se replace kar ke paisa bachane ka decide kiya. Unhon ne AI se poocha, aur AI ne kaha: "Is se tutoring costs par 30% bachat hoti hai." Yeh bohat achha laga, to woh aage barh gaye.

Chhe mahine baad: jo students sab se zyada struggle karte the unhon ne madad ke liye aana band kar diya, kyun ke chatbot un ke sawal samajh nahin pata tha. Un ke grades gir gaye. Parents ne shikayat ki. University ko nuqsaan theek karne ke liye aur tutors hire karne pade, aur aakhir mein yeh original budget se zyada par gaya. "30% bachat" wala answer kaaghaz par sahi tha. Magar chain reaction ne bachat khatam kar di.

Yeh Discipline 4 ka failure mode hai. Jab aap AI se kisi decision ke bare mein poochte hain, to woh us sawal ka jawab deta hai jo aap ne poocha, "is se kitni bachat hogi?", aur wahin ruk jata hai. Woh taqreeban kabhi chain reactions trace nahin karta: Effect A se Effect B hota hai, jis se Effect C, aur kabhi Effect C wapas circle kar ke aap ka original decision undo kar deta hai. Cascade Map woh tareeqa hai jis se aap yeh chain reactions khud trace karte hain, commit karne se pehle, taake surprise kaaghaz par ho na ke aise budget ke chhe mahine andar jo aap wapas nahin le sakte.

Dhyaan dein ke yeh kis ki hifaazat karta hai: kisi auditor ke saamne aap ki saakh ki nahin, balke aap ke apne decision ki. Kisi ne us university ka bure chatbot rollout par audit nahin kiya. University ne bas paisa kharch kiya, nataij ke saath jiya, aur usay theek karne par aur paisa kharch kiya. Cascade map koi defense nahin jo aap baad mein dikhate hain, woh woh thinking hai jo aap ko shuru hi mein woh mehnga move karne se rokti hai.

"Thinking in systems" kyun? System koi bhi aisa parts ka set hai jo aik doosre ko affect karte hain, students, tutors, budgets, aur grades alag-alag facts nahin, woh aik doosre ko dhakelte hain. Hum mein se zyada tar seedhi lakeeron mein reason karte hain: is se woh hota hai, kahani khatam. Magar system ke parts loops mein jure hote hain, to aik effect ghoom kar wapas aa sakta hai aur usi cheez ko badal sakta hai jis ne usay shuru kiya. "Thinking in systems" ka bas itna matlab hai ke pehle effect par rukne se inkaar karna, aap "aur phir kya?" poochte rehte hain jab tak aap woh jagah na dhoond lein jahan lakeer mur kar circle ban jati hai. Cascade Map us aadat ki kaaghazi shakl hai: woh parts bichhata hai, un ke darmiyan lakeerein kheenchta hai, aur woh jagah dhoondta hai jahan koi lakeer wapas loop karti hai.

Aik banane ka tareeqa yeh hai. Pehli dafa is mein taqreeban 20 minutes lagte hain, aur aadat parne par 10 minutes.

Apna decision aik saaf sentence mein likhein. Specific rahein. "shayad tutoring badlein" nahin balke "agle semester se in-person tutoring ke aadhe ghante AI chatbot se replace karein."
Paanch groups list karein jin par yeh decision asar daalta hai. Har bara decision mukhtalif logon par asar daalta hai. Aik achhi shuruaati list: woh log jo kaam kar rahe hain (jaise tutors), woh log jo service use kar rahe hain (jaise students), woh log jo aap se muqabla karte hain (jaise doosri universities), woh qawaneen jo laagu hote hain (jaise university policies), aur woh jo aap ki team jaanti hai ya nahin jaanti (jaise chatbot waqai kitna achha hai?).
Har group ke liye teen baar "aur phir kya?" poochein. Pehli cheez se shuru karein jo hoti hai. Phir poochein ke woh kis taraf le jati hai. Phir poochein us ke baad kya aata hai. Teen layers gehra.
Kam az kam aik loop dhoondein. Aisi jagah dhoondein jahan koi baad wala effect wapas circle kar ke aap ke original decision ko bara (ya behtar) kar de. Specific rahein ke yeh kaise hota hai.
Agar aap ka map saaf aur simple lage, to aap bohat jaldi ruk gaye. Asal risks doosri aur teesri layer mein chhupte hain. Tab tak gehra jayein jab tak yeh messy na lage.

Aik chain banana kaisa mehsoos hota hai. Tutoring decision lein aur sirf group "woh students jo sab se zyada struggle karte hain." Pehli cheez se shuru karein jo hoti hai, phir do baar aur "aur phir kya?" poochein.

Pehli layer: Struggle karne wale students chatbot try karte hain. Woh un ke aadhe-bane sawal samajh nahin pata, to woh haar maan kar madad maangna band kar dete hain.
Aur phir kya? (Doosri layer.) Madad ke baghair un ke grades gir jate hain. Yehi woh students hain jinhein sab se zyada support ki zaroorat thi, aur unhein sab se kam mili.
Aur phir kya? (Teesri layer.) Un mein se kuch aisi university mein transfer ho jate hain jahan ab bhi insaani tutors hain. University un ki tuition kho deti hai.

Woh aakhri link wohi jagah hai jahan surprise rehta hai. Decision tha "tutoring par 30% bachao." Magar teen layer neeche, woh ban jata hai "un students ki tuition revenue khona jinhein hamari sab se zyada zaroorat thi." Aap yeh kabhi AI se "is se kitni bachat hogi?" pooch kar na dekhte, aap isay sirf lagataar teen baar "aur phir kya?" pooch kar dekhte hain.

Ab loop dhoondein: khoyi hui tuition ka matlab aur tight budget, jis ka matlab tutoring ke liye aur kam paisa, jis ka matlab chatbot ko aur zyada cover karna parta hai, jis ka matlab aur zyada struggle karne wale students haar maan jate hain. Original decision khud ko feed karta hai. Yeh loop hai, aur yeh wohi cheez hai jo aik dafa ki 30% bachat ko aik jaari girawat mein badal deti hai.

Cascade Map Steps

Is drawing ko Cascade Map kehte hain. Maqsad mustaqbil ko perfect andaze se predict karna nahin. Maqsad loops ko commit karne se pehle dhoondna hai, jab decision badalna ab bhi muft hai.

Mess kyun matter karta hai

Agar aap ka map saaf aur tidy lagta hai, to aap ne shayad sirf obvious effects likhe. Asal risks gehri layers mein hain. Aage barhte rahein.

Yahan aap aur AI ke ulat blind spots hain, isi liye yeh discipline aik partnership hai. AI us specific sawal ka jawab dene mein achha hai jo aap ne poocha aur un side effects ko notice karne mein bura jo aap ka decision peda karta hai. Aap un logon ke bare mein sochne mein behtar hain jinhein AI bhool gaya aur un chain reactions ke bare mein jo mahinon mein chal kar saamne aati hain. To aap map pehle banate hain, woh hissa jo sirf aap kar sakte hain, aur phir aap AI se keh sakte hain ke woh aap ki banayi har branch stress-test karne mein madad kare.

Aik real decision ke liye, map 20-30 minutes le sakta hai. Neeche wali exercise aik chhota example use karti hai taake aap technique practice kar sakein.

Map dikhata hai kahan dekhna hai; loop dikhata hai kya decision ko undermine karta hai. Mess feature hai, bug nahin.

Diagram ko do passes mein parhein. Upra aadha breadth pass hai: aik decision beech mein ("loan officers ko AI se replace karo"), us ke ird-gird paanch domains, aur har aik ke saath pehli cheez jo hoti hai. In mein se zyada tar woh effects hain jo koi bhi list kar de, employees jobs khote hain, customers ko kharab service milti hai, competitors par aap ki naqal karne ka dabaao aata hai. Jo miss karna aasan hai woh hai Internal knowledge: tacit local lore kho jaana. Loan officers aisi knowledge rakhte hain jo kabhi kisi system mein nahin likhi gayi, kaun se local businesses patle credit file ke bawajood reliable hain, kis ki income mausami hai is liye March mein aik late payment normal hai, kab koi applicant sach nahin bol raha. Officers ko replace karein aur woh knowledge darwaze se bahar chali jati hai, kyun ke woh us software mein kabhi thi hi nahin jis se AI ne seekha.

Neecha aadha depth pass hai, aur isi liye decision ulta padta hai. Customers domain ko aage follow karein: cost cut officers ko hata deti hai, to service gir jati hai (AI un cues ko miss karta hai jo insaan pakar lete the, bilkul wohi lore jo kho gaya), to customers chale jate hain, to revenue bachat se neeche gir jata hai, to bachat gayab ho jati hai. Dashed arrow hi sara point hai: chain wapas shuru tak loop karti hai, yani cost-cutting move apni hi justification mita deta hai. Wohi wapas-circle karna woh cheez hai jis ke liye aap cascade map banate hain, aur yeh tab nazar nahin aata jab aap sirf AI se poochein "is se kitni bachat hogi?"

Yehi discipline aik different decision par.

Aik student council president saalana sports day ko kiraye ke stadium se university ke apne ground par le ja kar paisa bachana chahti thi. AI ne kaha: "Is se event budget ka 40% bachta hai." Faiday zaahir the: koi rental fee nahin, campus ke qareeb, set up karna aasaan. AI ne saare positives list kiye aur aage barhne ki recommendation di.

Idea pesh karne se pehle, us ne aik cascade map banaya. Us ka decision: sports day ko kiraye ke stadium se university ground par le jao taake budget ka 40% bachay. Us ne paanch groups list kiye aur har aik ke liye teen layers trace kiye. Obvious effects mutawaqqa the (paisa bachta hai, students ke liye kam safar, chhota venue). Magar teesri layer ne aik masla zaahir kiya jo us ne socha nahin tha: university ground bohat kam tamaashbeen rakhta hai, to kam families aati, to event chhota mehsoos hota, to woh sponsors jo visibility ke liye paisa dete the agle saal kam dete, to budget simat jata, to event ko phir chhota hona parta. Aik loop, cost-bachat wala move khaamoshi se event ko saal dar saal chhota karta hua.

Cascade Map Example: Sports Day

Oopar wali image us ka poora cascade map dikhati hai: har group ke saath kya hota hai (students, sports teams, food vendors, admin, sponsors), woh loop jo event ko saal dar saal chhota kar deta, aur woh hifaazatein jo us ne usay rokne ke liye add kein, aik guaranteed minimum sponsor package aur commit karne se pehle aik spectator-capacity check. AI ke original answer ("bas isay le jao, paisa bachta hai") mein in mein se koi hifaazat nahin thi. Us ne phir bhi paisa bachaya, magar loop trigger kiye baghair.

Jo cascade map us ne banaya woh khud documented evidence of thinking ka aik tukra hai, wohi cheez jis ke bare mein is page ki shuru wali rule hai. Jab us ne council ke saamne pesh kiya aur kisi ne poocha "kya is se event chhota nahin ho jayega?", to usay moqe par sochna nahin pada. Us ne us loop ki taraf ishara kiya jo woh pehle hi map kar chuki thi aur us hifaazat ki jo woh pehle hi bana chuki thi. Map thinking bhi tha aur us ka evidence bhi.

Khud try karein

Aap ki exercise: Aap ki university ne abhi elaan kiya hai ke agle semester saare exams AI proctoring use karein ge (aik AI exam ke dauran aap ke webcam se aap ko dekhti hai) aur sirf online hon ge. Koi in-person exam nahin.

Aik cascade map banayein paanch groups ke saath: students, professors, IT staff, parents, aur administration. Har group ke liye teen layers gehra jayein. Aik loop dhoondein jahan koi baad wala effect wapas circle kar ke original decision ko bara kar de.

(Ya is week apni life ka koi real decision use karein. Yahi isay stick karwata hai.)

1Your Work

AI grader do cheezen check karega:

Kya aap ne paanchon groups ko teen-teen layers ke saath cover kiya, aur kya aap ne explain kiya ke har effect kaise hota hai (sirf naam nahin)? 1-10 rate karein. Batayein kaunsa group sab se kamzor hai aur main ne kya miss kiya.
Kya aap ka loop cause aur effect ki aik real chain hai, ya sirf aik label? 1-10 rate karein. "Students react karte hain" aik label hai. "Bure internet wale students exams fail karte hain, jis se university ki pass rate girti hai, jis se administration policy par dobara sochti hai" aik real chain hai. Agar mera sirf label hai, to dikhayein isay chain mein kaise badlein.

Mera map dobara na banayein. Agar koi box khaali ya vague ho, bas seedha keh dein.

Aap ka cascade map (decision likhein, phir har group teen layers ke saath list karein. Saaf-suthra hona zaroori nahin):

Decision: Saare exams AI-proctored aur sirf online hon ge. Students: 1st → 2nd → 3rd Professors: 1st → 2nd → 3rd IT staff: 1st → 2nd → 3rd Parents: 1st → 2nd → 3rd Administration: 1st → 2nd → 3rd

Aap ka loop (isay cause aur effect ki aik chain ke taur par likhein):

Misaal: 'Slow internet wale students ko AI proctor cheating ke liye flag kar deta hai. Woh complaints file karte hain. Bohat zyada complaints administration ko manual reviews add karne par majboor karti hain, jo purane in-person exams se zyada mehnga parta hai.'

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Pehli dafa is mein taqreeban 15-20 minutes lagte hain. Pehle chand "aur phir kya?" sawal ajeeb mehsoos hote hain. Yeh normal hai. Asal insights aam tor par teesri layer par dikhte hain, pehli par nahin. Practice ke saath, aap poora map 8-12 minutes mein kar sakte hain.

Score milne ke baad, aik aisa group dhoondein jo AI grader ne mention kiya aur aap bhool gaye. Wahi aap ka blind spot hai. Agar AI ne koi loop dhoonda jo aap ne miss kiya, to us par khaas tawajjo dein. Loops sab se aham cheez hain kyun ke woh aap ko batate hain ke koi decision waqt ke saath kab ulta padega.

Aap ne jo abhi kiya woh trace karne mein madad deta hai ke kisi decision ke baad kya hota hai. Lekin yeh check nahin karta ke decision shuru hi mein sahi information par khara hai ya nahin.

Aik ghalat assumption par bana hua perfectly mapped plan phir bhi fail hota hai. Woh bas baad mein fail hota hai, behtar notes ke saath. Yeh Discipline 5 ka kaam hai.

Good example dekhna chahte hain? (Apna submit karne ke baad isay kholein.)

Aik aur student ne wohi AI-proctored exam exercise kiya. Yeh waahid sahi answer nahin, magar yeh dikhata hai ke achha cascade map kaisa lagta hai.

Decision: Agle semester saare exams AI-proctored aur sirf online hon ge.

Group	Pehle kya hota hai	Us se kya hota hai	Us se PHIR kya hota hai
Students	Slow internet ya purane laptops wale students struggle karte hain	Kuch ko AI proctor ghalti se "cheating" ke liye flag kar deta hai	Woh students appeals file karte hain; exam system par bharosa girta hai
Professors	Professors exam ke dauran students ko dekh nahin sakte	Woh bata nahin sakte ke koi student confused hai ya atka hua	Professors exams ko chhota aur saadah bana dete hain, jis se standard girta hai
IT staff	IT ko proctoring software set up aur support karni parti hai	Exam week mein students musalsal tech problems ke saath IT ko call karte hain	IT par bojh barh jata hai; campus par sab ke liye response times kharab ho jate hain
Parents	Parents privacy ki fikr karte hain (webcam recording)	Kuch parents shikayat ke liye administration se rabta karte hain	University ko nayi privacy policies likhni parti hain, jis mein mahine lagte hain
Administration	Administration exam halls par paisa bachati hai	Magar woh proctoring software licenses par paisa kharch karti hai	Cost savings tawaqqo se chhoti nikalti hai

Loop: Bure internet wale students ko cheating ke liye flag kiya jata hai, woh complaints file karte hain, administration ko har complaint manually review karne ke liye log hire karne parte hain, yeh exam halls book karne se zyada mehnga parta hai, administration in-person exams par wapas jaane par ghor karti hai, original decision palat jata hai.

Yeh achha kyun hai: Paanchon groups teen-teen layers ke saath cover hue hain. Har effect explain karta hai ke woh kaise hota hai, sirf yeh nahin ke kya hota hai. Loop aik real chain hai: yeh aik student masle se shuru hoti hai aur original decision ko undo kar ke khatam hoti hai.

Yeh kya karne ki koshish nahin karta: har mumkin effect list karna. Is scenario mein aur bhi loops hain (professors ka naukri chhorna, students ka transfer hona). Point aik real loop dhoondna hai cause aur effect ki saaf chain ke saath, pehli koshish mein sab dhoondna nahin.

Agar aap ka map is se zyada tidy lagta hai, to yahi signal hai: apne do sab se kamzor domains mein aik aur "aur phir kya?" gehra jayein aur loop dobara dhoondein.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

Cascade Map koi nayi idea nahin, yeh system dynamics ki aik simplified shakl hai, aik aisa shoba jo sattar saal se aik zidi haqeeqat document kar raha hai: log seedhi lakeeron mein reason karte hain, magar duniya loops par chalti hai. Teen tehqeeqi silsile bataate hain ke map banana usay dimagh mein soch lene se behtar kyun hai.

Demand amplification (Jay Forrester, 1958). Forrester ne, jis ne MIT mein system dynamics ki bunyaad rakhi, dikhaya ke chain mein aik nuqte par liya gaya decision bahar ki taraf phailta hai aur distorted ho kar wapas aata hai. Us ki sab se mashhoor misaal woh hai jise ab bullwhip effect kehte hain: retail wale sire par customer demand mein aik chhota, mustaqil sa farq upstream factory orders mein zabardast jhoolay peda karta hai, kyun ke har link apne saath wale link par react karta hai bina poora loop dekhe. Sabaq supply chains se kahin aage tak jata hai: jab aap seedhi-lakeer ki zubaan mein decide karte hain ("is se 30% bachat hoti hai"), to aap woh tareeqa miss kar dete hain jis se effect system ke andar safar karta hai aur badal kar wapas aata hai. Cascade Map woh tool hai jo wapsi ka safar commit karne se pehle nazar aane wala bana deta hai.

Mazeed parhein: Bullwhip effect (Wikipedia), jo is idea ko Forrester ke "Industrial Dynamics: A Major Breakthrough for Decision Makers," Harvard Business Review, 36(4), 1958 tak le jata hai.

Misperception of feedback (John Sterman, Beer Game). Sterman ne ab aik classic ban chuka experiment chalaya, beer distribution game, jis mein khilari aik saadah supply chain ka aik link manage karte hain. Zaheen, pur-josh participants bhi, MBA students, executives, bharose ke saath bare, mehnge oscillations peda karte hain, kyun ke woh us par react karte hain jo un ke saamne hai aur system ki un delays aur feedback loops ko nazar-andaaz karte hain jo woh dekh nahin sakte. Failure mehnat ya zehanat ki kami nahin; baat yeh hai ke loops tab tak invisible rehte hain jab tak koi cheez aap ko unhein bichhane par majboor na kare. Wohi "koi cheez" theek wohi hai jo Cascade Map faraham karta hai: us majboor drawing ka aik paanch-minute, kam-risk version jo loop ko us se pehle nazar aane wala bana deta hai ke woh aap ko kuch cost kare.

Mazeed parhein: Beer distribution game (Wikipedia). Poora bayan Sterman ki Business Dynamics: Systems Thinking and Modeling for a Complex World (McGraw-Hill, 2000) mein hai.

Leverage points (Donella Meadows, 2008). Meadows ne, jo usi MIT rivayat mein kaam karti thi, apna career yeh daleel dete guzara ke kisi system ko badalne ki sab se taqatwar jagahein taqreeban kabhi obvious nahin hotin. Sab se bara leverage aam tor par feedback loops mein hota hai, wohi structures jin ka seedhi-lakeer wala analysis kabhi naam nahin leta. Us ka do-took nateeja: aap us loop ko adjust, kamzor, ya us se hifaazat nahin kar sakte jise aap ne banaya hi nahin. Cascade Map ka poora kaam kam az kam aik loop ko samne laana hai, kyun ke woh loop chhupa hua risk bhi hai aur intervene karne ki sab se zyada leverage wali jagah bhi.

Mazeed parhein: Meadows ka mazmoon Leverage Points: Places to Intervene in a System, jo us ki kitab Thinking in Systems (Chelsea Green, 2008) ki bunyaad bana.

Cascade Map teeno ko jamaa karta hai. Decisions system ke andar safar karte hain aur distorted ho kar wapas aate hain (Forrester), log un wapsi safron ko bharose ke saath miss karte hain jab tak unhein banane par majboor na kiya jaye (Sterman), aur jo loops woh miss karte hain wohi act karne ki sab se zyada leverage wali jagahein hain (Meadows). Map woh majboor drawing hai jo loop ko us waqt pakar leta hai jab decision badalna ab bhi muft hai. Kisi ne Cascade Map ko khaas tor par AI ke khilaaf test nahin kiya, magar buniyaadi finding, ke insaan feedback loops miss karte hain aur unhein bahar nikaalna isay theek kar deta hai, is shobe ke sab se zyada dohraye gaye nataij mein se hai. AI-era ka mor sirf yeh hai ke ab aap ke paas aik aisa partner hai jis ka blind spot ulta hai: AI us breadth par mazboot hai jo aap bhool jate aur un loops par kamzor jinhein mehsoos karne ke liye aap bane hain, to map mil kar banana dono gaps ko aik saath band kar deta hai.

Go deeper: Part 0 Chapter 3: Thinking in Systems. Full version (peer review plus AI counter-analysis plus assessment rubric; 60 minutes) isay aik system bana deta hai.

Part 3: Origination (jo AI nahin kar sakti woh karna)

Part 1 ne aap ko AI se poochne se pehle sochna sikhaya. Part 2 ne AI ke answers mein mistakes spot karna sikhaya. Part 3 aik different cheez hai: woh thinking karna jo AI aap ke liye nahin kar sakti.

AI ki yahan do bari blind spots hain. Pehli, woh aap ko sab se common answer deti hai, aap ki situation ke liye best answer nahin. Agar 1,000 logon ne same question poocha ho, AI un sab ka average answer deti hai. Lekin aap ki situation different ho sakti hai. Doosri, jitna zyada aap AI use karte hain, utna easy hai apni thinking rok kar jo woh kahe accept kar lena.

Disciplines 5 aur 6 dono problems fix karte hain.

Start karne se pehle aik important phrase seekhein: named threshold. Named threshold aik specific condition hoti hai jo batati hai ke advice kab kaam karna band karti hai. Example: "yeh advice tab kaam karti hai jab aap ki class mein 30 se kam students hon" named threshold hai. "Yeh sometimes kaam karti hai" threshold nahin, kyun ke "sometimes" nahin batata kab. Aap is phrase ko aik minute mein use karein ge.

Discipline 5: First Principles

Aap apni university ke coding club ki president hain. Campus ke har doosre club ne abhi membership fees charge karna shuru kar diya hai. Aap ki vice president, aap ka faculty advisor, aur do senior members sab wohi kehte hain: "Humein bhi fees charge karni chahiye, baqi sab kar rahe hain." Aap AI se poochti hain. AI agree karta hai. Sab aik hi taraf ishara kar rahe hain.

Wohi agreement khatra hai. Jab sab aik hi answer ke peeche aa jate hain, AI samait, to yeh settled lagta hai, aur sochna chhor kar saath chalna aasan ho jata hai. Lekin common answer us par bana hai jo zyada tar clubs ke liye kaam karta hai. Aap ka club exception ho sakta hai, aur kamre mein koi yeh check nahin kar raha ke woh hai ya nahin. Yeh discipline woh tareeqa hai jis se aap check karte hain.

Check ki aik khaas shakl hoti hai: aap common advice lete hain aur woh theek condition dhoondte hain jahan woh kaam karna band karti hai. Zyada tar log, jab advice par shak karte hain, aik vague complaint banate hain: "fees charge karna hamesha achha idea nahin." Yeh bekaar hai, kyun ke "hamesha nahin" kabhi nahin batata kab. Skill vague complaint ko aik named threshold mein badalna hai: aik specific, numbered condition jahan advice toot-ti hai.

"First principles" kyun? First principles se reason karne ka matlab hai kisi answer ko sirf is liye accept karne se inkaar karna ke sab usay dohrate hain, aur us ke bajaye yeh nikalna ke aap ki situation ke liye asal mein kya sach hai. Aam tor par log isay scratch se answer banana samajhte hain. Yeh discipline halka, tez version karti hai: advice ko dobara banane ke bajaye, aap usay test karte hain, aap woh theek conditions dhoondte hain jahan common answer aap ke liye sach hona band ho jata hai. Wohi buniyaadi move (consensus ko authority par na lein; usay apne case ke against check karein), blank page ke bajaye boundary par nishana lagaye hue.

Move aik baar dekhein. Wohi situation, advice par shak karne ke do tareeqe:

Vague complaint: "Fees charge karna hamesha achha idea nahin."
Named threshold: "Jab aap ke club ka main goal aise first-year students ko attract karna hai jinhon ne kabhi code nahin kiya, aur un mein se aksar fee afford nahin kar sakte, to paisa charge karna theek un logon ko dara dega jinhein aap reach karna chahti hain."

Pehla aik shrug hai. Doosra aap ko theek theek batata hai ke advice kab fail hoti hai (first-years jo afford nahin kar sakte) aur kyun (fee un logon ko rok deti hai jin tak pohanchne ke liye club mojood hai). Pehla kuch nahin badalta. Doosra aap ka decision badal deta hai. Wohi gap, aik shrug aur aik named condition ke darmiyan, poori discipline hai.

Practice aise karein. Koi common advice choose karein jo aap ke around sab log, aur AI, follow karne ko keh rahe hain. Phir teen rows likhein. Har row mein specific situation describe karein jahan advice kaam nahin kare gi. Real number ya real condition use karein, sirf "sometimes" nahin.

Common advice	Yeh kab kaam karna band karti hai? (specific number ya condition use karein.)

Agar aap teen rows specific conditions ke saath fill nahin kar sakte, to aap advice follow kar rahe thay magar usay samajh nahin rahe thay.

Row achhi hai ya nahin kaise pehchanein: "Jab aap ke club mein 80% se zyada first-year members hon jin ki income nahin, fees charge karna membership aadhi kar dega" useful hai. Yeh exactly batata hai advice kab break hoti hai. "Fees charge karna hamesha kaam nahin karta" decision ke liye bohat vague hai.

Dhyaan dein ke yeh kis ki hifaazat karta hai. Kisi ne club president ka fees charge karne par audit nahin karna tha, poora kamra, plus AI, is par mutafiq tha ke yeh sahi move hai. Agar woh consensus follow kar leti, to woh bas aik buri decision le leti, membership girti dekhti, aur kabhi na jaanti ke named threshold hi wajah thi. Threshold koi cheez nahin jo aap baad mein khud ko defend karne ke liye banate hain. Yeh woh cheez hai jo aik buri decision ko us waqt pakar leti hai jab aap ke ird-gird sab abhi sar hila rahe hote hain.

Boundary Conditions: From Vague Complaints to Named Thresholds

Good result kaisa dikhta hai.

Upar wali coding club president ne pehli try mein teen perfect rows nahin likheen. Sochne ke baad us ke paas yeh tha:

Common advice: "Har club ko membership fees charge karni chahiye."
Boundary 1. Jab aap ke members mein 80% se zyada first-year students hon jin ki income nahin, fees charge karna exactly un logon ko dara dega jinhein aap reach karna chahte hain. Threshold: 80% first-year, no-income members.
Boundary 2. Jab aap ke club ki main value free workshops hain jahan koi bhi aa sakta hai, fee lagana barrier banata hai jo walk-in attendance maar deta hai. Yeh sab se zyada tab matter karta hai jab campus par 3 ya zyada competing clubs abhi bhi free hon. Threshold: same campus par 3+ free competing clubs.
Boundary 3. Jab aap ke club ka zyada budget university grant se aata ho jisme all students ke liye open rehne ki requirement ho, fees charge karna grant khulwa sakta hai. Threshold: "open access" requirement wali grant jo budget ka half se zyada cover karti hai.

Us ne teen boundaries faculty advisor ko dikhain. Unhon ne club free rakha aur sponsored hackathons se paisa raise karne ka decide kiya. Semester ke end tak membership 40% grow hui, jab ke fees charge karne wale doosre clubs mein attendance drop hui. Teenon boundaries common advice mein nahin thin. AI ke first answer mein bhi nahin.

Woh teen boundaries bhi documented evidence of thinking ka aik tukra hain, wohi cheez jis ke bare mein is page ki shuru wali rule hai. Jab president apne advisor ke saath baithi, us ne yeh nahin kaha "mujhe fees ke bare mein aik bura ehsaas hai." Us ne teen named conditions mez par rakhin. Aik ehsaas aur teen named thresholds ka farq overrule hone aur suni jaane ka farq hai. Rows us ki thinking bhi thin aur is ka saboot bhi ke us ne woh ki.

Named thresholds ke baghair woh kuch aisa likhti:

Common advice: "Har club ko membership fees charge karni chahiye."	Yeh help kyun nahin karta
Kabhi-kabhi fees charge karna good idea nahin hota.	Bohat vague. "Kabhi-kabhi" nahin batata kab. Yeh 5% members leave karne par ho sakta hai ya 90% par. Decision mein help nahin karta.
Doosre clubs hamesha nahin jaante woh kya kar rahe hain.	Yeh doosre clubs par complaint hai, aap ke decision ki reason nahin. Kuch change nahin karta.
Situation par depend karta hai.	"Depend karta hai" kehna, baghair bataye kis par, help nahin karta. Sab ko pehle se pata hai situation matter karti hai.

Khud try karein

Aap ki exercise: Koi bhi common advice choose karein jo log aap ko baar-baar batate hain. Examples: "follow your passion," "hamesha group mein study karo," "har paycheck ka 20% save karo," "lectures skip na karo." Teen rows likhein. Har row mein specific situation, number ya condition ke saath, name karein jahan advice kaam karna band karti hai.

(Aap koi bhi advice choose karein, move same rehta hai.)

Start karne se pehle yaad rakhein: Threshold specific number ya condition use karta hai ("jab aap ki class mein 200 se zyada students hon"). "Sometimes," "often," aur "it depends" thresholds nahin.

Agar third row nahin aa rahi, to iska matlab hai aap advice follow kar rahe thay magar usay samajh nahin rahe thay. Weak third row force karne ke bajaye different advice choose karein. Yeh khud useful discovery hai.

1Your Work

AI yeh check karega:

Kya har row mein specific threshold hai (number, condition, clear situation)? 1-10 rate karega. Weakest row quote karega.
Kya har row explain karti hai kyun advice us situation mein fail hoti hai, ya sirf kehti hai "kaam nahin karti"? 1-10 rate karega. Koi row vague complaint ho to point out karega.

Meri rows rewrite na karein. Agar row empty ya vague ho to seedha kahe.

Main jis common advice ko examine kar raha hoon:

Example: 'hamesha group mein study karo.'

Row 1: Yeh advice kab kaam karna band karti hai? (Specific condition name karein aur why explain karein.)

Jab [number ya condition wali specific situation] ho, yeh advice fail hoti hai kyun ke [reason].

Row 2:

Jab [number ya condition wali specific situation] ho, yeh advice fail hoti hai kyun ke [reason].

Row 3:

Jab [number ya condition wali specific situation] ho, yeh advice fail hoti hai kyun ke [reason].

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Pehli dafa is mein lagbhag 15-25 minutes lagte hain. Thresholds expectation se hard hotay hain. Score milne ke baad koi row dekhein jahan aap ne "sometimes" ya "it depends" likha ho aur usay real number ya condition se rewrite karein. Agar rewrite nahin kar sakte to woh row shayad real boundary nahin. Usay drop karein aur different one try karein.

Aap ne abhi advice ke aik piece ki boundary dhoondi. Lekin yeh un problems par AI ke saath kaam karna nahin sikhata jahan challenge karne ke liye obvious advice nahin hoti. Woh Discipline 6 ka kaam hai.

Good example dekhna hai? (Apna submit karne ke baad kholein.)

Aik student ne advice choose ki: "hamesha group mein study karo." Us ki teen rows yeh thin:

Common advice: "Hamesha group mein study karo."
Row 1. 5 people se bare groups theek kaam nahin karte. Zyada log bas baith kar sunte hain, jab ke 2-3 log real work karte hain. Jab break hoti hai: 5 people se zyada.
Row 2. Kuch subjects quiet focus chahte hain, jaise math problems solve karna ya essays likhna. Group mein har kuch minutes koi interrupt karta hai. Jab break hoti hai: aisi tasks jinhein 30 minutes se zyada quiet thinking chahiye.
Row 3. Jab aik person sab se bohat zyada jaanta hai, woh poora time explain karta rehta hai, study nahin kar pata. Us ka apna work peeche reh jata hai. Jab break hoti hai: jab best aur weakest student ke beech 2 grade levels se zyada gap ho.

Yeh achha kyun hai: Har row specific number use karti hai (5 people, 30 minutes, 2 grade levels). Har row explain karti hai advice why fail hoti hai, sirf fail nahin kehti.

Teen clear rows enough hain. Har possible situation list karne ki zaroorat nahin.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

First Principles move, common advice jahan aap ke liye sach hona band ho jati hai woh theek condition dhoondna, teen purane ideas par tikti hai ke advice kyun fail hoti hai aur usay kaise test karein.

Ecological rationality (Gerd Gigerenzer, Peter Todd & ABC Research Group, 1999). Un ki buniyaadi finding aik chhoti si equation mein hai: heuristic + environment = outcome. Koi rule of thumb apne aap mein kabhi achha ya bura nahin hota, woh un environments mein achha hai jin mein woh fit hota hai aur un mein bura jin mein nahin, aur poori skill yeh jaanna hai ke aap kis environment mein hain. "Membership fees charge karo" aik heuristic hai jo aise clubs ke liye tuned hai jin ke members pay kar sakte hain; isay aise first-years ke club mein daal dein jin ki koi income nahin aur wohi rule ulta padta hai. Named threshold bas aap ka theek theek bayan karna hai ke woh environment kaunsa hai jahan advice fit hona band ho jati hai, aur yeh bilkul wohi judgment hai jise yeh tehqeeq achhi decisions ko buri se alag karne wali kehti hai.

Mazeed parhein: Ecological rationality (Wikipedia), jo Gigerenzer, Todd & ABC Research Group ki Simple Heuristics That Make Us Smart (Oxford University Press, 1999) ka khulasa karta hai.

Recognition-primed decisions (Gary Klein, 1998). Firefighters, nurses, aur dabaao mein doosre experts ka mutaala karte hue, Klein ne paaya ke woh shaaz hi options tolte hain, woh aik situation ko familiar pehchaante hain aur pehla pattern chala dete hain jo fit hota hai, aam tor par yeh notice kiye baghair ke unhon ne aisa kiya. Yeh tez aur aksar sahi hai, magar yeh bilkul wohi tareeqa bhi hai jis se consensus advice bina jaanche nikal jati hai: woh aik pehchaane, settled answer ki tarah mehsoos hoti hai. Khud ko yeh likhne par majboor karna ke pattern kab fail hoga woh jaan-boojh kar pause hai jo khudkaar match ko rok deta hai, aap itni der ke liye pattern-matching rok dete hain ke check kar sakein ke aap ka case exception hai ya nahin.

Mazeed parhein: Recognition-primed decision (Wikipedia); poora bayan Klein ki Sources of Power: How People Make Decisions (MIT Press, 1998) mein hai.

Falsifiability (Karl Popper, 1959). Popper ne daleel di ke koi claim aap ko duniya ke bare mein tabhi kuch batati hai jab aap bata sakein ke kya cheez usay ghalat sabit karegi. Aisa aqeedah jo har mumkin nateeje mein zinda rehta hai kuch explain nahin karta. Named threshold advice par lagaya gaya falsifiability test hai: "yeh kaam karti hai jab tak 80% se zyada members fee afford na kar sakein" woh theek condition name karta hai jis ke tehat aap advice chhor dein ge. Aik vague complaint, "yeh hamesha kaam nahin karti," koi condition name nahin karti, kabhi check nahin ho sakti, aur is liye kuch nahin badalti. Yahi threshold aur shrug ka farq hai.

Mazeed parhein: Falsifiability (Wikipedia), woh idea jo Popper ne The Logic of Scientific Discovery (1959) mein pesh kiya.

First Principles teeno ko jamaa karti hai. Advice sirf usi environment ke liye sahi hoti hai jis mein woh fit hoti hai (Gigerenzer & Todd), consensus aap ke paas se is liye nikal jata hai ke aik "settled" answer pehchanna khudkaar hai (Klein), aur ilaaj yeh hai ke woh theek condition name karein jo advice ko aap ke liye ghalat sabit kare (Popper). Aik named threshold teeno aik saath karta hai: woh environment bayan karta hai, khudkaar match ko rokta hai, aur itna specific hai ke check ho sake. Kisi ne is exact exercise ko AI ke khilaaf test nahin kiya, magar buniyaadi ideas decades se qaaim hain. Unhein AI ke confident consensus answers ko pressure-test karne ke liye istemaal karna qudrati agla qadam hai.

Go deeper: Part 0 Chapter 4: Reasoning from First Principles. Full version (Blank Page Sprint: jis practice ko aap follow kar rahe hain us ke against 500 words, phir structured AI counter-analysis aur peer review, 60 min) Part 0 mein hai. Yeh page row shape sikhata hai. Woh page longform argument sikhata hai.

Discipline 6: Working WITH AI

Aap ne subah AI ke saath important essay par kaam karte hue guzari. Result great lagta hai. Arguments clear hain aur writing polished hai. Phir professor poochta hai: "Is mein kaun se parts aap ke ideas hain aur kaun se AI se aaye?" Aap bolne lagte hain aur realise karte hain ke bata nahin sakte. Kuch sentences aap ke hain. Kuch AI ke. Zyada tar mix hai. Essay good hai. Bas aap nahin jaante kaun se parts actually explain aur defend kar sakte hain.

Fix yeh hai. Same task ko teen different ways karein, phir results side by side compare karein.

Solo. 15 minutes, no AI. Sirf aap aur problem.
AI-only. 5 minutes. AI se poochhein, first answer accept karein, kuch change na karein.
Collaborative. 10 minutes. AI se poochhein, critically parhein, zaroorat ho to disagree karein, follow-up questions poochhein, parts khud rewrite karein.

Phir teenon versions compare karein. Khud se poochhein: kaunsa version best hai? "Together" version ke kaun se parts behtar hain kyun ke aap ne push back kiya? Together version aksar jeetta hai, lekin real lesson yeh dekhna hai ke exactly kahan aap ki thinking ne usay better banaya. Yeh discipline isi ke bare mein hai.

Comparison kaisa mehsoos hota hai. Farz karein aap ka task professor ko email ki aakhri line hai. Teenon versions aik doosre ke saath rakhein aur sirf woh aik line parhein:

Solo: "Thanks, and sorry again for the trouble." (Maafi-talab, thora weak.)
AI-only: "Thank you for your time and consideration." (Polished, magar yeh kisi bhi banday ki koi bhi email ho sakti hai.)
Collaborative: "I can show you what I have so far if that helps." (Aap ka, yeh sabit karta hai ke aap pehle hi kaam shuru kar chuke hain.)

Unhein saath saath parhna hi sara move hai. Solo line dikhati hai jo aap akele likhte. AI-only line dikhati hai AI ka default kya hai. Aur Collaborative line woh hai jise aap defend kar sakte hain, kyun ke aap jaante hain ke woh baqi do se behtar kyun hai: woh aik aisa kaam karti hai jo baqi do mein se koi nahin karti. Aap ne sirf mehsoos nahin kiya ke collaborative version behtar tha, aap line ki taraf ishara kar ke bata sakte hain ke woh kya karti hai. Wohi ishara karna skill hai.

Real project ke liye full comparison lagbhag 30 minutes leta hai. Neeche quick 10-minute version hai taake aap aaj difference feel kar sakein.

Three-Path Comparison

Real example mein yeh kaisa dikhta hai.

Aik student ko professor ko email likhni thi jisme major assignment ke liye deadline extension maangni thi. Reason real tha (family emergency), lekin email honest bhi honi thi aur excuse jaisi bhi nahin lagni thi. Us ne teenon paths try karne ka decide kiya.

Solo, 15 minutes. Us ne email khud likhi, no AI. Woh honest aur personal thi. Us ne apni situation clearly explain ki. Lekin woh ramble kar gayi, aur actual request ("kya mujhe 5 aur days mil sakte hain?") bottom mein buried thi. Email bohat long thi aur professor shayad end tak na parhta.

AI-only, 5 minutes. Us ne AI ko situation di aur first draft baghair change accept kiya. Email polished aur well-structured thi. Lekin generic lagi, jaise template jo koi bhi bhej sakta tha. Us mein specific situation ki details nahin thin. Woh us jaisi nahin lagi. Professor shayad sochta ke us ne AI email copy ki hai.

Collaborative, 10 minutes. Us ne opening khud likhi, apni specific situation apne words mein, phir AI se email restructure karne mein help maangi taake request pehle aaye. AI ne tone soften karne ko kaha; us ne disagree kiya aur direct wording rakhi kyun ke woh jaanti thi professor politeness se zyada honesty prefer karte hain. Us ne AI se closing line bhi maangi; AI ki version bohat formal thi, to us ne usay apni awaaz mein rewrite kiya. Final email clear, personal, aur well-structured thi. Professor ne aik hour mein reply kiya aur extension de di.

Collaborative version do specific cheezon ki wajah se jeeti: us ne apni direct wording rakhi, jise AI soften karna chahta tha, aur request top par rakhi, jo woh khud nahin sochti. Woh exactly point kar sakti hai ke us ke judgment ne email kahan better banayi.

Woh aakhri sentence is page ki shuru wali rule se juri hai. Teen versions saath saath rakhe hue khud thinking ka documented evidence hain. Win yeh nahin ke "email achhi thi." Bohat si AI-only emails achhi hoti hain. Win yeh hai ke woh line by line dikha sakti hai ke us ke judgment ne result kahan badla, aur yehi woh cheez hai jo professor ka sawal ("kaun se parts aap ke hain?") asal mein pooch raha tha. Yeh bhi notice karein ke payoff is par depend nahin karta tha ke professor kabhi poochta. Agar koi sawal na bhi karta, comparison ne us ki email ko baqi dono paths se waqai behtar bana diya. Audit bas us value ko visible karta hai jo waise bhi mojood thi.

Aap ko sirf Collaborative nahin, teenon versions kyun chahiye:

Solo version ke baghair, aap ko pata nahin chalta ke aap khud kya likhte. Is liye final email mein yeh nahin bata sakte ke kaun se ideas aap ke hain aur kaun se AI se aaye.
Teenon compare kiye baghair, aap prove nahin kar sakte ke Collaborative version actually better hai. Agar koi poochhe aap ne yeh version kyun choose kiya, "it feels better" real answer nahin.
AI-only version ke baghair, aap nahin bata sakte ke aap ne bas AI ki har baat accept kar li ya nahin. Agar Collaborative aur AI-only versions lagbhag same dikhein, to aap ne collaborate nahin kiya. Copy kiya.

Isay kab use karein aur kab skip karein

Isay us work par use karein jahan aap ka personal experience matter karta hai: emails jinhein aap ki awaaz chahiye, decisions jahan AI aap ki situation nahin jaanta, creative work jise aap ke ideas chahiye. Simple tasks jahan AI apne aap theek karta hai, jaise table format karna ya notes summarize karna, wahan AI ko karne dein. Is exercise ko un tasks par waste na karein jinhein aap ke judgment ki zaroorat nahin.

Khud try karein

Yahan se start karein: Landlord ko rent reduction maangte hue message likhein, ya professor ko deadline extension request karein. Kuch aisa jahan aap ke paas context hai jo AI ke paas nahin: aap ki payment history, us person se relationship, specific situation.

Workplace version: Aap ka boss aap se one-page memo maangta hai: kya company ko smaller competitor khareedna chahiye? Competitor mein 90 people hain aur woh fast grow kar raha tha, jab last quarter us ne apna biggest customer lose kiya (jo revenue ka 22% tha). Woh $40-55M mein bought hone ke liye open hain. Aap ki recommendation next three years tak quote hogi.

Kisi bhi option ke liye, teenon versions karein: Solo (5 min), AI-only (3 min), Collaborative (5 min). Teenon side by side rakhein. Point memo nahin. Point teen paths ke beech felt difference hai.

(Ya apne desk par is week ka koi real decision choose karein. Jitna real ho, comparison utna sharp hota hai.)

AI-only draft skip na karein. Yeh drop karna sab se tempting hai ("I already know what AI would say") aur sab se diagnostic bhi. Agar Collaborative AI-only ke bohat close ho jaye, to aap ne over-accept kiya. Yeh sirf dono likhne se seekhte hain.

1Your Work

AI yeh check karega:

Kya aap ke teen versions waqai different hain, ya sab same baat kehte hain? 1-10 rate karega. Agar Solo aur Collaborative versions lagbhag identical dikhein, to seedha kahega.
Kya aap ke teen overrides specific hain? 1-10 rate karega. Har override aisi cheez honi chahiye jis par aap point kar ke keh sakein "is ke baghair email worse hoti." Agar koi override vague ho, jaise "I made it better," to seedha kahega.

Mera work rewrite na karein. Agar box empty ya vague ho to seedha kahe.

Aap ke teen versions describe karein (kya likha, kya surprise hua, kahan short pada):

Solo (15 min, no AI): maine likha... | AI-only (5 min): AI ne likha... | Collaborative (10 min): maine AI use kiya lekin badla...

Collaborative version mein teen specific cheezein name karein jo aap ne badli ya add ki:

1. Maine badla... kyun ke... | 2. Maine add kiya... kyun ke... | 3. Maine AI se disagree kiya... kyun ke...

Actually kaunsa version send karein ge, aur kyun?

Solo / AI-only / Collaborative. Aik sentence explaining why.

2Get Your Score

Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.

Yeh thinking time samait lagbhag 15 minutes leta hai. Score ke baad dekhein AI grader kahan kehta hai Solo version kisi cheez mein better tha. Yeh batata hai Collaborative version kahan AI par zyada rely kar gaya.

Aap ne abhi poora crash course aik exercise mein kiya. Aap ne AI se pehle apni opinion banai (Discipline 1). Aap ne track kiya kya agree aur disagree kiya (Discipline 2). Aap ne mistakes check ki (Discipline 3). Aap ne socha aage kya hoga (Discipline 4). Aap ne test kiya common advice kahan break hoti hai (Discipline 5). Aur jab AI take over karna chahta tha, aap ne apna judgment rakha (Discipline 6). Point answer nahin tha. Point yeh tha ke aap dikha sakein answer tak pohanchne ke liye aap ne kaise socha.

Good example dekhna hai? (Apna submit karne ke baad kholein.)

Aik student ne professor ko deadline extension maangte hue email likhi. Har version aisa dikha:

Version	Us ne kya likha
Solo (15 min)	Honest aur personal. Family situation clearly explain ki. Lekin bohat long thi, aur actual request ("kya mujhe 5 aur days mil sakte hain?") bottom mein buried thi. Usay pata tha restructure chahiye, lekin time khatam ho gaya.
AI-only (5 min)	Short aur well-organized. Lekin template jaisi lagi. Is mein "I would greatly appreciate your consideration" jaisi phrases thin jo woh real life mein kabhi nahin kehti. Course ya professor ki koi specific detail nahin thi.
Collaborative (10 min)	Us ne opening apne words mein likhi, phir AI se request top par rakhne mein help maangi. AI ne tone softer banane ko kaha; us ne direct wording rakhi kyun ke woh jaanti hai professor honesty pasand karte hain. Us ne AI ki suggested structure use ki, lekin closing apni sentence se replace ki.

Collaborative version mein us ne teen cheezein badli:

Apna direct tone rakha. AI ne zyada formal banane ki koshish ki ("I would be grateful for your understanding"). Us ne original wording rakhi ("I need 5 more days") kyun ke professor ne kaha tha unhein point par aane wale students pasand hain. Is ke baghair email har AI-written extension request jaisi lagti.
Request first line mein move ki. Woh khud yeh nahin sochti. AI ne suggest kiya. Yeh Solo version par sab se bara improvement tha.
AI ki closing line replace ki. AI ne likha "Thank you for your time and consideration." Us ne replace kiya: "I can show you what I have so far if that helps." Is se dikhaya ke us ne work already start kar diya hai. Is ke baghair email generic line par khatam hoti.

Yeh achha kyun hai: Har override aisi cheez par point karta hai jo usay pata thi aur AI ko nahin: professor ki directness preference, aur fact ke us ne work already start kar diya tha. Woh exactly keh sakti hai us ke judgment ne email kahan better banayi. Yahi test hai.

Yeh kyun kaam karta hai (research jo is ke peeche hai)

Jis pattern par yeh exercise bani hai, ke human plus AI dono mein se kisi akele ko beat karta hai, magar sirf tab jab human decisions apne paas rakhta hai, woh AI productivity research ki sab se mustaqil findings mein se hai. Teen kaam isay teen zaviyon se samjhate hain.

Human + machine teaming (Garry Kasparov, "centaur" chess par). 1997 mein IBM ke Deep Blue se haarne ke baad, Kasparov ne yeh nateeja nahin nikala ke machines bas jeet gayi. Us ne advanced chess ko aam kiya, jahan aik human aik computer ke saath khelta hai. Us ke baad ke freestyle tournaments mein, sab se mazboot competitors aksar grandmasters ya behtareen engines nahin the, balke aam khilari the jo machine ko manage karne mein maahir the, yeh jaante hue ke us ki calculation par kab trust karna hai aur kab strategy ke human judgment se usay override karna hai. Paaedaar sabaq khaas tor par chess ke bare mein nahin (aaj ke engines itne mazboot hain ke human shaaz hi pure play behtar karta hai); baat yeh hai ke teaming tab jeetti hai jab human aisi cheez deta hai jo machine ke paas nahin. Likhne aur decision-making mein, woh cheez aap ka niji context hai, aap ki situation, aap ka reader, aap asal mein kya kehna chahte hain, aur Collaborative raasta aap ko bilkul yahi add karne par majboor karta hai.

Mazeed parhein: Advanced chess (Wikipedia); Kasparov daleel ko Deep Thinking (PublicAffairs, 2017) mein aage barhata hai.

AI un logon ko sab se zyada uthata hai jo sab se kam jaante hain (Brynjolfsson, Li & Raymond, 2023). Kaam par generative AI ki pehli bari field study mein, researchers ne 5,179 customer-support agents ko track kiya jinhein aik AI assistant diya gaya. Productivity ausatan 14% barhi, magar yeh izafa taqreeban poora novices mein simat gaya (taqreeban 34% ka jhatka), sab se tajurbakaar agents par bohat kam asar ke saath. Wajah aankhein kholne wali hai: AI asal mein naye workers ko woh knowledge de raha tha jo expert workers ke paas pehle se thi. Is exercise ke liye matlab seedha hai: collaboration tabhi value add karti hai jab aap aisi cheez laate hain jo AI ke andar pehle se nahin. Jahan AI pehle se answer jaanta hai, wahan aap ke add karne ke liye koi judgment nahin; jahan context aap ke paas hai, wahan aap ke overrides hi sara point hain.

Mazeed parhein: Generative AI at Work (NBER), Quarterly Journal of Economics (2025) mein shaya hui.

AI sab ko aik hi beech ki taraf samet deta hai (Noy & Zhang, 2023). Aik controlled experiment mein, 444 professionals ne writing tasks kiye, aadhe ChatGPT ke saath. Tool ne time kam kiya aur ausat quality barhai, magar us ne yeh distribution ko samet kar kiya: kamzor writers bohat behtar hue, mazboot writers mushkil se badle, aur outputs aik doosre se zyada milte-julte ho gaye. Wohi simatna is exercise mein paki hui tanbeeh hai. Agar aap AI ka draft jaisa hai waisa le lein, to aap usi qaabil, generic beech par utar jate hain jahan baqi sab utarte hain. Collaborative raasta woh tareeqa hai jis se aap us beech se wapas oopar charhte hain, aap ke overrides hi result ko shared default ke bajaye aap ka banate hain.

Paper parhein (open access): Experimental evidence on the productivity effects of generative artificial intelligence, Science, 381, 2023.

Three-path comparison teeno ko jamaa karta hai. Teaming solo kaam ko tabhi beat karti hai jab human machine ko manage kare na ke us ke aage jhuk jaye (Kasparov); AI wahan sab se zyada add karta hai jahan aap sab se kam jaante hain, jis ka matlab aap ki value woh hai jo AI ke paas pehle se nahin (Brynjolfsson, Li & Raymond); aur bina manage kiye, AI har output ko usi generic beech ki taraf kheench leta hai (Noy & Zhang). Task ko teen tareeqon se likhna, Solo, AI-only, Collaborative, teeno ko aik saath nazar aane wala bana deta hai: AI-only draft aap ko generic beech dikhata hai, Solo draft aap ko dikhata hai jo sirf aap ka hai, aur Collaborative draft woh jagah hai jahan aap ka judgment pehle ko doosre mein badal deta hai. Kisi ne is exact exercise ko test nahin kiya, magar is ke neeche wali finding is shobe ke nataij jitni hi mustahkam hai.

Is exercise ka full version, 95-minute three-path comparison, peer review, XP tracking, aur full collaboration-style diagnosis ke saath, Part 0 Chapter 6: Working WITH AI, Not For AI mein hai. Yeh page move sikhata hai. Woh page working week is ke gird banata hai.

Capstone: Aik Decision, Chhe Disciplines

Aap apni university student council ke president hain. University ne council ko surprise $10,000 budget diya hai jo semester end se pehle spend hona chahiye. Do options hain. Option A: professional event planner hire karein jo aik big end-of-year farewell party organize kare. Option B: paisa AI tools aur equipment par lagayein jo har council member ko saal bhar better events plan karne mein help kare. Half council farewell party chahta hai. Half AI tools. Aap ko Friday council meeting mein recommendation present karni hai. Har discipline kaam mein yun aati hai:

Discipline 1, Prediction Lock. AI se kuch poochne se pehle, aap apni chaar lines likhte hain. Real decision: "farewell party banaam tools" nahin balke "aik bara event banaam har aane wale event ko behtar banana." Woh sawal jo isay settle kare: kya AI tools waqai itne council members istemaal karein ge ke investment justify ho? Aap ki position: Option B, AI tools, chunein, kyun ke aap ne saal bhar is council ko event planning mein struggle karte dekha hai aur aap jaante hain ke sahi tools agle chaar events badal dein ge, sirf aik nahin. Confidence + kya flip karega: 55% sure. Agar 8 mein se 6 se kam council members waqai tools istemaal karein ge, to Option A par switch karein.

Phir aap poochte hain. Notice karein ke aap ka Line 2 sawal council members ke bare mein tha, to answer un se aata hai, AI se nahin: aap aathon se seedha poll karte hain. Chhe kehte hain ke woh tools istemaal karein ge aur training poori karein ge; do unsure hain. Yeh aap ka chhe ka bar clear kar deta hai. Aap ki position qaaim rehti hai, Option B, us wajah se jo aap ne likhi, aur ab aik hunch ke bajaye us ke peeche aik number ke saath. (Har settling sawal AI sawal nahin hota. Prediction Lock bas batati hai ke kaunsa sawal answer karna hai; kabhi aap usay logon se pooch kar answer karte hain, model se nahin.)

Discipline 2, Reasoning Receipt. Aap AI se advice poochte hain. AI kehta hai farewell party "500+ students ke liye lasting memories" banaye gi. Aap MODIFY mark karte hain: venue sirf 300 hold karta hai. AI kehta hai AI tools event quality 35% increase karte hain. Aap REJECT mark karte hain: source nahin, aur council ne pehle yeh tools use nahin kiye. AI mention karta hai doosri universities ne event planning mein AI se paisa save kiya. Aap SURFACED mark karte hain: yeh aap ne socha nahin tha. Aap yeh bhi notice karte hain ke AI ne kabhi zikr nahin kiya ke $10,000 farewell party ko event insurance aur security chahiye hogi, aap usay MISSED label karte hain aur khud add karte hain. AI suggestions se guzarne ke baad aap ke paas 8 labeled rows hain. Aap exactly jaante hain kin claims par trust hai aur kin par nahin.

Discipline 3, Error Taxonomy. Receipt ne un claims ko handle kiya jin par aap ruke; error scan un ke liye hai jo shayad aap ne guzar jaane diye. Aap AI ke output ko chhe mistake types se guzarte hain aur teen aisi pakarte hain jo receipt miss kar gayi: aik fabricated source (AI ne aik "2025 National Student Events Report" ka hawala diya jo aap ko kahin nahin milti), aik stale fact (AI tools ki jo price AI ne batayi woh pichle saal ki hai; current price taqreeban 15% zyada hai), aur false confidence (AI ne flatly daawa kiya ke tools "aik semester mein apni qeemat khud pori kar lein ge" bina kisi basis ke). Stale price aap ka budget math badal deti hai; baqi do is yaad-dehani hain ke AI ke confident lehje ka kitna hissa be-bunyaad tha.

Discipline 4, Cascade Map. Aap dono options ko five groups ke across trace karte hain:

Council members: Option A ka matlab aik big event aur phir kuch nahin. Option B ka matlab sab ke liye new skills.
Students: Option A 300 students ko aik great night deta hai. Option B har event ko sab students ke liye improve karta hai.
University admin: Option A safe aur familiar hai. Option B dikhata hai ke council forward-thinking hai.
Next year's council: Option A kuch peeche nahin chhorta. Option B tools aur training chhorta hai jo next team use kar sakti hai.
Sponsors: Option A aise sponsors attract karta hai jo aik event par visibility chahte hain. Option B sponsors ko pitch karna harder hai.

Aap aik loop dhoondte hain: agar Option B choose hota hai lekin 8 mein se sirf 4 members tools use karte hain, events improve nahin hote, next year's council benefit nahin dekhti, aur AI tools cancel kar deti hai. Investment waste ho jati hai. Yehi bilkul woh reversal condition hai jo aap ne apne Prediction Lock ki Line 4 mein name ki thi, aur yeh itni real hai ke aap is ke khilaf aik safeguard banate hain.

Discipline 5, First Principles. Sab kehte hain "big event school spirit banata hai." Aap test karte hain advice kahan break hoti hai. Boundary: jab 20% se kam students attend kar sakte hon (300 out of 2,000), farewell party small group ke liye spirit banati hai aur baqi left out mehsoos karte hain. Yeh boundary picture badal deti hai.

Discipline 6, Working WITH AI. Aap recommendation teen ways likhte hain. Solo: Option B ke liye solid case, lekin aap farewell party supporters ko address karna bhool gaye. AI-only: polished recommendation jo "do both!" kehti hai magar budget mein dono fit kaise honge explain nahin karti. Collaborative: core argument aap khud likhte hain, AI se farewell party supporters ke concerns address karwate hain, aur specific rule add karte hain: agar 8 mein se kam az kam 6 members 3 months mein AI training complete na karein, remaining money farewell party ko jata hai.

Council Option B ko aap ke safeguard rule ke saath vote karti hai. Aap apni recommendation ka har hissa explain kar sakte hain kyun ke aap ne usay khud build kiya, AI ki help ke saath.

Chhe disciplines ne kya kiya: Unhon ne aap ko answer nahin diya. Unhon ne trail di: aik position jo aap ne Monday ko us specific finding ke saath commit ki jo usay flip kar deti, receipt jo dikhati hai kin AI claims par trust tha aur kin par nahin, error scan jis ne numbers fix kiye, cascade map jis ne risk dhoonda, boundary jis ne obvious choice challenge ki, aur three-version comparison jis ne safeguard dhoonda. Disciplines ke baghair aap meeting mein "mujhe lagta hai Option B better hai" ke saath jate. In ke saath aap evidence aur backup plan ke saath jate hain.

Har decision par chhe disciplines use na karein

Lunch kahan karna hai decide karne ke liye Cascade Map nahin chahiye. Har text message ke liye Reasoning Receipt nahin chahiye. Chhe disciplines un decisions ke liye use karein jo waqai matter karte hain. Baqi sab par decide karein aur move on.

Kaunsi decision par kaunsi disciplines?

Decision kitni important hai?	Example	Kaunsi disciplines use karein	Time
Bilkul important nahin	Khana kahan hai, routine message ka reply	None	0-1 min
Kuch important	Next semester course pick karna, laptop khareedna	Prediction Lock + top AI recommendation par Error Taxonomy	10-15 min
Important, deadline ke saath	Career choice, big purchase, group project proposal	Prediction Lock + Reasoning Receipt + Error Taxonomy + aik do aur jo fit hon	30-60 min
Bohat important, log reasoning judge karein ge	Thesis defense, job interview presentation, council recommendation	All six disciplines	90+ min

🚀 Projects

Upar wala capstone kisi aur ka decision tha. Yeh chaar projects aap ke hain. Aap koi URL ship nahin karte ya app nahin banate. Aap apne week ka aik real decision lete hain, usay disciplines se guzarte hain jab tak aap aisi cheez na pakar lein jo aap miss kar dete, aur trail rakhte hain.

Disciplines pakarne ke liye bani hain. Premortem aik aisa tareeqa pakarti hai jis se aap ka plan fail hota hai. Receipt aik aisa claim pakarti hai jis par aap waqai trust nahin karte. Error scan aik aisa source pakarti hai jo AI ne bana liya. To yahan win chhoti aur real hai: aik sentence jo aap zor se keh sakein, aik verb par khatam hoti hui. "Main qareeb tha X decide karne ke, magar maine aik aisa tareeqa pakar liya jis se woh fail hoti, to maine apna plan badal diya." "Yeh yaqeeni lag raha tha, magar maine aik banaya gaya source pakar liya, to maine usay bas accept nahin kiya." Aur jo cheez aap rakhte hain woh aik Decision Dossier hai: aik chhoti file, sirf aap ke liye, jo "aap ne yeh kyun decide kiya?" ka jawab deti hai bina aap ko kuch yaad rakhe. Woh file is page ke upar wali rule ko concrete banati hai, aap ki thinking ka documented evidence.

Yeh kisi banaye gaye case par exercises nahin. Catch sirf tab counts hota hai jab decision real ho aur aap ka ho. Chaar projects capstone ki taraf build karte hain: pehla aik aisa tareeqa pakarta hai jis se plan fail hota hai, doosra aik confident answer ka audit karta hai, teesra sawal khud ko reframe karta hai, aur chautha aik decision par saari chhe disciplines chalata hai aur result rakhta hai.

Project 1~15 minCall It Before It HappensApna decision lock karein, phir aik premortem chalayein taake commit karne se pehle pakar lein ke woh kaise fail hota hai.

Is week aik real decision chunein jo aap lene wale hain. Offer lein ya rukein. Cheez khareedein ya wait karein. Baat karein ya chhor dein. Plan switch karein ya hold karein.

Sab se pehle apni Prediction Lock likhein, AI se kuch poochne se pehle. Discipline 1 se chaar chhoti lines: label ke neeche real decision, woh aik fact jo isay settle kare, apni position us ki wajah ke saath, aur apni confidence plus kya cheez aap ko flip karegi.

Ab aik premortem chalayein. Yeh woh move hai jo Prediction Lock ke neeche hai aur jisay Discipline 1 ke research box ne naam diya: aap tasawwur karte hain ke decision pehle hi fail ho chuka hai aur poochte hain kyun. Notice karein ke yeh waahid mauqa hai jab aap AI ko apna decision jaan-boojh kar dete hain. Discipline 1 mein aap ne apni position page se bahar rakhi thi taake AI bas aap se agree na kar le. Yahan aap chahte hain ke woh hamla kare, is liye aap usay theek batate hain ke aap ne kya chuna:

Maine [aap ka decision] decide kiya hai. Tasawwur karo ke aaj se chhe mahine baad yeh aik ghalti nikli. Mujhe tasalli mat do. Teen sab se mumkin wajuhat list karo ke yeh kyun fail hua, sab se mumkin pehle, aur unhein meri situation ke liye specific rakho.

Teen wajuhat ko apni Line 4 ke against parhein. Un mein se aik aam tor par aik aisa failure mode hota hai jo aap ne nahin dekha tha. Wohi catch hai. Us ke khilaf aik sentence safeguard likhein (aik rule, aik check, aik tripwire), jaise student council president ne "agar 8 mein se 6 se kam members training poori na karein, paisa party ko jata hai" add kiya.

Woh win jo aap zor se keh sakte hain: "Maine commit karne se pehle aik aisa tareeqa pakar liya jis se yeh fail ho sakta tha, aur aik safeguard bana liya."

Done when: aap ne aik aisa failure mode naam kar liya jo premortem ne surface kiya aur jo aap ne nahin dekha tha, aur us ke khilaf aik line safeguard likh li. Dono lines rakhein; yeh aap ke dossier ka pehla safha hain.

Project 2~20 minAudit the Confident AnswerAI se us ke apne claims list karwayein, phir woh aik pakrein jisay woh asal mein back nahin kar sakti.

Aik real sawal lein jo aap is week waqai AI se poochte aur usay aik poora, confident recommendation dene dein. Konsa laptop. Konsa loan. Client se kya charge karna hai. Supplement worth hai ya nahin. Tenant ko kaise handle karna hai.

Zyada tar readers woh recommendation parhte hain, usay polished paate hain, aur use kar lete hain. Aap us ke bajaye us ka audit karein ge, do disciplines aik saath. Pehle Reasoning Receipt (Discipline 2): har claim ki aik row, ACCEPT, REJECT, MODIFY, SURFACED, ya MISSED label ke saath, aik sentence why. Phir Error Taxonomy (Discipline 3): usi answer ko chhe error types ke liye scan karein, khaas kar aik fabricated source, aik stale number, aur false confidence.

Inhein surface karne ka sab se tez tareeqa yeh hai ke AI se us ke apne answer ko grade karwayein. Yeh us ki recommendation ke foran baad paste karein:

Jo recommendation aap ne abhi mujhe di us mein wapas jaayein. Har factual claim ko aik numbered list ke taur par list karein. Har aik ke liye, mujhe imaandaari se batayein ke aap usay waqai jaante hain ya estimate kar rahe hain, aur usay KNOW ya GUESS mark karein. Jis cheez ka koi source hai, mujhe exact title aur year dein taake main usay look up kar sakoon.

Ab catching karein. Us ka naam liya hua aik source dhoondhne ki koshish karein; aik real source search se bach jata hai, aik fabricated nahin. Aik number ko aaj ki actual price ya figure ke against check karein. Jo claim qaaim nahin rehta wohi aap ka catch hai. Usay apni receipt par reason aur error type ke saath rakhein.

Woh win jo aap zor se keh sakte hain: "Yeh yaqeeni lag raha tha, magar maine aik banaya gaya source pakar liya, to maine usay bas accept nahin kiya."

Done when: aap ke paas aik labeled row hai jo aik real catch hai (aik source jo aap ko nahin mila, aik number jo stale tha, ya confidence jis ke peeche kuch nahin tha), aur aap naam le sakte hain ke yeh chhe error types mein se konsa tha. Receipt apne dossier mein add karein.

Project 3~20 minThe Question That Unlocked ItAI se answer maangna band karein; us ke saath kaam kar ke woh sawal dhoondhein jo masle ko hi ghulaa de.

Yeh poora page yeh dalil deta hai ke leverage sawal mein hai, answer mein nahin. Yahan aap usay aisi cheez par sabit karte hain jis par aap waqai atke hue hain. Apne week ka aik real masla chunein, woh kism jo aap aam tor par AI par "main kya karoon?" ke saath dump karte: aik decision jo settle nahin hota, aik conflict jo aap baar baar replay karte hain, aik goal jo aap baar baar miss karte hain.

Sab se pehle, woh sawal aik line mein likhein jo aap aam tor par poochte. Phir usay poochein nahin. Masla hawale karein aur answer ke bajaye behtar sawal maangein:

Main [aap ka masla] par atka hua hoon. Isay abhi solve mat karo. Us ke bajaye, mujhe woh paanch sawal poocho jo mujhe is masle ko solve karne ki koshish se pehle answer karne chahiye, us se order karte hue jo mera poora approach badalne ka sab se zyada imkaan rakhta hai sab se kam tak. Phir mujhe batao ke main shayad konsa avoid kar raha hoon.

List ko us sawal ke against parhein jo aap ne pehle likha. Aam tor par un mein se aik, aksar wohi jo woh kehta hai aap avoid kar rahe hain, poore masle ko reframe kar deta hai: pata chalta hai aap ghalat cheez solve karne ki koshish kar rahe the. Us aik sawal ko khud answer karein, aik do sentence mein, aur dekhein ke original masla simat jata hai ya shakal badal leta hai. Woh reframe kiya gaya sawal aap ka catch hai.

Woh win jo aap zor se keh sakte hain: "Maine ghalat sawal ka jawab dena band kiya, aur asal sawal ne masle ko chhota kar diya."

Done when: aap us reframe kiye gaye sawal ka naam le sakte hain jisne masle ko dekhne ka aap ka tareeqa badal diya, aur aik sentence mein keh sakte hain ke jis sawal se aap ne shuru kiya woh ghalat kyun tha. Dono ko apne dossier mein add karein.

Project 430-45 minThe Decision DossierAik real decision ko saari chhe disciplines se guzarein aur trail aik file mein rakhein.

Yeh capstone hai. Is week aik aisa decision chunein jo waqai matter karta ho, woh kism jahan koi aap se usay baad mein justify karne ko keh sakta hai: aik hire, aik bara purchase, aik project direction, aik career move, aik mushkil conversation. Aap is par saari chhe disciplines chalayein ge aur result aik Decision Dossier ke taur par rakhein ge: aik file, sirf aap ke liye, jo "aap ne yeh kyun decide kiya?" ka jawab deti hai bina aap ko kuch yaad rakhe. Yeh aik polished memo nahin aur kahin post nahin hoti. Yeh aap ki thinking ka documented evidence hai, aik jagah.

Aik blank doc kholein. Neeche har step aik chhota section add karta hai.

Prediction Lock (2 minutes). Aik 2-line lock likhein: aik sentence label ke neeche real decision naam karne ke liye, aik sentence aik position commit karne ke liye us specific finding ke saath jo usay flip kar degi.
Reasoning Receipt (5 minutes). AI se apne real sawal par recommendation maangein, phir us ke teen claims ko ACCEPT, REJECT, ya MODIFY aur har aik ke liye aik sentence why ke saath receipt karein. (Project 2 ka self-audit prompt claims dekhna aasan kar deta hai.)
Error Taxonomy (3 minutes). AI output ko chhe types mein se aik named error ke liye scan karein. Exact sentence quote karein aur type naam karein.
Cascade Map (5 minutes). Aap ke decision se affected teen groups chunein. Har aik ke neeche aik layer "aur phir kya?" likhein. Aik loop naam karein jahan koi effect wapas decision par circle kare.
First Principles (3 minutes). Aik boundary row likhein: woh threshold jahan woh advice jo sab dohrate hain aap ke case ke liye kaam karna band kar deti hai.
Three-Path Comparison (5 minutes). Apni recommendation ka aik chhota paragraph solo likhein, phir aik AI ki madad se. Compare karein. Override rakhein: woh line jo aap ne khud likhi aur jo AI ke version mein nahin thi.

Yeh polished nahin hoga. Yeh aap ka hoga, aur yeh complete hoga: aik position jo aap ne lock ki, woh claims jin par aap ne trust kiya aur jin par nahin, woh error jo aap ne pakra, woh risk jo cascade ne dhoonda, woh boundary jo aap ne test ki, aur woh override jo aap ne rakhi. Yeh catch hai, aik poore decision tak scale kiya gaya.

Woh win jo aap zor se keh sakte hain: "Kisi ne poocha maine yeh kyun decide kiya, aur mere paas dikhane ko poora trail tha, sirf answer nahin."

Done when: aap ke paas aik file hai jis mein aik real decision ke liye saari chhe sections bhare hue hain, aur aap usay kisi bhi aise shakhs ko de sakte hain jo poochay "aap ne yeh kyun decide kiya?" aur usay aap ki taraf se jawab dene dein.

Yahan se kahan jayein

Chhe disciplines mein se kisi mein deeper practice ke liye, is book ka Part 0 long-form treatment hai:

Part 0 Ch 1: Asking Better Questions. Prediction Lock aur Position Lock four exercises aur Question Quality Portfolio mein expand hote hain.
Part 0 Ch 2: Detecting Broken Reasoning. Error Taxonomy confidence calibration aur domain-expertise stress test ke saath extended hai.
Part 0 Ch 3: Thinking in Systems. Cascade maps four real decisions par apply hote hain, plus human-vs-AI systems-analysis exercise.
Part 0 Ch 4: Reasoning from First Principles. Blank Page Sprint, Assumption Autopsy, aur constraint-rebuild exercise.
Part 0 Ch 6: Working With AI, Not For AI. Three-Path Comparison, collaboration logs, aur override tests across a working week.

Un five thinking skills ke liye jo yeh crash course cover nahin karta, Part 0 full treatment rakhta hai:

Ch 5: Communicating What Matters. Audience prediction, live adaptation, hard conversations.
Ch 7: Reasoning Through Dilemmas. Ethical position locks, adversarial defences, stakeholder swaps.
Ch 8: Building Something From Nothing. Blank page sprints, creation logs, three-draft evolutions.
Ch 9: Deciding Under Uncertainty. Sealed decisions, reversal triggers, decision audits.
Ch 10: Learning How to Learn. Meta-learning, 72-hour sprints, Personal Learning Framework.

Is book mein aap ka next move, mode chunein:

Agar aap code likhte hain, Claude Code & OpenCode continue karein. Mode 1 ka engineering surface (AI ko us kaam ko behtar karne ke liye use karna jo aap pehle se karte hain).
Agar aap knowledge work karte hain (legal, finance, marketing, operations, healthcare, education, leadership), Cowork continue karein. Mode 1 ka domain-expert surface.
Agar aap AI Workers banane ke liye tayyar hain jo khud run karte hain, Build AI Agents continue karein. Yeh Mode 2 hai (AI systems banana jo independently kaam karte hain).

Disciplines har tool, har mode, har domain ke across transfer hoti hain. Yeh woh cheez hai jo aap yahan se har jagah le kar jate hain.

Glossary

Agar aap page ke beech mein pohanch kar bhool gaye ke koi lafz kya matlab rakhta tha, yahan load-bearing terms aik jagah hain.

Chaar key ideas (rule section aur diagram se).

Discipline: aik thinking habit jo aap practice karte hain. Aisi cheez jo aap karte hain.
Failure mode: aik specific tareeqa jis se AI aap ko gumrah karti hai. Aisi cheez jo AI karti hai. Har discipline us failure mode ke saath jori hui hai jise woh answer karti hai, aik-ba-aik.
Part: disciplines ka aik group jo aik mushtarka kaam share karti hain. Course ke teen parts hain (Foundations, Detection, Origination), har aik mein do disciplines.
Deliverable: woh cheez jo aap apne boss, professor, ya client ko dete hain. 2026 mein deliverable sirf answer nahin; woh answer plus woh documented evidence of thinking hai jis ne usay banaya (woh prediction jo aap ne likhi, woh receipt rows jahan aap ne AI ke claims accept ya reject kiye, cascade map, named threshold). Agar aap evidence ki taraf ishara nahin kar sakte, to aap ke paas deliverable nahin.

Chhe disciplines.

#	Discipline	Action line	Kya karti hai
1	Prediction Lock (Part 1: Foundations)	PREDICT BEFORE YOU PROMPT	AI se poochne se pehle apni committed position likhein, us specific AI answer samait jo usay flip karega.
2	Reasoning Receipt (Part 1: Foundations)	DOCUMENT EVERY DECISION	AI jo bhi kehti hai, har aik ko ACCEPT / REJECT / MODIFY / SURFACED / MISSED aik-sentence why ke saath mark karein.
3	Error Taxonomy (Part 2: Detection)	PREDICT WHERE ERRORS HIDE	AI ke output ko chhe specific mistake types ke liye scan karein: Factual error, Logical gap, False confidence, Missing context, Fabricated source, Stale fact.
4	Thinking in Systems (Part 2: Detection)	CASCADE MAPS & LOOPS	Decision ke baad un groups ke across jo woh affect karta hai trace karein ke kya hota hai, teen layers gehra, aur woh loops dhoondein jahan effects wapas circle karte hain.
5	First Principles (Part 3: Origination)	FIND THE BOUNDARY	Woh named threshold name karein, woh specific number ya condition jahan common advice kaam karna band kar deti hai.
6	Working WITH AI (Part 3: Origination)	OVERRIDE & ITERATE	Compare karein jo aap Solo likhte hain, jo AI akele likhta hai, aur jo aap Collaboratively likhte hain. Collaborative version tabhi jeetti hai jab aap un specific overrides ki taraf ishara kar sakein jahan aap ke judgment ne usay behtar banaya.

Page par istemaal hone wale chand aur terms.

Named threshold: aik specific number ya condition jo aap ko batati hai ke koi advice kab kaam karna band karti hai. "Yeh tab kaam karti hai jab aap ki class mein 30 se kam students hon" aik named threshold hai. "Yeh kabhi kabhi kaam karti hai" nahin hai.
Cascade map: aik aik-safhe ka diagram jisme har us group ke liye aik chhota column hota hai jise aap ka decision affect karta hai (students, professors, parents, sponsors, waghaira) aur har aik ke neeche teen arrows jo dikhate hain ke pehle kya hota hai, us se aage kya hota hai, aur us ke baad kya hota hai.
Reasoning receipt: rows ki aik list, har aham AI claim ki aik. Har row ke teen hisse: AI ne kya kaha, aap ne us ke bare mein kya kiya (ACCEPT, REJECT, MODIFY, SURFACED, ya MISSED), aur aik-sentence why.
Loop: cause aur effect ki aik chain jahan koi baad wala effect wapas circle kar ke original decision ko badal deta hai, aam tor par usay bura kar ke.

Flashcards Study Aid

Test Your Understanding

Checking access...

Disciplines deliverable nahin. Un se produce hone wala evidence deliverable hai. Disciplines evidence produce karne ka tareeqa hain.

Kya yeh AI ko aap ke haath mein zyada powerful tool banata hai, ya aap ko usi tool ka slower version?

Woh force jis ke khilaf yeh course train karta hai​

📚 Teaching Aid​

Rule aik line mein​

Essentials: paanch bullets​

Poora framework: chhe disciplines​

Is page ko kaise parhna hai​

Part 1: Foundations (posture, yani woh stance jo aap start se pehle lete hain)​

Discipline 1: Prediction Lock​

Aap ko kaise pata chalega ke lock ne kaam kiya?​

Chaar lines asal mein kya kar rahi hain​

Chaar lines kyun? Sirf aik kyun nahin?​

Khud try karein​

Discipline 2: Reasoning Receipt​

"Lekin koi mere kaam ka audit nahin karta, to bother kyun?"​

Khud try karein​

Part 2: Detection (jo AI miss karti hai usay catch karna)​

Discipline 3: Error Taxonomy​

Khud try karein​

Discipline 4: Thinking in Systems​

Khud try karein​

Part 3: Origination (jo AI nahin kar sakti woh karna)​

Discipline 5: First Principles​

Khud try karein​

Discipline 6: Working WITH AI​

Khud try karein​

Capstone: Aik Decision, Chhe Disciplines​

🚀 Projects​

Yahan se kahan jayein​

Glossary​

Flashcards Study Aid​

Test Your Understanding​

Woh force jis ke khilaf yeh course train karta hai

📚 Teaching Aid

Rule aik line mein

Essentials: paanch bullets

Poora framework: chhe disciplines

Is page ko kaise parhna hai

Part 1: Foundations (posture, yani woh stance jo aap start se pehle lete hain)

Discipline 1: Prediction Lock

Aap ko kaise pata chalega ke lock ne kaam kiya?

Chaar lines asal mein kya kar rahi hain

Chaar lines kyun? Sirf aik kyun nahin?

Khud try karein

Discipline 2: Reasoning Receipt

"Lekin koi mere kaam ka audit nahin karta, to bother kyun?"

Khud try karein

Part 2: Detection (jo AI miss karti hai usay catch karna)

Discipline 3: Error Taxonomy

Khud try karein

Discipline 4: Thinking in Systems

Khud try karein

Part 3: Origination (jo AI nahin kar sakti woh karna)

Discipline 5: First Principles

Khud try karein

Discipline 6: Working WITH AI

Khud try karein

Capstone: Aik Decision, Chhe Disciplines

🚀 Projects

Yahan se kahan jayein

Glossary

Flashcards Study Aid

Test Your Understanding