{"section":"introduction","title":"Introduction Rules","description":"Core principles that guide all API design decisions","totalRules":3,"spectralRules":[],"rules":[{"id":"api-first-design","requirement":"MUST","rule":"API design (description, schema) is the master of truth, not the implementation","severity":"error","spectralRule":null,"rationale":"Ensures consistent contracts and enables parallel development"},{"id":"api-first-compliance","requirement":"MUST","rule":"API implementation MUST always be compliant with the approved API design contract","severity":"error","spectralRule":null},{"id":"robustness-ignore-unknown","requirement":"MUST","rule":"Clients MUST safely ignore unexpected fields in responses","severity":"error","spectralRule":null,"rationale":"Enables API evolution without breaking clients"}]}