Why AI Can Fill API Spec Gaps but Cannot Invent Routes

The article argues that AI should only fill specific, named gaps in an API specification, never create new routes. A deterministic code scan first establishes the actual routes, methods, and paths through framework tracing and static analysis. Any element the scan cannot resolve is flagged with a gap code tied to a specific handler, and the model then supplies a bounded fill for that gap only. The author warns that invented routes would enter documentation as fact and propagate into mocks and reviews. Human review checks each AI fill against the source before it is adopted.