luigidemasi opened a new pull request, #183: URL: https://github.com/apache/camel-kit/pull/183
Successive pipelines can leave readers reconstructing the system from change-specific documents and can bring superseded decisions back into scope. This adds a shared lifecycle for a coherent current-system description, updated in place, alongside ADRs that retain decision history. Fixes #182. Follows up on the evolution/documentation feedback in #163. - Reuse existing documentation conventions, with `docs/camel-kit/system-design.md` and `docs/adr/` as defaults. Keep existing pipeline paths and preserve project-owned files on reinitialization. - Prepare ADRs during design with neutral context, credible alternatives, consequences and concrete responses. Preserve accepted reasoning and reciprocal supersession links; distinguish acceptance from implementation. - Connect discovery, design, plan, execute, reporting-only validation, direct migration and debug to the shared lifecycle. Add documentation-only reconciliation through `camel-start`. Execute owns finalization after chained validation; standalone validation identifies the documentation-only handoff. - Keep Ship's candidate, native proposal allowlist and Stamp controller-owned. The invoking parent reconciles documentation after publication; direct CLI callers receive an explicit follow-up, including on stderr with JSON output. - Add `doc snapshot`, `doc record`, and opt-in `doc check --project`. Content and directory inventories detect manual/uncommitted additions, edits and deletions. Partial, failed, missing or changed evidence cannot report unchanged completed-review inputs. Legacy commands remain compatible. - Update the security model, CLI/stage documentation and Antora navigation, with a worked observability-to-archive evolution example. Validation: - Java 21 full root `./mvnw -B clean install`: all 13 modules passed; 2,199 tests passed, 11 existing conditional Knowledge skips, no failures/errors. - `./mvnw -B -Psourcecheck validate` and diff checks passed, including shipped-asset structure and resource consistency in the full build. - Executed rendered documentation commands for all eight agents and both CLI prefixes; checked preservation through reinitialization. Added actual Camel YAML evolution and source/evidence boundary tests. A mutation disabling source-drift detection was caught; the implementation was restored and retested. - An independent agent followed the installed guidance through the initial feature, accepted-but-unimplemented successor, implemented archive and later manual drift. It retained ADR reasoning, consolidated the complete fixture description, and kept pending/failed verification unverified without silently accepting drift. - Antora component rendering passed with the same six unavailable external-component cross-references as the base, no new diagnostics, and 40 local links checked on the new guide. Review records bind the reviewer's stated scope and conclusions to file contents; they do not prove semantic correctness or coverage. Behavioral acceptance used real Camel with two roles, in-process endpoints and in-memory capture processors. It does not certify Kafka, durable storage, production controls, or every native agent/Ship host. Full external website integration was not run. _AI-generated by Codex 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]
