What is an Agile Manifesto?
The 2001 Agile Manifesto states four value pairs: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan — plus 12 supporting principles.
The most-misread word is "over": the right side has value too; the left side has more. Teams that quote the manifesto to justify zero documentation have inverted it into an excuse.
Worked example
A vendor demands a signed 200-page spec before coding (contract negotiation); the client's team proposes two-week demos with reprioritization rights (customer collaboration). Eighteen months later, the collaborative contract shipped a product users shaped — and still produced documentation: exactly as much as operating the product actually requires.