Add context-first development principle to Agentic development

Establishes the flow: intention → docs → README → code. Code echoes the docs,
not the other way around. Links to README-Driven Context and explains why this
matters for agentic development at scale.

Author: MariusStorhaug

docs/Ways-of-Working/Principles.md

@@ -70,6 +70,26 @@ LLM tokens are not the right tool for work that has a deterministic answer. Use
 - **Integration** — the agent's ability to act on a platform as if it were human. GitHub, the editor, the terminal.
 - **Sensoring** — the agent's ability to notice that it is needed. Webhooks, scheduled checks, signals from the platform.
 
+### Context-first development
+
+An echo of platform engineering's "a product starts with a README." Every change flows through context before it touches code:
+
+```text
+Intention of change → Update documentation → Update README → Update code
+```
+
+Code echoes the docs, not the other way around. The README and the docs are the **specification**. If a change isn't reflected in context first, the code has no contract to implement against — and agents have nothing to read.
+
+This means:
+
+- A new feature starts as a documented intent (issue, README update, or docs change) before any code is written.
+- A refactor updates the relevant documentation **first**, then the code follows to match.
+- If the docs and the code disagree, the docs are wrong — fix the docs, then fix the code to match.
+
+This is what makes agentic development work at scale. Agents read context. If the context is stale or missing, the agent builds the wrong thing. Keeping context ahead of code is how we stay in control.
+
+See [README-Driven Context](Readme-Driven-Context.md).
+
 ## Getting Things Done
 
 From David Allen's [GTD](https://gettingthingsdone.com/). If something is only in your head: