IDDn
Henry Grech-Cini
Light theme
One intent · six disciplines
IDD
Intent Driven Development
Building it
Pause cycle
Intent is invariant. The output artefact is not.
Intent Driven Development is a way of building with AI in which every requirement is written down with the reason it exists, signed by a named person, and checked by the build before anything is made from it.
What do you want to do first?
Documentation docs.iddn.uk What the method is, the schema a graph follows, and how to run one.
Examples iddn.uk/examples/ Seven accounts of real work by a person and an AI, from a parking register to a talk.
Articles iddn.uk/articles/ Arguments about the method, each resting on one of the worked examples. The first is on what using AI actually removes.
Catalogue catalogue.iddn.uk Public throughlines for WCAG, ASVS, NIST and other standards, to compose into your own graph. Each is marked draft until a named person signs it.
Tools tools.iddn.uk Tools that run in the browser: read and sign a graph, take it apart, keep a folder in step with GitHub.
Skills skills.iddn.uk Claude Code skills for working in a throughline repository.
throughline github.com/rhodium-org/throughline The tool: a command line and a file format for a requirements graph, open source.
Frozen lockup
IDDevelopment
Compact mark
IDDn
Favicon · 44px
IDDn
Plain text
iddn
n = 6
Development is canonical
Show why this exists
Provenance mode on — point at anything