> For the complete documentation index, see [llms.txt](https://inside-llms.gitbook.io/mechanisms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inside-llms.gitbook.io/mechanisms/readme.md).

# Inside LLMs

We’re a small group of undergrads from the [Data Science Group](https://dsgiitr.in/) at IIT Roorkee who got unusually curious about one question:

What’s actually going on inside neural networks?

*The mechanisms,* circuits, representations, algebraic structure, failure modes, all of it.

This GitBook is where we document that curiosity.

***

### Why this exists

A lot of ML research focuses on *what models can do*.\
Mechanistic interpretability asks something different:

> **How are they learning it?**

That question pulled us into probing attention layers, dissecting MLPs, testing causal interventions, studying fine-tuning shifts, and even poking at ideas like self-modeling, model introspection, and more interpretable foundational architectures.

Some of this became workshop papers, some rejected submissions, some ongoing experiments, and some things we’re still confused about.&#x20;

***

### What you’ll find here

Think of this GitBook as a **public research notebook**.

Inside:

* Work on domain specialization and circuit discovery in LLMs
* Our AAAI workshop paper on bilinear MLP interpretability
* Experiments on self-modeling and model introspection
* Probing studies, causal interventions, fine-tuning analyses
* Random mech-interp curiosities we didn't resist exploring

If something worked, we explain it.\
If it didn’t, we try to explain that too.

***

### Who we are (and who we aren’t)

We’re not a formal lab.

Just a bunch of students who:

* ask slightly obsessive questions about models
* try to read and understand mech-interp papers
* run questionable experiments at 2 AM
* and somehow keep coming back for more

You’ll find the humans behind this in the **Our Team** section below.

***

### Why make this public?

Because mech-interp benefits from openness:

* ideas cross-pollinate fast
* half-formed intuitions sometimes help others
* and honestly, we learned most of this from people who shared generously.

So this is our attempt to do the same.

If you’re into interpretability, alignment, or just curious how neural nets tick, our guess is you’ll probably find something interesting here.

And if not, at least you’ll know some IITR undergrads tried 🙂

\---

**P.S.** Contact details are on the Team page if you want to reach out.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://inside-llms.gitbook.io/mechanisms/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
