---
title: "Instruction Set Architecture as a Contract"
description: "The instruction set is the promise the hardware makes to every program: these operations exist, these registers are visible, this is how memory is addressed. Everything below it can be rebuilt without"
canonical: https://lightmysky.com/learn/computing/instruction-set-architecture-as-a-contract-mt_pbwHRePY5M
source: https://lightmysky.com/learn/computing/instruction-set-architecture-as-a-contract-mt_pbwHRePY5M.md
retrieved: 2026-09-12
---

> **Agent view.** This is the Markdown twin of the page, for tools and assistants.
> When to use this site, and the call that answers each job: https://lightmysky.com/agent-instructions.md
> API description (OpenAPI 3.1): https://lightmysky.com/openapi.json · Authentication: https://lightmysky.com/auth.md
> Pricing: https://lightmysky.com/pricing.md · Catalog: https://lightmysky.com/llms.txt · Full catalog: https://lightmysky.com/llms-full.txt
> Every machine-readable file on this domain: https://lightmysky.com/.well-known/ai-catalog.json
> Ask for Markdown with `Accept: text/markdown`, a `.md` address, or `?mode=agent`.

# Instruction Set Architecture as a Contract

The instruction set is the promise the hardware makes to every program: these operations exist, these registers are visible, this is how memory is addressed. Everything below it can be rebuilt without breaking a single compiled program, and that separation is why chips can change while software does not.

Subject: Computing · Area: Computer Systems · Ages 18 to 19
Page: https://lightmysky.com/learn/computing/instruction-set-architecture-as-a-contract-mt_pbwHRePY5M

## Ready when they can

- Name what an instruction set fixes and what it deliberately leaves to the implementation
- Compare a load-store design with one that operates directly on memory and say what each costs
- Explain why two chips with different internals can run the same binary

## Lesson: The promise between chips and programs

The instruction set is the promise the hardware makes to every program. It fixes which operations exist, which registers programs can see, and how memory is addressed. Everything below that line can be rebuilt without breaking a single compiled program.

**Example.** In a load-store design, only loads and stores touch memory, and arithmetic works on registers. In a design that operates directly on memory, an operation can read and write memory cells itself. The first keeps each step simple at the price of extra loads and stores. The second saves those steps at the price of more complex operations.

Two chips with different internals can run the same binary because both keep the same promise. One may schedule work differently inside, but programs only see the operations, registers, and addressing the contract names.

**Tip.** To judge a designer change, ask whether programs can see it. New scheduling inside keeps the promise. Renaming a visible register, removing an operation, or changing the addressing breaks it.

**Recap.** The instruction set fixes what programs see, and everything below that line is free to change.

## Practice

8 questions on this page, each with its working shown.

## Needs first

- [Assembly Language and the Instruction Set](https://lightmysky.com/learn/computing/assembly-language-and-the-instruction-set-mt_bzmsfvdzwp)
- [Registers, Buses and the Fetch-Execute Cycle in Detail](https://lightmysky.com/learn/computing/registers-buses-and-the-fetch-execute-cycle-in-detail-mt_yjy3eSStzH)

## Opens up

- [Code Generation and What an Optimiser May Change](https://lightmysky.com/learn/computing/code-generation-and-what-an-optimiser-may-change-mt__ZSPwP4hfA)
- [The Memory Hierarchy and Why Caching Works](https://lightmysky.com/learn/computing/the-memory-hierarchy-and-why-caching-works-mt_0f5ArFPlxP)
- [What an Operating System Is: Privilege and System Calls](https://lightmysky.com/learn/computing/what-an-operating-system-is-privilege-and-system-calls-mt_0kMavEKxpX)
- [Race Conditions and Mutual Exclusion](https://lightmysky.com/learn/computing/race-conditions-and-mutual-exclusion-mt_hygT74jJDE)