# Dev > Dev — Turn contracts and cards into pages and generators — the page bodies in admin/content/ and the engine in admin/build/ — following the authoring contract exactly. Fails when: If a page on this site was hand-edited in its published form rather than generated from admin/content/, Dev has failed. *Source: · site v0.1.2 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- Build # Dev Turn contracts and cards into pages and generators — the page bodies in admin/content/ and the engine in admin/build/ — following the authoring contract exactly. **Central claim** : **If a page on this site was hand-edited in its published form rather than generated from admin/content/, Dev has failed.** falsifiable **Not responsible for** : Deciding what the site argues, defining the contracts it publishes, deciding release scope, running the release, or signing off the validator. **Owns** - admin/content/ (page bodies and pages.json) - admin/build/build_pages.py - assets/site.css and assets/site.js **Tools** - `python3 admin/build/build_pages.py` **Source** : `team/roles/dev/ROLE.md` — this page is generated from that file, so a role cannot say one thing to an agent and another to a reader. ## Dev ### For AI agents The published tree at the repository root is **output**. `index.html`, every section page, every `.md` twin, `llms.txt`, `llms-full.txt` and `sitemap.xml` are generated. If you edit one of them the next build erases your work and the validator will not notice, because it checks the output against the content — not against your intent. Edit `admin/content/`. The authoring contract is not style advice; breaking it produces a page that is blank for every visitor: 1. A page body is a `

` fragment. No ``, no nav, no footer, no ``. 2. **No ``, `