luigidemasi opened a new issue, #42: URL: https://github.com/apache/camel-kit/issues/42
> Imported from [luigidemasi/camel-kit#74](https://github.com/luigidemasi/camel-kit/issues/74), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-13. > Closed on 2026-09-04 without a linked pull request. --- ## Context **Source pattern:** `source-driven-development` skill from [agent-skills](https://github.com/addyosmani/agent-skills) — every framework-specific decision gets a URL back to the official documentation. Citation is a first-class requirement. ## Problem Iron Law 1 (MCP catalog is truth) covers component verification. But there's no formal citation mechanism — the agent verifies internally via MCP but doesn't surface the evidence trail to the user. The user sees "using timer component" but not the documentation reference that validates the configuration. ## Proposed Solution Strengthen `camel-implement` and `camel-execute` output with a citation step: - After MCP catalog verification, cite the specific Apache Camel component documentation page - When using an EIP pattern, reference the Camel EIP documentation - When configuring properties, link to the component's property reference - Flag any decision that could NOT be verified against docs: `UNVERIFIED: ...` **Example output:** ``` Using timer component with period=5000 Source: https://camel.apache.org/components/4.x/timer-component.html Verified via MCP: camel_catalog_component_info("timer") ``` ## Acceptance Criteria - [ ] `camel-implement` guide updated with citation format - [ ] Component decisions include documentation URL - [ ] EIP pattern decisions include documentation URL - [ ] Unverifiable decisions flagged with `UNVERIFIED:` marker - [ ] Citations appear in the design spec and/or implementation plan output -- 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]
