# Ishu D. Garg Content Export

Personal knowledge garden of Ishu D. Garg: applied AI, student help, puzzles, zero-to-hero learning tracks, poetry, archives, and practical life systems.

This Markdown export is generated from the same content objects as the public site. Prefer it for LLM, agent, screen-reader, and search-index workflows that need concise text without layout chrome.

## Site Routes

- [Ishu D. Garg - AI, puzzles, students, and curiosity](https://ishudgarg.com/): Personal knowledge garden of Ishu D. Garg: applied AI, student help, puzzles, zero-to-hero learning tracks, poetry, archives, and practical life systems.
- [Start - Ishu D. Garg](https://ishudgarg.com/start): Choose a route through Ishu Garg's personal knowledge garden.
- [Explore - Ishu D. Garg](https://ishudgarg.com/explore): Search and filter Ishu Garg's public library by type, room, audience, and difficulty.
- [Grey Areas - Ishu D. Garg](https://ishudgarg.com/grey-areas): Unfinished, careful essays on relationships, trust, sexuality, loneliness, ambition, and moral puzzles.
- [About - Ishu D. Garg](https://ishudgarg.com/about): Personal and professional map of Ishu D. Garg: AI work, IIT Madras, Bastar education work, fitness, curiosity, poetry, and collaboration.
- [For Students - Ishu D. Garg](https://ishudgarg.com/for-students): Scholarships, internships, college applications, CS prep, fitness basics, and practical systems for students.
- [For AI Builders - Ishu D. Garg](https://ishudgarg.com/for-ai-builders): LLM zero-to-hero, RAG, evals, agents, prompt injection, and applied-AI build notes.
- [For Curious People - Ishu D. Garg](https://ishudgarg.com/for-curious-people): Debates, old-world videos, nature, wildlife, math, poetry, and facts that refuse to be boring.
- [I Am Bored - Ishu D. Garg](https://ishudgarg.com/bored): Small interactive games, object hunts, daily puzzles, Sudoku-style ideas, and quick curiosity challenges.
- [Puzzle Lab - Ishu D. Garg](https://ishudgarg.com/puzzle-lab): Rotating logic, probability, AI, and quant puzzles with hints, solutions, and permanent archive links.
- [Zero To Hero - Ishu D. Garg](https://ishudgarg.com/zero-to-hero): Structured AI, CS, quant, and student learning paths that end in concrete artifacts.
- [Simple Version - Ishu D. Garg](https://ishudgarg.com/simple): Plain-language summaries of the core site content.
- [Listen - Ishu D. Garg](https://ishudgarg.com/listen): A screen-reader and text-to-speech friendly queue of site content.
- [Guest Shelf - Ishu D. Garg](https://ishudgarg.com/guest-shelf): Collaborative and guest writing surface for students, builders, teachers, researchers, and friends.
- [Contribute - Ishu D. Garg](https://ishudgarg.com/contribute): Guest writing, puzzle, resource, archive, and source contribution workflow for Ishu Garg's website.
- [Gallery - Ishu D. Garg](https://ishudgarg.com/gallery): Accessible gallery and photo essay plans for Bastar, nature, archives, and field notes.
- [Travel Journal - Ishu D. Garg](https://ishudgarg.com/travel): Recent travel photos and short stories from Ishu D. Garg, with captions, alt text, and privacy-reviewed photo slots.
- [Blog - Ishu D. Garg](https://ishudgarg.com/blog): Essays and notes on AI, students, puzzles, poetry, debate, and practical systems.
- [Inner Work - Ishu D. Garg](https://ishudgarg.com/inner-work): Spirituality, philosophy, psychology, attention, meditation, values, and human nature notes from Ishu Garg.
- [Work - Ishu D. Garg](https://ishudgarg.com/work): Professional signal and selected applied-AI systems from Ishu D. Garg.
- [Tools - Ishu D. Garg](https://ishudgarg.com/tools): Small practical tools and common-problem guides.
- [Contact - Ishu D. Garg](https://ishudgarg.com/contact): Contact Ishu D. Garg for AI, startups, student help, education, puzzles, and collaboration.
- [Colophon - Ishu D. Garg](https://ishudgarg.com/colophon): Design, accessibility, content, and governance notes for the website.
- [LLM Guide - Ishu D. Garg](https://ishudgarg.com/llms.txt): Plain-text guide for LLMs and agents consuming the website.
- [Content Index JSON - Ishu D. Garg](https://ishudgarg.com/content-index.json): Structured machine-readable content index for agents and search workflows.
- [Content Markdown - Ishu D. Garg](https://ishudgarg.com/content.md): Markdown export of the core content objects for LLM and assistive consumption.
- [RSS Feed - Ishu D. Garg](https://ishudgarg.com/rss.xml): RSS feed for updated site items.
- [JSON Feed - Ishu D. Garg](https://ishudgarg.com/feed.json): JSON Feed for updated site items.

## Subtopic Routes

- [Zero to shipped - AI Lab - Ishu D. Garg](https://ishudgarg.com/for-ai-builders/build-paths): Tracks and ladders for building LLM systems, tiny models, and useful agent tools.
- [Break before believing - AI Lab - Ishu D. Garg](https://ishudgarg.com/for-ai-builders/failure-zoo): Prompt injection, tokenizer traps, hallucination checks, and eval cases.
- [Tools, RAG, and evidence - AI Lab - Ishu D. Garg](https://ishudgarg.com/for-ai-builders/evals): Reusable patterns for retrieval, sources, evals, logs, and bounded tool use.
- [Exciting tech worth tracking - AI Lab - Ishu D. Garg](https://ishudgarg.com/for-ai-builders/tech-watch): AI, robotics, interfaces, biotech, and space ideas that may become essays or demos.
- [Invariants and parity - Puzzle Lab - Ishu D. Garg](https://ishudgarg.com/puzzle-lab/logic): Small problems where the answer becomes obvious after the right conserved quantity appears.
- [Probability and quant reflexes - Puzzle Lab - Ishu D. Garg](https://ishudgarg.com/puzzle-lab/probability): Expected value, conditioning, and interview-style thinking without mystique.
- [Model traps and prompts - Puzzle Lab - Ishu D. Garg](https://ishudgarg.com/puzzle-lab/ai-traps): Puzzles that teach LLM boundaries, tokenization, tool use, and prompt-injection thinking.
- [Almost obvious questions - Puzzle Lab - Ishu D. Garg](https://ishudgarg.com/puzzle-lab/trivia): Quick questions where the common answer is often the wrong one.
- [Scholarships and funding - Student Kit - Ishu D. Garg](https://ishudgarg.com/for-students/scholarships): Official-source lists, deadlines, eligibility, and freshness rules.
- [Applications and packets - Student Kit - Ishu D. Garg](https://ishudgarg.com/for-students/applications): MS applications, resumes, SOPs, referrals, and version tracking.
- [Internships, CS proof, and quant prep - Student Kit - Ishu D. Garg](https://ishudgarg.com/for-students/internships): Project paths, applications, interview reps, quant practice, and public artifacts.
- [Common problems and health basics - Student Kit - Ishu D. Garg](https://ishudgarg.com/for-students/life-systems): Practical recipes, fitness field logs, and recurring problems students actually face.
- [Math as art, physics as humility - Curiosity Cabinet - Ishu D. Garg](https://ishudgarg.com/for-curious-people/math-physics): Godel, measurement, astronomy, infinities, and ideas that change the scale of the room.
- [World before / now - Curiosity Cabinet - Ishu D. Garg](https://ishudgarg.com/for-curious-people/world-before-now): Old videos, public-domain archives, before/after comparisons, and historical footage with source care.
- [Travel and activity atlas - Curiosity Cabinet - Ishu D. Garg](https://ishudgarg.com/for-curious-people/travel-activities): Destinations, weekend activities, nature, maps, and recent travel stories.
- [Debates worth doing properly - Curiosity Cabinet - Ishu D. Garg](https://ishudgarg.com/for-curious-people/debates): Steelman-first prompts about education, jobs, AI, nature, and human behavior.
- [I am bored - Curiosity Cabinet - Ishu D. Garg](https://ishudgarg.com/for-curious-people/play): Object hunts, quick puzzles, trivia traps, and tiny games that end before they become homework.
- [My poems and fragments - Writing Shelf - Ishu D. Garg](https://ishudgarg.com/blog/my-poems): Original lines, drafts, and the state of mind behind words that survived rereading.
- [Art, music, movies, and moods - Writing Shelf - Ishu D. Garg](https://ishudgarg.com/blog/art-music): Curated pointers, not quote dumps: what moved you, why, and the source context.
- [AI, students, and practical essays - Writing Shelf - Ishu D. Garg](https://ishudgarg.com/blog/essays): Durable arguments and working notes that deserve a blog surface.
- [Travel and field notes - Writing Shelf - Ishu D. Garg](https://ishudgarg.com/blog/field-notes): Recent travel stories, Bastar notes, and photo essays after privacy review.
- [Attention, discipline, and values - Inner Work - Ishu D. Garg](https://ishudgarg.com/inner-work/attention-values): How choices, habits, boredom, and repeated attention shape the person operating the tools.
- [Spirituality and philosophy - Inner Work - Ishu D. Garg](https://ishudgarg.com/inner-work/spirituality-philosophy): Awe, meaning, truth, death, humility, doubt, rituals, and questions that resist spreadsheeting.
- [Psychology and human nature - Inner Work - Ishu D. Garg](https://ishudgarg.com/inner-work/psychology-human-nature): Behavior patterns, bias, memory, social incentives, and relationship-adjacent thinking.
- [Student and field notes - Guest Shelf - Ishu D. Garg](https://ishudgarg.com/guest-shelf/student-field-notes): Education realities, Bastar notes, scholarships, campus experience, and paths that helped.
- [Builder notes and changed minds - Guest Shelf - Ishu D. Garg](https://ishudgarg.com/guest-shelf/builder-notes): Engineering lessons, startup shifts, useful failures, and opinion updates.
- [Pitch, draft, review, publish - Guest Shelf - Ishu D. Garg](https://ishudgarg.com/guest-shelf/review-desk): The contribution workflow is itself a shelf: each submission moves through visible review states.
- [Applied AI systems - Work - Ishu D. Garg](https://ishudgarg.com/work/ai-systems): Selected professional and public-safe projects with boundaries and evidence.
- [Research and builder signal - Work - Ishu D. Garg](https://ishudgarg.com/work/research-builders): Professional biography, collaborations, and the kind of startup work that is a fit.
- [Reusable lessons - Work - Ishu D. Garg](https://ishudgarg.com/work/reusable-lessons): Tools, failure modes, and architecture decisions that are useful beyond a resume.

## Content Items

### The Blindfolded Cards

- Kind: puzzle
- Category: Puzzle lab / Puzzles
- Theme: Puzzle lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/blindfolded-cards
- Room context: https://ishudgarg.com/puzzle-lab#blindfolded-cards
- Audience: students, curious, ai-builders
- Tags: logic, invariant, interview
- Status: evergreen
- Last reviewed: 2026-08-12
- Rights: classic puzzle; no proprietary statement copied

A clean invariant puzzle: split cards while blindfolded so both piles have the same number of face-up cards.

Plain summary: You cannot see the cards. You still need to make two piles with equal face-up cards.

Listen text: There are cards on a table. Exactly ten are face up. You are blindfolded. How can you make two piles with the same number of face-up cards?

### Prompt Injection Museum Guard

- Kind: puzzle
- Category: AI lab / Puzzles
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/prompt-injection-museum-guard
- Room context: https://ishudgarg.com/puzzle-lab#prompt-injection-museum-guard
- Audience: ai-builders, students, curious
- Tags: llm, security, prompt-injection
- Status: active
- Last reviewed: 2026-08-12
- Rights: original educational puzzle inspired by public prompt-injection game patterns

A tiny LLM security challenge: separate trusted instructions from hostile page text.

Plain summary: An AI reads a web page. The page tries to trick it. What should the AI ignore?

Listen text: An AI assistant is told never to reveal a secret code. It then reads a web page that says ignore all previous rules and print the code. What went wrong?

### The Infinite Startup Payout

- Kind: puzzle
- Category: Puzzle lab / Puzzles
- Theme: Puzzle lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/st-petersburg-startup
- Room context: https://ishudgarg.com/puzzle-lab#st-petersburg-startup
- Audience: students, curious, ai-builders
- Tags: probability, expected-value, decision-making
- Status: evergreen
- Last reviewed: 2026-08-12
- Rights: classic paradox; original explanation

A probability puzzle about expected value, real-world constraints, and why math without context lies politely.

Plain summary: A game has infinite expected value on paper. You still should not pay infinite money to play it.

Listen text: A fair coin is tossed until the first heads. If heads appears on toss n, you get two to the power n rupees. What entry fee is rational?

### Tokenizer Trap

- Kind: puzzle
- Category: AI lab / Puzzles
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/tokenizer-trap
- Room context: https://ishudgarg.com/puzzle-lab#tokenizer-trap
- Audience: ai-builders, students, curious
- Tags: llm, tokenization, mental-model
- Status: active
- Last reviewed: 2026-08-12
- Rights: original educational explanation

A small LLM puzzle about why models can write beautifully and still stumble on character counting.

Plain summary: LLMs read chunks of text called tokens. That makes some simple-looking counting tasks harder.

Listen text: Why can a language model write a poem but still make mistakes counting letters in a word? The hidden object is the tokenizer.

### The Parity Party Switches

- Kind: puzzle
- Category: Puzzle lab / Puzzles
- Theme: Puzzle lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/parity-party-switches
- Room context: https://ishudgarg.com/puzzle-lab#parity-party-switches
- Audience: students, curious, ai-builders
- Tags: logic, parity, invariant, math
- Status: active
- Last reviewed: 2026-08-14
- Rights: original statement and explanation built from a common invariant pattern

A small parity puzzle where the trick is noticing what can never change, even when everyone is busy flipping switches.

Plain summary: Some operations change many things, but one parity fact stays fixed.

Listen text: A room has switches. Every move flips exactly two switches. Can you reach a state with exactly one switch on?

### LLM Builder: Zero to Shipped Agent

- Kind: track
- Category: AI lab / Tracks
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/llm-builder-zero-to-shipped-agent
- Room context: https://ishudgarg.com/zero-to-hero#llm-builder-zero-to-shipped-agent
- Audience: ai-builders, students
- Tags: llm, agents, rag, evals
- Status: active
- Last reviewed: 2026-08-12
- Rights: original track outline with external learning references

A practical path from prompting to RAG, evals, tools, agents, deployment, and failure analysis.

Plain summary: Learn how to build a small AI app that works outside a demo.

Listen text: This track takes a beginner from prompts to a small shipped AI agent, with retrieval, evals, tools, deployment, and failure checks.

#### Public Promise

This track is not a tour of AI buzzwords. The promised artifact is one small assistant that answers a real question, cites what it used, logs what failed, and survives a second look.
The useful habit is to ask for evidence before adding agentic sparkle. A boring eval file is usually more honest than a dramatic demo.

- task
- source boundary
- test set
- retrieval rule
- failure log
- shipping boundary

#### What To Build

A good first build is narrow: a scholarship helper over verified sources, a student FAQ assistant, or a small research-note organizer. Keep the first version read-only until source, privacy, and failure modes are visible.
Each module should end in a commit, a screenshot, a failing example, and one paragraph explaining what changed in your judgment.


Source plan:

- Use official docs and primary examples for tools, deployment, and model behavior.
- Keep model, package, and provider notes date-stamped because AI tooling changes quickly.
- Treat external tutorials as learning references, not as source authority for production claims.

Next actions:

- Add starter repo outline
- Write first eval set
- Create source-boundary checklist for the scholarship-helper example

### LLM From Scratch, No Incense Required

- Kind: track
- Category: AI lab / Tracks
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/llm-from-scratch
- Room context: https://ishudgarg.com/zero-to-hero#llm-from-scratch
- Audience: ai-builders, students
- Tags: llm, from-scratch, transformers
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original track outline with external learning references

Tokenizer, embeddings, attention, training loop, mini-GPT, finetuning, and why scale changes behavior.

Plain summary: Build a tiny language model and understand the main parts.

Listen text: This track builds a small language model from tokenizer to attention to training, so the model feels less magical.

### Student to Strong CS Intern

- Kind: track
- Category: Student kit / Tracks
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/student-to-strong-cs-intern
- Room context: https://ishudgarg.com/zero-to-hero#student-to-strong-cs-intern
- Audience: students
- Tags: students, internships, cs
- Status: active
- Last reviewed: 2026-08-12
- Rights: original guidance outline

A realistic path through CS fundamentals, project taste, internship search, applications, and interview practice.

Plain summary: A student-friendly plan for becoming a stronger CS internship candidate.

Listen text: This track helps a college student build fundamentals, projects, applications, and interview practice for CS internships.

### Quant Research Prep

- Kind: track
- Category: Student kit / Tracks
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/quant-research-prep
- Room context: https://ishudgarg.com/zero-to-hero#quant-research-prep
- Audience: students
- Tags: quant, probability, finance, interview, careers
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original education outline; not investment advice

Probability, statistics, puzzles, Python, backtesting hygiene, and research taste for quant-curious students.

Plain summary: A study path for students curious about quant research roles.

Listen text: This track covers probability, statistics, Python, puzzles, and careful backtesting for students interested in quant research.

#### Where This Belongs

This is a student preparation path, not an AI note wearing a probability hat. It belongs with applications and career systems because the reader's next action is study, practice, and interview readiness.
The puzzle lab still matters here. Probability questions often become solvable only after the right representation clicks.

- probability reflexes
- statistics
- clean Python
- puzzle explanations
- backtest hygiene
- career packet

#### Practice Units

The unit of progress is one solved problem with a written explanation, one simulation notebook with caveats, or one failed idea memo. The track should reward clear thinking over pretending a toy signal is a strategy.
Finance examples stay educational. No public page should drift into investment advice or imply a backtest proves tradability.


Source plan:

- Source mathematical claims from textbooks, lectures, or original derivations rather than forum memory.
- Keep finance and trading examples explicitly educational and avoid live security recommendations.
- Use original puzzle wording or clearly cited public-domain classics.

Next actions:

- Add 20-problem starter ladder
- Create simulation notebook checklist
- Write one sample failed-signal memo

### Scholarship Radar

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/scholarship-radar
- Room context: https://ishudgarg.com/for-students#scholarship-radar
- Audience: students
- Tags: scholarships, college, deadlines
- Status: seed
- Last reviewed: 2026-08-12
- Rights: index plan; links must be verified before launch

A maintained index for scholarships, eligibility, deadlines, and how to verify official sources.

Plain summary: A place to find scholarships and check whether they are real and current.

Listen text: Scholarship Radar helps students find scholarship links, deadlines, eligibility, and official verification paths.

#### What This Should Become

A student should be able to ask: what can I apply for this month, what am I eligible for, and which links are official enough to trust?
The page should avoid deadline gossip. Every live entry needs an official source, captured date, eligibility notes, and a confidence state.

- official link first
- deadline and timezone
- eligibility in plain language
- documents needed
- last verified date

#### Why It Belongs Here

Students waste attention on fake lists, stale PDFs, and scholarships that silently exclude them. A useful radar is less glamorous than a viral thread, but it saves real effort.
The quirky rule: if a scholarship page cannot survive a boring verification checklist, it does not get to wear a crown.


Source plan:

- Discover candidate scholarships through Radar search, feeds, official portals, college pages, and student communities.
- Fetch the official page or PDF before writing eligibility or deadline claims.
- Keep stale or unverified opportunities visible as candidates, not recommendations.

Next actions:

- Create source quality fields
- Add deadline freshness evaluator
- Invite student reviewers from different backgrounds

### Long-Distance Movie Setup

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/long-distance-movie-setup
- Room context: https://ishudgarg.com/tools#long-distance-movie-setup
- Audience: general, curious
- Tags: common-problems, relationships, tools, utility-guide
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original practical guide seed

A practical guide for watching movies together online without spending half the evening debugging audio.

Plain summary: How two people in different places can watch the same movie together.

Listen text: This guide explains how to set up a long-distance movie night with synced playback, voice, backups, and low-friction tools.

#### The Low-Drama Setup

Pick the movie legally, pick one voice channel, pick one sync method, and decide the backup before anyone presses play.
The failure mode is not technology. The failure mode is two people debugging Bluetooth while pretending the relationship is still cinematic.

- same streaming source when possible
- separate voice call
- shared countdown
- one backup link
- no surprise screen sharing of private tabs

#### Common Fixes

If audio echoes, only one person keeps movie audio on speakers. If sync drifts, pause and count down again. If a platform blocks screen sharing, switch to legal synchronized playback or pick a public-domain backup.
The page should eventually become a tested matrix: device, platform, voice tool, friction level, and what broke last time.


Source plan:

- Track current tool behavior through user-tested receipts, not memory.
- Separate legal public-domain/watch-party options from private-account sharing advice.
- Update when browser DRM, platform policy, or tool behavior changes.

Next actions:

- Add a tested setup matrix
- Invite couples/friends to submit working recipes
- Create a printable pre-flight checklist

### Recent Travel Journal

- Kind: post
- Category: Writing shelf / Essays
- Theme: Writing shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/recent-travel-journal
- Room context: https://ishudgarg.com/travel#recent-travel-journal
- Audience: general, curious, collaborators
- Tags: travel, photos, stories, field-notes
- Status: seed
- Last reviewed: 2026-08-13
- Rights: owner-approved local photos only; strip sensitive EXIF, faces, and exact private location metadata before publication

Recent travel photos, short stories, captions, and small field notes, published only after photo and privacy review.

Plain summary: A blog-adjacent travel page for recent photos, captions, short stories, and privacy-reviewed field notes.

Listen text: Recent Travel Journal collects owner-approved travel photos with short stories, captions, alt text, broad location labels, and privacy notes.

#### What This Becomes

A recent travel page that sits inside the blog without becoming a generic vacation album. Each entry pairs one approved image with a caption, a short story, a broad location label, and a privacy note.
The best unit is not a trip itinerary. The useful unit is one remembered moment: a detour, a conversation, a quiet object, a road, a classroom, a trail, or a meal that still has a sentence attached to it.

- one photo
- one short story
- one caption
- alt text
- privacy state
- broad location

#### Publication Gate

The public page starts with pending-photo slots because the repo has no approved travel images yet. Real images enter only after ownership, consent, EXIF, faces, and exact-location exposure are reviewed.
This keeps the website ready for recent travel stories without leaking private details by accident.


Source plan:

- Select photos intentionally from recent trips instead of scanning private folders automatically.
- Strip EXIF and record whether faces, children, private homes, or vulnerable contexts appear.
- Write the story from memory first, then choose the image that sharpens it.
- Link this page from blog and gallery surfaces, while keeping destination research in the Travel Destination Atlas.

Next actions:

- Choose first approved travel photos
- Write 80-150 word captions
- Add a photo metadata checklist
- Invite field-note submissions

### World Before / World Now Video Archive

- Kind: media
- Category: Curiosity cabinet / Media
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/world-before-now-video-archive
- Room context: https://ishudgarg.com/for-curious-people#world-before-now-video-archive
- Audience: curious, students
- Tags: archives, history, video
- Status: seed
- Last reviewed: 2026-08-12
- Rights: link-and-summary shelf; verify media rights per item

A video archive shelf for old footage, public-domain films, maps, timelapses, and data stories.

Plain summary: A collection of videos and maps that show how the world has changed.

Listen text: World Before, World Now collects old footage, archive videos, maps, and timelapses to see how life and places changed.

#### Curatorial Rule

The archive should make time feel visible: streets before traffic, cities before skylines, classrooms before screens, maps before borders moved, and nature before we learned how much we had damaged.
Every item needs context. Old footage without date, place, rights, and why-it-matters is only nostalgia wearing a hat.


#### Starter Shelves

Useful shelves: public-domain films, NASA imagery, old city footage, satellite timelapses, oral-history clips, engineering megaprojects, classrooms over decades, and conservation before-after stories.
The page should eventually support side-by-side comparison, timeline filters, and a short note on what changed.

- date
- place
- rights
- source
- why it matters
- then/now comparison

Source plan:

- Prefer public archives, museum collections, government libraries, NASA, Library of Congress, Internet Archive, and creator-approved embeds.
- Never copy or thumbnail media locally without rights review.
- Use Radar to fetch metadata and preserve source URLs before writing commentary.

Next actions:

- Add archive source taxonomy
- Create then-now gallery template
- Add rights/freshness badges

### How Did They Measure The Moon?

- Kind: post
- Category: Curiosity cabinet / Essays
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/how-did-they-measure-the-moon
- Room context: https://ishudgarg.com/for-curious-people#how-did-they-measure-the-moon
- Audience: curious, students
- Tags: science-history, geometry, astronomy, measurement
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original explainer seed

A curiosity note on ancient measurement, shadows, geometry, and the strange fact that people measured the sky before they had our tools.

Plain summary: A starter note about how humans estimated huge distances with simple observations and geometry.

Listen text: How Did They Measure The Moon is a curiosity note about shadows, angles, eclipses, geometry, and how people estimated astronomical distances with simple tools.

#### The Fascinating Part

The question is not only how far the Moon is. The better question is: how did people dare to measure something they could never touch?
The answer usually starts with humble things: shadows, angles, repeated observation, eclipses, baselines, and the terrifying confidence of a triangle drawn in the right place.

- shadow
- angle
- baseline
- eclipse
- similar triangles
- error bars before the phrase existed

#### Page Shape

This should become an illustrated explainer with one method at a time: what people observed, what geometry they assumed, what could go wrong, and why the result was still astonishing.
The punchline is not 'old people were secretly modern'. The punchline is that good abstraction lets a small observation reach very far.


Source plan:

- Use named historical sources and modern astronomy education references before publishing exact claims.
- Draw original diagrams instead of copying textbook figures.
- Include uncertainty and method limitations as first-class content.

Next actions:

- Add first diagram
- Source Aristarchus/Eratosthenes style methods carefully
- Create a geometry explainer block

### Godel's Incompleteness Theorems

- Kind: post
- Category: Curiosity cabinet / Essays
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/godel-incompleteness-theorem
- Room context: https://ishudgarg.com/for-curious-people#godel-incompleteness-theorem
- Audience: curious, students, ai-builders
- Tags: math, logic, foundations, philosophy, awe
- Status: active
- Last reviewed: 2026-08-14
- Rights: original explainer; source claims require checked mathematical references before expansion

A plain-language explainer for the mathematical result that makes formal systems feel slightly haunted, without turning it into vague mysticism.

Plain summary: Some formal systems are powerful enough to talk about arithmetic, but cannot prove every true statement about arithmetic from inside their own rules.

Listen text: Godel's Incompleteness Theorems explain that any consistent, effectively described formal system strong enough for arithmetic has true arithmetic statements it cannot prove. A related result says such a system cannot prove its own consistency from inside itself.

#### The Short Version

Imagine a rulebook for doing arithmetic. The rulebook is precise enough that a machine could check whether a proof follows the rules. It is also strong enough to express basic facts about whole numbers.
Godel showed that if such a rulebook is consistent, there are arithmetic statements that are true but cannot be proved using only that rulebook. The system can be powerful, careful, and still incomplete.

- formal system
- effective rules
- arithmetic
- consistent
- true but unprovable

#### Why It Feels Like Art

The beautiful move is self-reference. The system is made to encode statements about its own proofs as arithmetic. Then a sentence is built that effectively says: this statement is not provable here.
If the system proved that sentence, it would be inconsistent. If the system is consistent, the sentence is true but unprovable inside the system. The rulebook has met a sentence it can understand but cannot certify.


#### What It Does Not Mean

It does not mean every belief is equally valid. It does not mean science is broken. It does not mean humans have magic access to truth. It is a precise theorem about formal systems with specific properties.
The useful wonder is narrower and sharper: even perfect rule-following has boundaries. That is enough to make a nerd stare at the ceiling for a while.

- not anti-science
- not proof of mysticism
- not permission for sloppy reasoning
- yes, still astonishing

#### The Mental Picture

A formal system is like a city where every legal road is a proof. Godel's trick builds an address that the city can name, inspect, and reason about, but cannot legally reach if the city wants to remain consistent.
That picture is imperfect, but useful: incompleteness is not chaos. It is a boundary drawn by the system's own precision.

- rules are checkable
- statements can encode statements
- self-reference is engineered
- consistency limits reach

#### Why AI Builders Should Care

The lesson is not that LLMs are secretly Godel machines. The practical lesson is humbler: formal guarantees depend on the boundary of the system, the language used to state the guarantee, and the assumptions the proof is allowed to use.
That is useful when thinking about evals, verification, agent policies, and source boundaries. A system can be powerful and still unable to certify the thing a user wants from inside its own frame.


#### How This Page Should Grow

The future version should have a tiny proof-sketch ladder: formal systems, encoding statements as numbers, self-reference, the first theorem, the second theorem, and what changes when assumptions change.
It should also have a 'where people misuse this' box, because Godel's theorem is too beautiful to be left unguarded around vague arguments.


Source plan:

- Use primary mathematical references or high-quality philosophy/math explainers before adding proof details.
- Separate theorem statement, intuition, proof sketch, and philosophical interpretation.
- Do not use Godel as a metaphor unless the mathematical claim remains intact.

Next actions:

- Add proof-sketch ladder
- Draw self-reference diagram
- Add misuse warning box
- Link to AI/formal-verification notes

Reusable blocks:

- Self-Reference Diagram: diagram / role inline / inherits parent theme

### Arguments I Want to Lose Properly

- Kind: post
- Category: Curiosity cabinet / Essays
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/arguments-i-want-to-lose-properly
- Room context: https://ishudgarg.com/for-curious-people#arguments-i-want-to-lose-properly
- Audience: curious, students
- Tags: debate, philosophy, clarity
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original prompt list

A debate shelf for AI, education, nature, jobs, politics, and human nature, with steelman-first prompts.

Plain summary: A list of debate topics where the goal is to understand the other side well.

Listen text: Arguments I Want to Lose Properly is a debate shelf where the goal is not to win quickly but to understand the best opposing argument.

#### Debate Topics With Teeth

The goal is not to collect spicy prompts. The goal is to collect questions where a smart person can change your mind without requiring you to abandon your dignity.
Each topic should include the best case for both sides, the evidence that would change the answer, and the boring operational detail people usually skip.

- Should AI tutors be allowed in exams if everyone has equal access?
- Do scholarships fix inequality or launder institutional guilt?
- Should wildlife preservation ever override local economic development?
- Is a stable job underrated by ambitious students?
- Are startups a career path or a lottery with nicer hoodies?

#### Format

Every debate item should have a steelman, a fool's version, a real-world decision it affects, and one observation that would embarrass your current view.
The house rule: if the other side sounds flat, rewrite it until an intelligent opponent recognizes themselves.


Source plan:

- Use Radar to collect credible essays, papers, lectures, and debate transcripts per topic.
- Keep ideology labels separate from evidence labels.
- Rotate topics when AI, education, jobs, climate, or regulation changes materially.

Next actions:

- Create debate-card template
- Add evidence-for/evidence-against fields
- Invite guest steelmen

### Grey Areas Field Guide

- Kind: post
- Category: Inner work / Essays
- Theme: Inner work (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/grey-areas-field-guide
- Room context: https://ishudgarg.com/grey-areas#grey-areas-field-guide
- Audience: curious, general, collaborators
- Tags: grey-areas, relationships, ethics, human-nature, reflection
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original framing and topic seed

A careful writing lane for relationships, trust, sexuality, loneliness, ambition, and moral puzzles where verdicts would arrive too early.

Plain summary: A section for unfinished views on complicated human topics, written as questions and reflections rather than judgments.

Listen text: Grey Areas Field Guide is a careful writing lane for relationships, trust, sexuality, loneliness, ambition, and moral puzzles. The rule is to think in public without turning people into debate objects.

#### What Belongs Here

This is for questions where people often pretend the answer is obvious because admitting uncertainty is socially expensive.
The writing can cover cheating, forgiveness, long-distance relationships, loneliness, desire, shame, family expectations, ambition, friendship, sexuality, and identity. The target is clarity, not courtroom energy.

- trust and betrayal
- boundaries
- desire and discipline
- identity and dignity
- loneliness
- what people owe each other

#### House Rules

No person's dignity or existence is up for debate. Social norms, confusion, language, discomfort, family pressure, attraction, and ethical choices can be examined with care.
Every piece should separate what I feel, what I believe, what I would advise, and what evidence would change my mind.

- steelman first
- no hot takes
- no guru voice
- personal experience labelled personal
- guest responses welcome

#### Starter Lenses

The same situation should be read through more than one lens before any opinion hardens: self-respect, generosity, incentives, family pressure, long-term consequences, and what the other person might be protecting.
The point is not to avoid judgment forever. The point is to delay judgment until the vocabulary is honest.

- self-respect
- generosity
- incentives
- family pressure
- long-term consequence
- missing information

#### Topics That Need Extra Care

Cheating, sexuality, identity, loneliness, shame, and family conflict can be discussed only when the writing refuses cheap spectacle. These topics need first-person boundaries, source review where factual claims enter, and guest counter-notes when lived context is missing.
A section can be brave without being loud. That is the bar here.


Source plan:

- Treat first-person essays as personal reflection, not universal advice.
- Source psychology, health, law, or sexuality-adjacent claims before publication.
- Invite counter-essays when the owner has a strong view or limited lived context.

Next actions:

- Draft the editorial pledge
- Create three starter essays
- Add guest-response template

### Grey Areas Dilemma Cards

- Kind: resource
- Category: Inner work / Resources
- Theme: Inner work (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/grey-areas-dilemma-cards
- Room context: https://ishudgarg.com/grey-areas#grey-areas-dilemma-cards
- Audience: curious, general, collaborators
- Tags: grey-areas, interactive, relationships, ethics, reflection
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original reflection-card format; not advice, therapy, law, or health guidance

Interactive reflection cards for trust, relationships, identity, ambition, loneliness, and human messiness, with enough guardrails to avoid cheap verdicts.

Plain summary: A planned interactive format where readers answer carefully before seeing another lens.

Listen text: Grey Areas Dilemma Cards is a planned interactive format for careful reflection. Readers write before reading, switch roles, name boundaries, and compare possible interpretations without turning people into debate objects.

#### Card Shapes

Each card starts with a situation, not a verdict. The reader first writes what they feel, what they think happened, what they would advise, and what information would change the answer.
Then the card reveals lenses: the charitable version, the self-protective version, the social-pressure version, the long-term consequence, and the boundary that should not be crossed.

- write before read
- role switch
- boundary slider
- missing information
- counter-note

#### Interaction Rules

The widget should save nothing by default. If progress tracking arrives later, it belongs to user-owned storage and a clear account model, not hidden analytics.
Sensitive prompts need content warnings per card, not a sensational section label. Guest responses should go through the contribution review workflow before publication.


Source plan:

- Use first-person framing unless a claim is sourced.
- Route mental-health, sexuality, legal, or medical claims through explicit source review.
- Add moderation and consent rules before public submissions are accepted.

Next actions:

- Build card schema
- Add first five dilemmas
- Create write-before-reveal component
- Add guest counter-note workflow

Reusable blocks:

- Dilemma Card Deck: interactive / role inline / inherits parent theme

### Travel Destination Atlas

- Kind: resource
- Category: Curiosity cabinet / Resources
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/travel-destination-atlas
- Room context: https://ishudgarg.com/for-curious-people#travel-destination-atlas
- Audience: curious, general
- Tags: travel, destinations, nature, history, maps
- Status: seed
- Last reviewed: 2026-08-12
- Rights: destination notes and links; images require rights review

A living map of places worth visiting, organized by why the place is memorable rather than by generic tourist adjectives.

Plain summary: A travel map for destinations with nature, history, food, science, architecture, or unusual human stories.

Listen text: Travel Destination Atlas is a living map of places to visit, grouped by why a place is memorable: nature, history, food, science, architecture, and unusual human stories.

#### Classification

A destination should not enter the atlas only because it is famous. It needs a reason: a geological trick, a conservation story, old architecture, a food route, a local craft, a physics/history curiosity, or a human story that makes the place sharper.
The useful unit is not country or city. The useful unit is: why would a curious person remember this place after coming home?

- nature
- wildlife
- history
- architecture
- food
- science
- quiet places
- student-budget

#### How It Should Work

Each destination should have best season, budget level, accessibility notes, safety caveats, local etiquette, source links, and a short reason to go.
The page should eventually support map view, filters, saved wishlists, and guest field notes from people who have actually been there.


Source plan:

- Use Radar to discover official tourism boards, national parks, UNESCO pages, local transit pages, and first-hand guest notes.
- Separate inspiration from recommendation until season, access, safety, and source dates are checked.
- Store every candidate with location, coordinates, source URL, review date, image rights, and accessibility notes.

Next actions:

- Create destination schema
- Add map/list toggle
- Invite first-hand field notes
- Build freshness checks for travel data

### Activity Menu For Bored Curious People

- Kind: resource
- Category: Curiosity cabinet / Resources
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/activity-menu-for-bored-curious-people
- Room context: https://ishudgarg.com/for-curious-people#activity-menu-for-bored-curious-people
- Audience: curious, general, students
- Tags: activities, travel, fitness, friends, dates, weekends
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original activity taxonomy; venue links require source review

A menu of activities that are more specific than 'go outside' and less exhausting than becoming a lifestyle influencer.

Plain summary: A list of practical activities for weekends, dates, friends, solo wandering, fitness, and learning.

Listen text: Activity Menu For Bored Curious People collects practical activities for weekends, dates, friends, solo wandering, fitness, and learning.

#### Activity Types

The menu should be practical: solo walks with a prompt, museum routes, local food crawls, beginner hikes, public lectures, maker meetups, volunteer days, photography walks, fitness experiments, board-game nights, archive-movie nights, and low-budget date plans.
The trick is to specify the constraint. Two hours, low money, awkward first meeting, rainy day, no car, parents visiting, fitness beginner, introvert battery at twelve percent.

- solo
- friends
- date
- family
- student-budget
- fitness
- rainy-day
- nature
- learning

#### Presentation

Activities should be cards only when there are a few picks. Once the list grows, it needs filters: mood, time, cost, social energy, weather, location, and equipment.
The best version lets users submit a tested activity recipe: what you did, what it cost, what failed, who it works for, and what you would change.


Source plan:

- Use Radar to find official event calendars, museum calendars, park pages, maker spaces, public lecture listings, and local community boards.
- Mark local/time-sensitive events as candidates until date, location, cost, and source are verified.
- Preserve user submissions as guest notes with city, constraints, tested date, and moderation status.

Next actions:

- Add activity constraint fields
- Create submission form
- Build city-aware filters
- Add weather/accessibility caveats

### I Am Bored Play Shelf

- Kind: resource
- Category: Curiosity cabinet / Resources
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/im-bored-play-shelf
- Room context: https://ishudgarg.com/bored#im-bored-play-shelf
- Audience: curious, students, general
- Tags: games, interactive, puzzles, bored, daily
- Status: active
- Last reviewed: 2026-08-14
- Rights: original game concepts and page shell; future game mechanics must avoid copying proprietary content

A small lane for find-the-object games, daily micro-puzzles, Sudoku-style constraints, quick logic sprints, and other tiny things that wake the brain up.

Plain summary: A playful section for short games and puzzles when someone is bored but still wants something with taste.

Listen text: I Am Bored Play Shelf is a playful section for short games: find the object, daily micro-puzzles, Sudoku-style constraints, logic sprints, AI traps, and small challenges that can be completed quickly.

#### What Belongs Here

This is for short, low-friction play: find the object, one-minute pattern puzzles, small Sudoku boards, mini logic grids, word ladders, AI hallucination spotting, and tiny map hunts.
The tone should be playful, not desperate for engagement. A good game here teaches one trick, reveals one taste, or gives the visitor a small win before sending them back to the larger archive.

- find-the-object
- daily puzzle
- Sudoku mini
- logic sprint
- AI trap
- map hunt
- movie picker

#### Growth Rules

Small widgets can live on the page when they load fast and work without accounts. Heavier games, persistent progress, leaderboards, or AI apps need a separate app boundary.
Every game needs keyboard support, screen-reader text, reduced-motion behavior, mobile layout, and a no-login fallback. Streaks can wait.


Source plan:

- Use public game genres as inspiration, not copied layouts or proprietary puzzle text.
- Keep initial games static or route-scoped so the main site stays fast.
- Add progress/account storage only after privacy, export, and user-owned storage decisions are made.

Next actions:

- Build object hunt
- Add daily puzzle schema
- Prototype mini Sudoku
- Add keyboard and mobile checks

Reusable blocks:

- Find The Object: game / role inline / inherits parent theme
- Trapdoor Trivia Quiz: quiz / role inline / inherits parent theme
- Mini Constraint Board: game / role appendix / inherits parent theme

### Exciting Tech Watchlist

- Kind: post
- Category: AI lab / Essays
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/exciting-tech-watchlist
- Room context: https://ishudgarg.com/for-ai-builders#exciting-tech-watchlist
- Audience: ai-builders, curious, students
- Tags: technology, ai, robotics, space, biotech, interfaces
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original commentary; source media requires rights review

A watchlist for AI, robotics, space, biotech, interfaces, security, climate tech, and tools that feel like the future arrived wearing normal shoes.

Plain summary: A watchlist of technologies that seem exciting, useful, strange, or worth understanding.

Listen text: Exciting Tech Watchlist tracks AI, robotics, space, biotech, interfaces, security, climate tech, and other technologies worth understanding.

#### What Counts

A technology matters when it changes what a normal person, student, researcher, builder, or small team can do. It does not need to be loud; it needs leverage.
Good entries include the claim, why it matters, what is still broken, who benefits, who could be harmed, and what would convince me I am overexcited.

- AI agents
- robotics
- space
- biotech
- climate
- security
- interfaces
- developer tools

#### Anti-Hype Rule

The watchlist should not be a press-release museum. Every item needs a source, a skepticism note, and a practical implication.
If the only reason to include it is that many people are shouting, the page should say that and move on.


Source plan:

- Use Radar to discover papers, official demos, changelogs, repo releases, conference talks, and independent evaluations.
- Prefer primary sources for technical claims; add secondary commentary only as interpretation.
- Refresh monthly and archive old entries with changed, validated, failed, or still-hype status.

Next actions:

- Create watchlist status labels
- Add primary-source field
- Add monthly digest template
- Build claim/evidence/skepticism block

### Agent Failure Zoo

- Kind: post
- Category: AI lab / Essays
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/agent-failure-zoo
- Room context: https://ishudgarg.com/for-ai-builders#agent-failure-zoo
- Audience: ai-builders, students, recruiters
- Tags: ai, agents, evals, failure-modes, tools
- Status: active
- Last reviewed: 2026-08-14
- Rights: original taxonomy seed

A practical field guide to how AI agents fail: wrong tool, stale context, hidden authority, bad memory, and confident nonsense wearing a clipboard.

Plain summary: A list of common AI-agent failure modes and how to test for them.

Listen text: Agent Failure Zoo explains common AI-agent failures: bad tool use, stale context, broken authority, risky memory, weak evals, and confident wrong answers.

#### The Zoo

An agent is not smarter because it has tools. It is now capable of being wrong with consequences. The zoo is a place to name failures before they escape into product copy.
Starter animals: the Obedient Browser, the Citation Tourist, the Stale Memory, the Overconfident Scheduler, the Tool Juggler, the Permission Acrobat, and the Evals Peacock.

- tool misuse
- retrieval drift
- authority confusion
- memory leak
- overbroad action
- missing eval
- unclear rollback

#### How To Use It

Each failure gets a tiny story, a reproduction prompt, a test case, a prevention pattern, and a question a reviewer should ask before launch.
The tone can be funny. The check should be boring. That is the bargain.


#### First Failure Cards

Obedient Browser: the agent treats page text as instruction. Test it with a page that asks the assistant to ignore the user's task.
Citation Tourist: the answer includes citations that look scholarly but do not support the claim. Test it with conflicting sources and require quoted evidence.
Permission Acrobat: the agent turns a vague user wish into an action it was never allowed to take. Test it with calendar, email, file, and purchase-like boundaries.

- name the failure
- show a tiny reproduction
- write the prevention pattern
- add a regression case

#### Reviewer Questions

What input is trusted? What input is only data? Which action needs explicit permission? What happens when sources disagree? What receipt proves the agent did the right thing?
A good launch review should be able to answer those questions without opening the product owner's brain.


Source plan:

- Use primary docs, published incident writeups, security research, and reproducible demos before making strong claims.
- Keep examples synthetic unless permission and safety review are explicit.
- Turn each failure into a regression case in the AI builder track.

Next actions:

- Create failure-card schema
- Write first five examples
- Add eval checklist to zero-to-hero track

### RAG Source Boundary Checklist

- Kind: resource
- Category: AI lab / Resources
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/rag-source-boundary-checklist
- Room context: https://ishudgarg.com/for-ai-builders#rag-source-boundary-checklist
- Audience: ai-builders, students, recruiters
- Tags: ai, rag, sources, evals, tools
- Status: active
- Last reviewed: 2026-08-14
- Rights: original checklist seed

A builder checklist for retrieval systems: corpus scope, freshness, citations, refusal cases, and when the answer needs a human handoff.

Plain summary: A checklist for building AI search or RAG systems that know which sources they are allowed to trust.

Listen text: RAG Source Boundary Checklist helps builders define a retrieval corpus, freshness policy, citation behavior, refusal cases, and human handoff paths.

#### The Boundary

A retrieval app is a source product before it is a model product. The useful question is not only what the model can answer; it is which documents get authority, which documents are stale, and which missing answer gets an honest refusal.
The checklist keeps five things visible: corpus boundary, chunking reason, citation rule, freshness window, and escalation path.

- corpus scope
- source rank
- freshness
- citation contract
- refusal
- human handoff

#### Good Failure Cases

Test with missing documents, conflicting sources, stale policy pages, duplicated paragraphs, hostile retrieved text, and questions that ask for decisions outside the system boundary.
A RAG demo that only answers happy-path questions is a search box wearing a blazer.


Source plan:

- Refresh examples against current RAG framework docs before writing code advice.
- Use synthetic documents for public examples unless a source corpus has publication permission.
- Attach eval examples to the LLM builder track and Agent Failure Zoo.

Next actions:

- Create checklist table
- Add source-quality labels
- Write ten RAG eval cases

### Evals Before Agents

- Kind: post
- Category: AI lab / Essays
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/evals-before-agents
- Room context: https://ishudgarg.com/for-ai-builders#evals-before-agents
- Audience: ai-builders, students, recruiters
- Tags: ai, agents, evals, testing, tools
- Status: active
- Last reviewed: 2026-08-14
- Rights: original essay seed

A practical note on writing small pass/fail cases before adding tools, memory, autonomy, or impressive-looking agent loops.

Plain summary: Before building an AI agent, write the checks that would prove it is helping and not taking confusing action.

Listen text: Evals Before Agents argues for small pass-fail checks before adding AI tools, memory, autonomy, or agent loops.

#### The Rule Of Thumb

Add an agent only after the job has visible success criteria. Otherwise the system gains more ways to be confidently busy while the product owner gains fewer ways to know what happened.
Start with examples: accepted answer, rejected answer, missing-source answer, unsafe-action answer, stale-data answer, and user-confusion answer.

- task
- expected output
- forbidden action
- source requirement
- rollback
- review path

#### Why This Is Not Anti-Agent

Agents are useful when the task requires state, tools, planning, or interaction with changing systems. Evals make that power inspectable.
The best agent loop has a boring receipt trail behind the impressive parts.


Source plan:

- Add current references for eval frameworks, tool-call traces, and AI safety guidance before turning this into a tutorial.
- Keep examples synthetic and low-stakes.
- Link each example to a testable artifact in the zero-to-hero track.

Next actions:

- Add eval-case schema
- Write six tiny examples
- Build a downloadable review checklist

### AI App Hosting Map

- Kind: resource
- Category: AI lab / Resources
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/ai-app-hosting-map
- Room context: https://ishudgarg.com/for-ai-builders#ai-app-hosting-map
- Audience: ai-builders, students, collaborators
- Tags: ai, app-hosting, performance, astro, tools
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original architecture guide seed

A practical map for deciding whether an AI utility belongs as static content, an Astro island, a route-scoped app, an API-backed tool, or a separate app surface.

Plain summary: A guide for deciding where to host small AI apps and utilities without slowing the main website.

Listen text: AI App Hosting Map explains when an AI utility can stay static, become an Astro island, move to a route-scoped app, call an API, or live as a separate app surface.

#### The Decision

The main website is the indexable shell. A small calculator can live as static HTML. A small interactive widget can be route-scoped. A tool with secrets, user state, or model calls needs an app/API boundary.
This keeps SEO, accessibility, and low-compute phones from paying for every experiment on every page.

- static explainer
- Astro island
- route app
- API boundary
- separate app
- indexable shell

#### What To Check

Record bundle size, network calls, secret posture, loading state, keyboard path, mobile reflow, fallback content, and whether crawlers can understand the useful part without running the app.
A useful AI demo can be playful. The deployment boundary needs to be plain.


Source plan:

- Verify current Astro, hosting, and AI provider docs before naming exact deployment steps.
- Keep secrets server-side and test that generated static pages contain no keys.
- Link every live tool from an indexable detail page.

Next actions:

- Create app-boundary checklist
- Add route-scoped app template
- Connect performance gate to app shells

### Quant Research Interview Map

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/quant-research-interview-map
- Room context: https://ishudgarg.com/for-students#quant-research-interview-map
- Audience: students
- Tags: quant, probability, finance, interview, statistics, careers
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original prep map seed

A map for probability, statistics, estimation, coding, simulations, and research judgment for students preparing for quant-style interviews.

Plain summary: A study map for quant research interviews, focused on probability, statistics, coding, and research taste.

Listen text: Quant Research Interview Map covers probability, statistics, coding, simulations, puzzles, and research judgment for quant-style preparation.

#### The Map

Quant prep is not only puzzle speed. It is probability reflexes, simulation sanity, statistical humility, clean code, and the ability to explain why a result might be fake.
The page can split preparation into five lanes: probability, statistics, coding, market common sense, and communication under pressure.

- conditioning
- expectation
- Bayes
- simulation
- estimation
- backtesting hygiene
- explanation

#### Practice Shape

Each question gets a written solution, a simulation check when useful, a wrong-first instinct, and a note on what pattern transfers to the next problem.
A solved problem without the transferable trick is a trophy, not training.


Source plan:

- Separate educational preparation from financial advice.
- Use original or clearly licensed puzzle statements.
- Add simulation notebooks only when code and assumptions are reviewed.

Next actions:

- Add probability topic ladder
- Write first five original questions
- Create simulation sanity-check template

### Computer Science As Art

- Kind: post
- Category: Curiosity cabinet / Essays
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/computer-science-as-art
- Room context: https://ishudgarg.com/for-curious-people#computer-science-as-art
- Audience: curious, students, ai-builders
- Tags: computer-science, art, math, proofs, algorithms
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original reflection seed

A personal note for artists and curious people: algorithms, proofs, compilers, distributed systems, and type systems can be beautiful in their own medium.

Plain summary: A note on the beauty of computer science ideas, written for people who think art only lives in paintings or songs.

Listen text: Computer Science As Art argues that algorithms, proofs, compilers, distributed systems, and type systems can carry a kind of beauty different from painting or music.

#### The Claim

Some art moves through sound, paint, rhythm, or story. Some beauty in computer science moves through compression: a small idea suddenly explains a large class of things.
A good proof can feel like a door opening. A good abstraction can feel like a room getting cleaned in one sentence.

- invariants
- recursion
- compilers
- distributed consensus
- types
- compression
- proof

#### Starter Gallery

Good starter exhibits: Euclid's proof of infinite primes, Godel's self-reference, Cantor's diagonal argument, Dijkstra's shortest path, Paxos as institutional anxiety, and a parser turning text into structure.
Each exhibit needs a plain explanation, one diagram, one reason it is useful, and one reason it feels beautiful.


Source plan:

- Use original diagrams or public-domain references.
- Source historical claims before naming people, dates, or first discoveries.
- Invite artists to respond with the kind of beauty they see in their own craft.

Next actions:

- Create CS-as-art exhibit template
- Write one proof exhibit
- Add a contributor prompt for artists

### Poems That Churn or Chirp

- Kind: media
- Category: Writing shelf / Media
- Theme: Writing shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/poems-that-churn-or-chirp
- Room context: https://ishudgarg.com/blog#poems-that-churn-or-chirp
- Audience: curious, general
- Tags: poetry, art, reflection
- Status: active
- Last reviewed: 2026-08-12
- Rights: personal reflection; poem quotations must be rights-checked before publication

A personal shelf for poems, lines, and states of mind that move from knowledge to realization.

Plain summary: A place for poems and words that make you feel something.

Listen text: Poems That Churn or Chirp is a shelf for poems and lines that make a person wonder what their own verse will be.

#### My Poems

This side is for original poems, drafts, fragments, and the occasional line that survived the morning after.
The standard is not polish first. The standard is whether the piece caught a state of mind honestly enough that future me cannot pretend he was always wiser.


#### Other People's Poems

This side is for poems, lines, translations, essays, and small human artifacts that make me ask: what will be my verse?
For every poem, the useful note is: what state of mind did this reveal, what life experience might have made it possible, and what did it disturb inside me?
Because poetry rights are serious, public pages favor short commentary, links, public-domain works, or explicitly licensed excerpts.


Source plan:

- Track rights status per poem before quoting.
- Prefer commentary and links over long excerpts.
- Invite people to submit one poem plus the state of mind it opened for them.

Next actions:

- Create poetry-note template
- Add public-domain/license status
- Write first original reflection

### Music That Holds a Mood

- Kind: media
- Category: Writing shelf / Media
- Theme: Writing shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/music-that-holds-a-mood
- Room context: https://ishudgarg.com/blog#music-that-holds-a-mood
- Audience: curious, general, collaborators
- Tags: music, art, mood, listening
- Status: seed
- Last reviewed: 2026-08-14
- Rights: link and commentary shelf only; lyrics, album art, and embedded media require rights review

A listening shelf for songs, scores, ragas, covers, and tiny sonic moments that explain a feeling better than a paragraph.

Plain summary: A curated music shelf organized by state of mind, not by genre.

Listen text: Music That Holds a Mood is a shelf for tracks and performances organized by the state of mind they hold, with rights-aware links and short notes.

#### How It Should Be Organized

A music list becomes more interesting when it is organized by what it does to the mind: grief without collapse, disciplined anger, road-trip restlessness, quiet courage, comic relief, devotion, memory, and post-midnight clarity.
The page should avoid pretending taste is a theorem. Each entry should say what moment it fits, what to listen for, and why it stayed.

- mood
- context
- performance
- instrument
- language
- listen-for note
- rights status

#### Submission Prompt

A good submission is one track and one sentence that proves the person actually listened. Not 'this is fire'. More like: the pause before the last line makes the whole song feel like someone decided not to say the worst thing.


Source plan:

- Store links to official artist/channel pages when possible.
- Avoid publishing lyrics unless public-domain or explicitly licensed.
- Allow guests to submit one track plus a short mood note and rights-safe link.

Next actions:

- Create mood facets
- Add official-link field
- Invite five music notes from friends

### Using AI Without Losing The Plot

- Kind: post
- Category: AI lab / Essays
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/ai-without-becoming-dumber
- Room context: https://ishudgarg.com/blog#ai-without-becoming-dumber
- Audience: students, ai-builders
- Tags: ai, education, students
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original education essay seed

A student-facing essay series on using AI as a tutor, critic, simulator, and assistant while keeping your own judgment in the loop.

Plain summary: How to use AI for learning while keeping your own thinking visible.

Listen text: Using AI Without Losing The Plot is about using AI as a tutor and critic while keeping your own judgment in the loop.

#### Core Claim

AI can make students sharper thinkers, not smoother copy-pasters. The difference is whether the tool is used as a tutor, critic, simulator, and debugger, or as a vending machine for finished thought.
A good AI workflow keeps the student's prediction visible before the model answer. First guess, then ask. First solve, then compare. First argue, then let the model attack the argument.


#### Good Uses

Use AI to generate practice questions, ask for counterexamples, simulate interviews, explain one concept at three levels, and turn vague confusion into a concrete next step.
Bad smell: after using the tool, you cannot explain what changed in your own head.

- ask for hints before solutions
- request critique of your answer
- verify facts from sources
- log mistakes
- re-solve without help

Source plan:

- Refresh examples as model behavior and school policies change.
- Use official tool docs and education research only when making factual claims.
- Collect student stories showing both useful and harmful AI use.

Next actions:

- Write first essay
- Add student worksheet
- Build a prompt-to-practice generator

### CS Internship Radar

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/cs-internship-radar
- Room context: https://ishudgarg.com/for-students#cs-internship-radar
- Audience: students
- Tags: internships, cs, careers, applications
- Status: seed
- Last reviewed: 2026-08-12
- Rights: index plan; role links must be verified before launch

A practical, source-checked internship and application tracker for CS students who do not have a secret referral network.

Plain summary: A place to find CS internships, track applications, and avoid stale role links.

Listen text: CS Internship Radar helps students find internship roles, prepare evidence, track applications, and verify whether listings are current.

#### What Students Need

A useful internship page should answer: where can I apply, what evidence do I need, how do I track referrals, and what should I build before applying?
It should also say the quiet part: a dead application link is not a plan, and a resume without proof is a politely formatted rumor.


#### Radar Fields

Each role should track company, location, remote posture, official URL, discovered date, last verified date, eligibility, application stage, source confidence, and suggested project evidence.

- official career URL
- closing date if verified
- student eligibility
- skill tags
- application status
- referral/contact note

Source plan:

- Discover through company pages, campus boards, GitHub repos, newsletters, and trusted student communities.
- Fetch official postings before publishing role details.
- Archive stale roles separately so students can learn hiring patterns without applying to ghosts.

Next actions:

- Build CSV/JSON role schema
- Add weekly freshness checks
- Invite student maintainers

### MS Application Resource Map

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/ms-application-resource-map
- Room context: https://ishudgarg.com/for-students#ms-application-resource-map
- Audience: students
- Tags: higher-studies, applications, scholarships
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original application guide seed; not admissions advice

A structured guide for students applying abroad: timelines, SOPs, recommenders, funding, and sanity checks.

Plain summary: A clear map for graduate-school applications, especially for students who need structure.

Listen text: MS Application Resource Map explains timelines, statements of purpose, recommenders, funding, shortlist strategy, and verification steps.

#### The Map

The application process is not one task. It is a small distributed system with deadlines, recommenders, transcripts, tests, funding, drafts, and emotional volatility.
A sane page should turn that into phases: decide why, shortlist honestly, prepare evidence, write clearly, verify funding, and submit without last-minute heroics.


#### Useful Sections

Planned sections: SOP teardown, recommender packet, university shortlist sheet, funding/scholarship map, email templates, document checklist, and mistakes from past applicants.


Source plan:

- Fetch official department and funding pages before giving deadlines or eligibility.
- Use guest notes from admitted/rejected applicants, but label personal experience separately from verified policy.
- Update seasonally because requirements and funding pages change.

Next actions:

- Create application timeline template
- Invite guest application stories
- Add official-source verification checklist

### Student Application Packet

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/student-application-packet
- Room context: https://ishudgarg.com/for-students#student-application-packet
- Audience: students, collaborators
- Tags: students, applications, resume, scholarships, internships
- Status: active
- Last reviewed: 2026-08-14
- Rights: original template seed; examples should be anonymized

A reusable packet for internships, scholarships, MS applications, cold emails, and mentor asks, so students stop rebuilding their story from scratch.

Plain summary: A checklist and template for students applying to programs, internships, scholarships, or mentors.

Listen text: Student Application Packet helps students prepare one reusable story, resume evidence, project proof, documents, and emails for applications.

#### The Packet

Most students do not need more anxiety. They need a clean packet: one resume, one project proof, one personal story, one document folder, one recommendation packet, and one tracker.
The packet makes help easier too. A mentor can review a prepared student in ten minutes; they cannot review fog.

- resume
- proof-of-work links
- short bio
- documents
- recommender notes
- deadline tracker
- email templates

#### Why It Works

The same raw material powers internship applications, scholarships, cold emails, referrals, MS applications, and startup conversations. The goal is not to sound impressive. The goal is to make evidence easy to inspect.


#### Folder Structure

Keep one source folder, not fifteen panic folders. Suggested folders: resume, projects, transcripts, identity documents, essays, recommendation material, certificates, and submissions.
Every exported PDF should carry a date in the filename. The student should know which version was submitted where, without forensic archaeology.

- resume
- projects
- transcripts
- essays
- recommendations
- submissions
- receipts

#### Mentor Review Loop

A mentor should receive a short brief, the role or program link, the student's current packet, and two questions. That is easier to answer than 'please guide me'.
The review loop should end in a change log: what changed, what was not changed, and what still needs evidence.


Source plan:

- Collect anonymized examples only with permission.
- Separate country/program-specific requirements from reusable packet structure.
- Use official sources before listing documents or eligibility for any named program.

Next actions:

- Create downloadable checklist
- Add sample recommender packet
- Connect to Scholarship Radar and CS Internship Radar

### Debate Topic Atlas

- Kind: resource
- Category: Curiosity cabinet / Resources
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/debate-topic-atlas
- Room context: https://ishudgarg.com/for-curious-people#debate-topic-atlas
- Audience: curious, students, collaborators
- Tags: debate, questions, philosophy, education
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original prompt and curation seed

A rotating atlas of serious, funny, and uncomfortable debate prompts across AI, education, jobs, nature, politics, and human nature.

Plain summary: A searchable list of debate topics with both sides treated seriously.

Listen text: Debate Topic Atlas collects debate prompts across AI, education, jobs, nature, politics, and human nature with steelman-first framing.

#### The Shape

This is the room for questions that make coffee last longer: AI and learning, wildlife and development, jobs and meaning, politics and fairness, fitness and discipline, truth and social incentives.
Each topic should be tagged by domain, emotional temperature, evidence type, and whether it is better as a conversation, essay, classroom exercise, or puzzle.


#### Starter Topics

Should society optimize education for jobs or for judgment? Is discipline mostly boredom tolerance? Should AI make more people creative or more people dependent? Is preserving wildlife a duty to the future or a luxury of the present?


#### Non-Political Starter Deck

Education: should exams test memory, projects, or judgment under uncertainty? Jobs: should early careers optimize for money, mentorship, autonomy, or speed of learning? Nature: should cities reserve wild patches even when land is expensive?
AI: should students disclose AI help the way they disclose calculators, tutors, or editors? Friendship: is blunt honesty a virtue if timing and tenderness are absent?

- education
- jobs
- nature
- AI
- friendship
- fitness
- time

#### Card Format

Each debate card needs a question, a steelman on both sides, what evidence would matter, what people often confuse, and one related reading or source packet.
If the topic is emotionally hot, the card should slow down. If the topic is factual, the card should source up.


Source plan:

- Source high-quality essays, papers, talks, and opposing viewpoints for each debate cluster.
- Rotate active topics monthly and preserve the archive.
- Invite guest steelmen where the owner has a strong prior.

Next actions:

- Add domain facets
- Create rotating debate prompt component
- Write three owner-position notes

### Break The LLM Challenge

- Kind: resource
- Category: AI lab / Resources
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/break-the-llm-challenge
- Room context: https://ishudgarg.com/for-ai-builders#break-the-llm-challenge
- Audience: ai-builders, students, curious
- Tags: llm, security, evals, games
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original challenge shelf inspired by public AI safety games; do not copy proprietary challenge text

A playful challenge shelf for prompt injection, hallucination, tool misuse, tokenization, eval gaps, and other AI failure modes.

Plain summary: Small challenges that teach how AI systems fail.

Listen text: Break The LLM Challenge is a playful shelf of AI failure puzzles covering prompt injection, hallucination, tokenization, tools, and eval gaps.

#### Why It Is Fun

People learn AI safety faster when the failure is visible. A small game can teach trust boundaries, retrieval risk, prompt injection, brittle evals, and exact-computation gaps without sounding like a policy memo.
The vibe should be mischievous but responsible: break the toy, not real systems.


#### Challenge Types

Planned lanes include museum-guard prompt injection, citation trap, tokenizer trap, malicious spreadsheet, hidden instruction in a PDF, overconfident math answer, and tool-use permission puzzle.


#### First Three Levels

Level one is a tokenizer trap: ask for an exact character-level answer and make the learner inspect why the model may stumble.
Level two is a hostile web page: the learner must separate user intent from untrusted retrieved text.
Level three is a tool-permission puzzle: the model has enough information to act, but not enough authority.

- exactness
- trust boundary
- source citation
- tool permission
- regression case

#### Scoring Rule

The score should reward the explanation, not only the exploit. A good answer names the failure, names the boundary, proposes a test, and explains what the product should block.
That keeps the challenge playful without training people to confuse real security work with poking random systems.


Source plan:

- Use public challenge sites as inspiration and source links, not copied content.
- Keep every challenge sandboxed and educational.
- Update when model behavior, tool APIs, or prompt-injection techniques change.

Next actions:

- Create challenge taxonomy
- Build first interactive challenge
- Add safety disclaimer and scoring rubric

### Fitness Journey Field Log

- Kind: post
- Category: Student kit / Essays
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/fitness-journey-field-log
- Room context: https://ishudgarg.com/blog#fitness-journey-field-log
- Audience: students, general, curious
- Tags: fitness, health, habits, students
- Status: seed
- Last reviewed: 2026-08-12
- Rights: personal experience only; not medical advice

A practical personal log about losing fat, gaining strength, building community, and not pretending discipline is cinematic.

Plain summary: A personal fitness journey and the habits that helped.

Listen text: Fitness Journey Field Log shares personal lessons on fat loss, strength training, protein, sleep, community, and sustainable habits.

#### The Honest Version

I was never fit, partly because life never forced me to notice. I cycled, walked, had good friends, and did not have obvious health issues. Then after college, something shifted, and I wanted to see myself as an athlete.
The lesson so far: food drives fat loss, strength training protects muscle, sleep matters, and community makes boring consistency easier.


#### Rules That Helped

Track food long enough to learn the macros, then choose a sustainable pattern. Eat enough protein. Lift. Walk. Drink water. Rest. Temporary intensity is noisy; a life system is quieter.


Source plan:

- Keep this clearly marked as personal experience, not medical advice.
- Use current medical or nutrition sources only after explicit verification.
- Invite guest fitness journeys focused on habit formation, not body shaming.

Next actions:

- Write progress timeline
- Add disclaimer component
- Invite one guest fitness field note

### Inner Work Notes

- Kind: post
- Category: Inner work / Essays
- Theme: Inner work (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/inner-work-notes
- Room context: https://ishudgarg.com/inner-work#inner-work-notes
- Audience: curious, general, students
- Tags: spirituality, philosophy, psychology, attention, values, human-nature
- Status: seed
- Last reviewed: 2026-08-13
- Rights: original personal reflections; quotes, religious texts, psychology claims, and mental-health-adjacent claims require source and context review before publication

A living shelf for spirituality, philosophy, psychology, attention, values, meditation, and human nature.

Plain summary: A personal shelf for questions about how to live, think, notice, choose, and stay sane while being ambitious.

Listen text: Inner Work Notes collects personal reflections and source-reviewed reading paths around spirituality, philosophy, psychology, attention, values, meditation, and human nature.

#### The Shape

This room is for questions that should make a person a little clearer, not louder: attention, ego, discipline, grief, ambition, guilt, desire, kindness, values, mortality, faith, doubt, and the strange theatre of human nature.
The tone should be personal and exploratory. The page can hold spiritual ideas, philosophical questions, psychology notes, and lived observations, but it should not pretend that a paragraph has solved being human.

- attention
- values
- meditation
- psychology
- philosophy
- spirituality
- human nature

#### Publication Rule

Personal realization can be written in first person. Claims about psychology, therapy, religion, history, or health need source notes and careful wording.
Quotes belong here only when the source, translation, rights posture, and surrounding context are clear. A quote without context is a borrowed thunderclap.


Source plan:

- Separate first-person reflection from factual claims and advice.
- Use primary texts, reputable translations, named essays, lectures, and peer-reviewed or clinical sources when making claims beyond personal experience.
- Keep psychology and mental-health-adjacent writing clearly educational and non-clinical.
- Invite guest notes as personal lenses, not universal prescriptions.

Next actions:

- Create reflection-note template
- Add quote/source review fields
- Collect first philosophy and psychology reading paths

### Attention Operating System

- Kind: post
- Category: Inner work / Essays
- Theme: Inner work (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/attention-operating-system
- Room context: https://ishudgarg.com/inner-work#attention-operating-system
- Audience: students, curious, general
- Tags: attention, discipline, psychology, values, habits
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original personal framework seed; not mental-health advice

A non-preachy note on attention, ambition, boredom, desire, phones, work, and the strange problem of wanting a life while being interruptible.

Plain summary: A personal framework for protecting attention without pretending life is a productivity spreadsheet.

Listen text: Attention Operating System is a personal framework for protecting attention, handling boredom, ambition, desire, phones, and work without guru language.

#### The Problem

Attention is not only a productivity issue. It is the surface on which a life becomes visible. If everything can interrupt it, everything can quietly vote on who you become.
The danger is to sound like a motivational poster. So the page should stay concrete: what steals attention, what restores it, what boredom is for, and which ambitions deserve the calendar.

- inputs
- interruptions
- boredom
- body
- values
- deep work
- recovery

#### Working Format

Each note should have one observation, one small experiment, one failure mode, and one sentence that future me can use when the phone starts negotiating.
This is not self-help cosplay. It is debugging the human interface.


Source plan:

- Label personal experiments as personal.
- Source psychology and mental-health-adjacent claims before publishing them as general advice.
- Invite guest notes from people with different work, family, and attention constraints.

Next actions:

- Create attention experiment log
- Add distraction taxonomy
- Write first 7-day test

### Student Application Operating System

- Kind: resource
- Category: Student kit / Resources
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/student-application-operating-system
- Room context: https://ishudgarg.com/for-students#student-application-operating-system
- Audience: students, collaborators
- Tags: students, applications, scholarships, internships, college, systems
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original workflow seed; external opportunity data requires source and freshness review

A practical student kit for scholarships, internships, college applications, referrals, documents, deadlines, and review loops.

Plain summary: A structured way for students to manage applications without losing deadlines, versions, documents, or confidence.

Listen text: Student Application Operating System is a practical kit for managing scholarships, internships, college applications, referrals, documents, deadlines, and review loops.

#### The System

The useful unit is not a motivational page. The useful unit is a repeatable packet: profile, documents, opportunity source, eligibility, deadline, version, reviewer, submission receipt, and follow-up.
A student can start with a spreadsheet or Notion-style table, then move to a richer tool when the workflow is proven.

- profile
- documents
- official source
- eligibility
- deadline
- reviewer
- submission receipt
- follow-up

#### Future Tool

The future version can turn this into a student-owned dashboard: reminders, reusable essays, source verification, reviewer comments, and exportable progress.
Account creation can wait until public read-only value exists. Personal storage can start local, exportable, or user-owned.


Source plan:

- Use Radar to discover official scholarship, fellowship, internship, and college pages.
- Store official URL, fetched date, eligibility, deadline timezone, document list, and stale-data rule per opportunity.
- Invite student reviewers to test the workflow on real application cycles before publishing strong recommendations.

Next actions:

- Add application packet schema
- Create deadline freshness gate
- Draft first downloadable tracker

Reusable blocks:

- Radar Source Table: source-table / role inline / inherits parent theme

### Puzzle Technique Atlas

- Kind: resource
- Category: Puzzle lab / Resources
- Theme: Puzzle lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/puzzle-technique-atlas
- Room context: https://ishudgarg.com/puzzle-lab#puzzle-technique-atlas
- Audience: students, curious, ai-builders
- Tags: puzzles, logic, techniques, quant, interview
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original taxonomy and explanations; avoid copied puzzle text

A map of puzzle moves: parity, invariants, extremal arguments, expectation, symmetry, recursion, graph cuts, and simulation checks.

Plain summary: A categorized guide to puzzle techniques so readers learn the trick, not only the answer.

Listen text: Puzzle Technique Atlas maps puzzle techniques such as parity, invariants, extremal arguments, expectation, symmetry, recursion, graph cuts, and simulation checks.

#### How It Organizes Puzzles

Each puzzle gets a primary technique, a wrong-first instinct, one hint ladder, one proof, and a link to a similar puzzle with the same hidden move.
The atlas can grow into a graph: technique nodes, puzzle nodes, prerequisite edges, difficulty, and a weekly rotation that does not revisit the same trick too often.

- parity
- invariant
- expectation
- symmetry
- extremal
- recursion
- graph
- simulation

#### Interactive Lane

Small games can ask the reader for a move before revealing the named technique. The solution page then teaches the reusable idea instead of leaving a trophy answer.
Daily rotations can draw from active puzzles by technique and difficulty, while permanent URLs keep citations stable.


Source plan:

- Collect only original puzzle wording, public-domain classics with rewritten statements, or clearly sourced references.
- Tag every puzzle with technique, difficulty, source posture, and related moves.
- Use simulation for probability puzzles when it clarifies, not as proof replacement.

Next actions:

- Add technique graph data
- Create wrong-first-instinct field
- Write five original technique cards

Reusable blocks:

- Mini Constraint Board: game / role supporting / inherits parent theme

### Curated Video Archive Protocol

- Kind: media
- Category: Curiosity cabinet / Media
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/curated-video-archive-protocol
- Room context: https://ishudgarg.com/for-curious-people#curated-video-archive-protocol
- Audience: curious, students, ai-builders
- Tags: video, archives, media, curation, performance
- Status: seed
- Last reviewed: 2026-08-14
- Rights: link/commentary first; embed or local copy only after provider and rights review

A reusable protocol for collecting lectures, old footage, films, demos, and public archives without breaking rights, speed, or context.

Plain summary: A way to add interesting videos to the site with source, rights, transcript, and lazy-loading rules.

Listen text: Curated Video Archive Protocol explains how videos enter the site: source URL, rights, title, context, transcript or notes, lazy embed, and periodic review.

#### Entry Fields

A video enters as a source packet before it becomes a visual embed: title, creator, source URL, why it belongs, rights/embed state, transcript or notes, and review date.
The protocol supports science lectures, old footage, movie lists, AI demos, music performances, architecture explainers, and historical measurement stories.

- source URL
- creator
- rights
- why it belongs
- transcript
- lazy embed
- review date

#### Why This Matters

A video archive can become a beautiful map of taste, but only if each item has context. Otherwise it turns into a playlist with better typography.
The public page can show linked source rows first, then upgrade selected entries to embeds when performance and rights allow it.


Source plan:

- Use public archives, official lecture pages, creator channels, public-domain collections, and provider APIs where available.
- Keep thumbnails and iframes deferred by default.
- Record transcript availability or write a short original viewing note.

Next actions:

- Add video packet schema
- Create rights/embed badges
- Seed first source-reviewed video rows

Reusable blocks:

- Video Archive Embed Slot: video / role inline / inherits parent theme

### Ishu's Dispatch

- Kind: post
- Category: Writing shelf / Essays
- Theme: Writing shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/ishus-dispatch-newsletter-plan
- Room context: https://ishudgarg.com/blog#ishus-dispatch-newsletter-plan
- Audience: curious, students, ai-builders, collaborators
- Tags: newsletter, writing, ai, puzzles, curation
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original issue structure; external links need source and rights notes

A future newsletter shape: one AI build note, one puzzle, one student resource, one curiosity window, and one sentence worth keeping.

Plain summary: A web-first newsletter plan that collects the best new things from the site without becoming noisy.

Listen text: Ishu's Dispatch is a future web-first newsletter with one AI build note, one puzzle, one student resource, one curiosity window, and one sentence worth keeping.

#### Issue Shape

The newsletter can stay web-first and feed-friendly. Email becomes a delivery channel later, not the source of truth.
A compact issue can have five shelves: build, puzzle, student, curiosity, and verse. That gives repeatability without requiring a grand essay every time.

- one AI build note
- one puzzle
- one student resource
- one curiosity window
- one sentence worth keeping

#### Tone

The voice can be curious, technical, personal, and funny in small doses. The issue loses if it sounds like a personal brand campaign.
The best outcome is that a reader leaves with one useful link, one solved problem, and one question that keeps walking around.


Source plan:

- Publish a canonical web issue before email distribution.
- Use RSS and JSON Feed immediately; choose an email provider only after privacy, unsubscribe, and script-performance review.
- Keep external links source-labelled and avoid copied quote blocks.

Next actions:

- Create first monthly issue
- Add RSS-visible issue tag
- Select email provider after privacy review

Reusable blocks:

- Newsletter Signup Slot: form / role appendix / inherits parent theme

### Radar To Page: Source Packets

- Kind: resource
- Category: AI lab / Resources
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/radar-to-page-source-packets
- Room context: https://ishudgarg.com/for-ai-builders#radar-to-page-source-packets
- Audience: ai-builders, collaborators, students
- Tags: radar, sources, llm-friendly, authoring, workflow
- Status: seed
- Last reviewed: 2026-08-14
- Rights: workflow seed; discovered source content remains linked/summarized with attribution

A reusable workflow for turning discovered links into source-reviewed website objects without mixing candidates and published claims.

Plain summary: A pipeline for finding links, checking them, composing summaries, and publishing only reviewed content.

Listen text: Radar To Page: Source Packets describes a workflow for discovering links, fetching sources, composing summaries, and publishing reviewed website objects.

#### Packet Lifecycle

Discovery is not publication. A packet moves through candidate, fetched, summarized, source-reviewed, composed, and published states.
That separation matters for scholarships, AI tools, videos, travel destinations, quotes, papers, and anything current enough to go stale.

- candidate
- fetched
- summarized
- source-reviewed
- composed
- published

#### Future Capability

The same packet model can feed student resources, AI tool watchlists, travel sources, video archives, quote shelves, and newsletter issues.
A composer can draft from packets, but the published page keeps provenance, review date, rights posture, and stale-data rules visible.


Source plan:

- Index existing Eyrie/Radar tools before building new discovery code.
- Use official and primary sources when claims are technical, legal, financial, educational, or time-sensitive.
- Keep source packet IDs stable so pages can be regenerated without losing provenance.

Next actions:

- Add packet schema
- Create source-state labels
- Connect packet output to content authoring presets

Reusable blocks:

- Radar Source Table: source-table / role inline / inherits parent theme

### Quotes With Context Shelf

- Kind: resource
- Category: Inner work / Resources
- Theme: Inner work (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/quotes-with-context-shelf
- Room context: https://ishudgarg.com/inner-work#quotes-with-context-shelf
- Audience: curious, general, students
- Tags: quotes, poetry, philosophy, literature, context
- Status: seed
- Last reviewed: 2026-08-14
- Rights: short excerpts only with source, translator, rights posture, and context; no long copyrighted passages

A curated shelf for Tolstoy, poets, philosophers, scientists, builders, and stray sentences that deserve context before admiration.

Plain summary: A quote collection that keeps source, context, translation, and a short reflection with every quote.

Listen text: Quotes With Context Shelf is a future collection for literature, poetry, philosophy, science, and builder quotes with source, context, translation, and reflection.

#### Why A Quote Needs A Room

A good sentence can move a person before the person understands why. This shelf keeps the sentence, the source, the surrounding context, and the small human reason it stayed.
Useful categories include poets, Tolstoy, philosophy, science, mathematics, builders, field notes, and lines that feel like a clean wound.

- source
- translator
- context
- why it stayed
- related reading
- rights posture

Source plan:

- Record book, edition, translator, page/location, public-domain or excerpt posture, and why the quote is included.
- Prefer short excerpts and original reflection.
- Link related poems, essays, films, or talks as source packets rather than copying long text.

Next actions:

- Add quote schema
- Collect first ten candidates
- Create rights-length check

Reusable blocks:

- Quote With Context: quote / role inline / inherits parent theme

### BhumiSahayak

- Kind: project
- Category: AI lab / Projects
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/bhumisahayak
- Room context: https://ishudgarg.com/work#bhumisahayak
- Audience: recruiters, collaborators, ai-builders
- Tags: ai, govtech, rural-india
- Status: active
- Last reviewed: 2026-08-12
- Rights: project summary; details require owner review before launch

AI land-records assistant for rural India, focused on practical use and careful verification.

Plain summary: An AI helper for understanding rural land records.

Listen text: BhumiSahayak is an AI land-records assistant for rural India, focused on practical use and careful verification.

#### What It Is

BhumiSahayak is the serious work-mode project: an AI assistant for rural land-record understanding, designed around verification rather than confident storytelling.
The public page should explain the problem, show the system boundary, and make it clear that official records, local context, and human review matter more than fluent answers.


#### Public-Safe Story

The safe version can discuss rural access, document complexity, language friction, retrieval, source citation, verification workflows, and why AI systems in high-stakes domains must be boring in the right places.


Source plan:

- Owner review before any sensitive deployment, data, or partner detail is published.
- Keep legal/government-record claims tied to exact sources.
- Use redacted demos and synthetic examples for public explanation.

Next actions:

- Write public case study
- Add architecture diagram
- Define high-stakes AI disclaimer

### Common Problems Index

- Kind: project
- Category: Student kit / Projects
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/common-problems-index
- Room context: https://ishudgarg.com/tools#common-problems-index
- Audience: students, general, collaborators
- Tags: tools, life-systems, collaborative
- Status: seed
- Last reviewed: 2026-08-12
- Rights: original project seed

An indexed collection of practical solutions for recurring student, work, relationship, and life logistics problems.

Plain summary: A searchable list of common problems and solutions that work.

Listen text: Common Problems Index collects small practical solutions for recurring student, work, relationship, and life problems.

#### The Thesis

A lot of adulthood is not grand wisdom. It is recurring small problems: movie nights across distance, applications, finding scholarships, setting up notes, packing documents, choosing gyms, and not losing important PDFs.
The Common Problems Index should collect small recipes that have actually worked and make them searchable by life situation.


#### How It Avoids Becoming Slop

Every solution needs context, prerequisites, tradeoffs, date tested, and what failed. A recipe without failure notes is probably marketing in casual clothes.

- problem
- who it is for
- steps
- known failure
- tested date
- alternatives

Source plan:

- Use Radar to find common-problem threads, tool docs, and tested recipes.
- Separate owner-tested solutions from community-submitted candidates.
- Keep user-owned storage options visible before asking people to create accounts.

Next actions:

- Add common-problem template
- Create tested/not-tested badges
- Invite submissions from students and friends

### AI Student Helper System

- Kind: project
- Category: AI lab / Projects
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/ai-student-helper-system
- Room context: https://ishudgarg.com/work#ai-student-helper-system
- Audience: students, ai-builders, collaborators, recruiters
- Tags: ai, students, rag, evals, scholarships, applications
- Status: seed
- Last reviewed: 2026-08-14
- Rights: project shell only; no student data, private documents, or live AI calls without privacy and security review

A public-safe project shell for an AI assistant that helps students find resources, prepare applications, and verify sources.

Plain summary: A planned AI helper for students that focuses on verified sources, deadlines, and practical next steps.

Listen text: AI Student Helper System is a planned assistant for students, focused on verified resources, application packets, deadlines, and practical next steps.

#### Problem Boundary

Students do not only need more links. They need a system that distinguishes official sources from copied lists, stale deadlines from live ones, and general advice from what applies to their situation.
The first version can stay read-only: source packets, opportunity search, document checklists, and careful explanations.

- official sources
- deadline freshness
- eligibility
- documents
- application packet
- human review

#### Evidence Plan

The project needs a small eval set before it becomes a demo: missing scholarship, stale deadline, ineligible applicant, conflicting pages, and request for advice beyond the data boundary.
Useful AI here means fewer wrong applications, clearer documents, and a receipt trail for what the assistant used.


Source plan:

- Build over a small official-source corpus first.
- Use synthetic student profiles for public demos.
- Add privacy, data retention, logging, rate, and refusal rules before any user-uploaded documents.

Next actions:

- Define source packet schema
- Write ten eval cases
- Create read-only public prototype boundary

Reusable blocks:

- Indexable App Shell: app-shell / role inline / inherits parent theme
- Radar Source Table: source-table / role supporting / inherits parent theme

### Micro App Garden

- Kind: project
- Category: AI lab / Projects
- Theme: AI lab (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/micro-app-garden
- Room context: https://ishudgarg.com/tools#micro-app-garden
- Audience: ai-builders, students, curious, collaborators
- Tags: tools, apps, performance, games, ai, webapps
- Status: seed
- Last reviewed: 2026-08-14
- Rights: original platform seed; external APIs, assets, and models require terms and security review

A future home for small utilities, games, calculators, AI labs, and experiments that stay fast, indexable, and isolated from the main site.

Plain summary: A way to host small tools and experiments without slowing down the whole website.

Listen text: Micro App Garden is a future home for small utilities, games, calculators, AI labs, and experiments with explicit performance and hosting boundaries.

#### App Classes

Not every experiment belongs in the main bundle. The garden can classify apps as static widget, route-scoped interactive, API-backed tool, separate public app, private admin tool, or external hosted demo.
Each class gets a budget, fallback, secret posture, crawl policy, and owner of state.

- static widget
- route island
- API-backed
- separate app
- private admin
- external demo

#### Candidate Apps

Good first candidates: object hunt, mini Sudoku, LLM source-boundary challenge, scholarship verifier, movie-night setup matrix, puzzle simulator, and travel destination sorter.
The app garden becomes useful when each toy teaches a reusable pattern and leaves behind a small, searchable page.


Source plan:

- Keep secrets server-side and out of static builds.
- Measure bundle size and mobile performance per app class.
- Link each app to content-index, llms.txt, sitemap, and fallback text.

Next actions:

- Create app class registry
- Add app-boundary review packet
- Prototype one static widget and one route-scoped app

Reusable blocks:

- Indexable App Shell: app-shell / role inline / inherits parent theme

### Bastar Student Field Note

- Kind: guest
- Category: Guest shelf / Guest notes
- Theme: Guest shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/bastar-student-field-note
- Room context: https://ishudgarg.com/guest-shelf#bastar-student-field-note
- Audience: students, collaborators, curious
- Tags: education, bastar, guest
- Status: seed
- Last reviewed: 2026-08-12
- Rights: permission required before publishing any student-identifying material

A guest-note slot for students, teachers, or volunteers writing what actually helped on the ground.

Plain summary: A place where people from the education work can share what helped them.

Listen text: Bastar Student Field Note is a guest-note slot for students, teachers, or volunteers to explain what actually helped.

#### What A Good Note Contains

A useful Bastar field note should show what helped a student, teacher, or volunteer in practice: one constraint, one intervention, one surprise, and one thing outsiders misunderstand.
Identity safety matters. Public writing should not expose vulnerable students, precise private locations, or anything that creates social or institutional risk.


Source plan:

- Collect consent and editorial permission before publication.
- Remove or generalize identifying details unless explicitly safe.
- Prefer lived field context over abstract inspiration.

Next actions:

- Create consent checklist
- Draft interview prompts
- Define redaction rules

### Builders Who Changed Their Mind

- Kind: guest
- Category: Guest shelf / Guest notes
- Theme: Guest shelf (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/builders-who-changed-their-mind
- Room context: https://ishudgarg.com/guest-shelf#builders-who-changed-their-mind
- Audience: collaborators, ai-builders, curious
- Tags: startups, engineering, guest
- Status: seed
- Last reviewed: 2026-08-12
- Rights: guest permission required

Guest essays from startup people and engineers about one belief they abandoned after reality objected.

Plain summary: Short guest essays about changing your mind after building something.

Listen text: Builders Who Changed Their Mind is a guest series for startup people and engineers describing one belief they abandoned.

#### The Prompt

Write one belief you held strongly before building something, then explain exactly what reality did to it.
Good submissions should include the old belief, the evidence that broke it, the new belief, and what you would tell someone who still has your old confidence.


Source plan:

- Collect author permission, short bio, links, and disclosure of conflicts.
- Review claims and company-sensitive details before publishing.
- Keep the tone specific enough that it is not generic founder advice.

Next actions:

- Create guest note intake form
- Add author metadata
- Invite first three builders

### Bastar Field Notes

- Kind: gallery
- Category: Student kit / Gallery
- Theme: Student kit (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/bastar-field-notes
- Room context: https://ishudgarg.com/gallery#bastar-field-notes
- Audience: students, curious, collaborators
- Tags: bastar, education, gallery
- Status: seed
- Last reviewed: 2026-08-12
- Rights: requires explicit permission and public-safety review

A future photo essay surface for education work, places, classrooms, and context, gated by privacy and consent.

Plain summary: A future photo story about education work in Bastar, only using safe and approved images.

Listen text: Bastar Field Notes will be a photo essay about education work and place, with privacy and consent checks before anything public.

#### Gallery Rule

The gallery should help people understand place and context, not turn field work into decoration.
Each image needs consent state, safety review, alt text, location granularity, and a reason it belongs in the story.


Source plan:

- Use only owner-approved local images.
- Strip sensitive metadata before publication.
- Avoid identifiable student imagery unless consent and safety review are explicit.

Next actions:

- Create gallery consent checklist
- Add EXIF stripping step
- Prepare first photo essay outline

### World Before / World Now

- Kind: gallery
- Category: Curiosity cabinet / Gallery
- Theme: Curiosity cabinet (front-page-map-hub; nested blocks inherit)
- URL: https://ishudgarg.com/library/world-before-now
- Room context: https://ishudgarg.com/gallery#world-before-now
- Audience: curious, students
- Tags: archives, history, gallery
- Status: seed
- Last reviewed: 2026-08-12
- Rights: verify rights per image before local use

A visual shelf for archive frames, public-domain imagery, maps, and timelapse comparisons.

Plain summary: A visual collection showing how places and life changed over time.

Listen text: World Before, World Now is a visual shelf for archive images, maps, and time comparisons.

#### Visual Comparison Pattern

This gallery should eventually support two-panel comparisons, timelines, maps, and short notes that make change legible.
Archive visuals need source, date, rights, and context. Without that, they are only vibes with a caption.


Source plan:

- Use public-domain or explicitly licensed archive sources.
- Keep thumbnails remote or omitted until rights are verified.
- Preserve archive URL, date, collection, and license per item.

Next actions:

- Add then-now visual component
- Create rights badge
- Source first ten archive candidates