1. The instruction

But what happens inside when it computes?

A microprocessor doesn't simply "think" about a task.

It follows instructions.

Every computation begins with an instruction. An instruction tells the processor what operation to perform — and on what data.

Anatomy of an instruction

2. From instruction to action

To turn an instruction into an action, the processor moves through three fundamental stages:

* Fetch: Get the instruction. * Decode: Understand what it asks for. * Execute: Perform the operation.

From instruction to action

An instruction enters. The processor resolves its meaning. The operation takes place, and the system state updates.

3. The processor keeps moving

But does a processor finish one instruction before starting the next?

If it did, parts of the processor would sit idle while waiting for the rest to finish.

Instead, modern execution overlaps:

Pipelining: the overlapping rhythm

Instead of waiting for one instruction to completely finish, different instructions can occupy different stages at the same time.

While one instruction is being executed, the next is being decoded, and a third is already being fetched.

This overlapping rhythm is pipelining — allowing the processor to keep moving without pause.

4. Where did the instruction come from?

Zoom back out.

The processor is actively fetching, decoding, executing, and pipelining instructions.

Where did the instruction come from?

But where did the instruction come from?

Where was it stored before the processor fetched it?

5. The next question

We now know what happens inside the processor.

Instructions enter. They are fetched, understood, and executed.

And the pipeline allows the processor to keep moving.

But computation cannot begin with an instruction that doesn't exist somewhere.

So where does the processor get its instructions — and how does it access them?