luigidemasi opened a new issue, #160: URL: https://github.com/apache/camel-kit/issues/160
Documentation follow-up for #111 (clarify whether interface contracts are supplied or designed during discovery). Replaces luigidemasi/camel-kit-web#58 now that the documentation lives in this repository (`docs/modules/ROOT/`, published at https://camel.apache.org/camel-kit/next/). ## What to document, once #111 is implemented In `greenfield.adoc` and `camel-brainstorm.adoc`: - Which artifacts users can provide: OpenAPI, AsyncAPI, WSDL, JSON Schema, XSD or documented message contracts. - An example where the source contract exists and the target contract has to be designed. - That supplied material is inspected before clarification questions, so already-resolved decisions are not asked again. - That pending contract artifacts remain explicit dependencies instead of being replaced by invented definitions. - That newly proposed contracts need design approval before implementation, and that existing external interfaces carry compatibility constraints. ## Acceptance criteria - Wording matches the behaviour delivered by #111 and its release scope; the enhancement is not described as shipped before it is implemented. - The Antora build passes; documented in the same change as the feature, or linked from #111 before it closes. _AI-generated by Claude Fable 5.1 on behalf of @luigidemasi._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
