wenjin272 commented on issue #894: URL: https://github.com/apache/flink-agents/issues/894#issuecomment-5091978430
Thanks, @weiqingy. The Azure OpenAI structured-output change sounds like a good first candidate. I think your baseline concern is valid for specification-driven development, where humans approve a design before implementation and the code must be verified against that fixed specification. My proposal is slightly different. The Implementation Description is an **as-built description of the final code**, intended to make review easier: 1. A human reviews the final architecture, behavioral contracts, failure behavior, and compatibility impact described there. 2. An independent coding agent checks whether the code and tests match the description, and whether the description omits any important behavior. In this model, updating the description as the implementation evolves is expected, so fixing a Stage 1 baseline is not essential. If an individual contributor chooses to follow an SDD workflow for a particular PR, pinning the human-approved specification would make sense in that case. However, this would remain an optional development practice rather than a community requirement. Regarding the issue of the description's position, I agree with your view. -- 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]
