No, your program is NOT text. It gets compiled to opcodes that the CPU understands. There are TONS of papers on the internals of a CPU from the one in your remote control, your car radio to your computer. Visit the Intel and AMD site for documents.

When the CPU gets made, it is built with microcode that understands the opcodes which opens/closes certain circuits. CPUS contain an ALU and CU, the CU decodes the opcodes, the ALU does math and logic. Read on the net, way too much info to explain here.

Search term: "how does a cpu execute programs"
Results: TONS!

compile a program and open it in a hex editor, see all those nubmers? Most of those are opcodes - instructions the CPU understands.

In a nutshell, the OS loader loads your program into memory (does a few calculations) and sets the EIP register to the address of the first instruction, the cpu executes that instruction and increments the address in EIP according to the opcode size, executes the next instruction.. this keeps going in a linear fashion from A to Z. Skipping some code according to compares and jmps. When you call a function, the cpu skips to the address of that function but returns to the spot right after the call.. Nutshell, it is very in depth as to the workings of the CPU