programming-layers
Installation
SKILL.md
Programming layers
A one-sentence request leaves a dozen things undecided: what each word means, what exists, who may act, what changes. The leap — request straight to code — decides all of them silently, in a form nobody can review. Descend instead. Each layer answers one question and ends in an artifact the next layer reads.
| # | Layer | Question | Artifact |
|---|---|---|---|
| 1 | Intent | What do we want to accomplish? | Intent |
| 2 | Semantics | What do the words mean? | Vocabulary |
| 3 | Ontology | What exists, and how is it related? | Entities and edges |
| 4 | Operational Model | What can happen, by whom, and with what effect? | Operation |
| 5 | Execution Model | How is an operation invoked? | Execution contract |
| 6 | Program | How is it implemented? | Code |
| 7 | Technology | What frameworks and runtimes carry it? | Stack |
| 8 | Runtime | How does the machine execute it? | Machine code |
Specification: OM-1.