REODE
Code migration
Before fixing, find the common cause.
A Java/Spring code-migration agent.
Making the repair agent read the configuration first
The agent that tried setter-by-setter edits is the repair agent inside the REODE product; development changed its input. Code and customer information are private.
March 21, 2026
Error groups, the original build and the Lombok setup became the repair input
Under developmentREODE repair agent
Observation · findingTried individual edits for about 40 setter errors · @Data / POM not inspected
- sent backMissed the common cause→ Read source and build configuration before fixing (Developer)
PersonDeveloper
ActionRead source and build configuration before fixing
- handoffRepair input changed→ Build the original baseline · group same-pattern errors (Development changes)
Work sessionDevelopment changes
ActionBuild the original baseline · group same-pattern errors
- handoff→ Collect evidence: paths · 3 source samples · annotations · POM (Development changes)
Written ruleContributor policy
Rule · unverifiedTask plan · owned worktree
- not a recorded executionRequired by policy→ Build the original baseline · group same-pattern errors (Development changes)
Work sessionDevelopment changes
ActionCollect evidence: paths · 3 source samples · annotations · POM
- handoff→ Deterministic Lombok fix first · LLM skipped if the rebuild passes (Development changes)
Written ruleContributor policy
Rule · unverifiedZero-context review: plan ↔ diff
- not a recorded executionRequired by policy→ Collect evidence: paths · 3 source samples · annotations · POM (Development changes)
Work sessionDevelopment changes
ActionDeterministic Lombok fix first · LLM skipped if the rebuild passes
- handoffRebuild failed→ If the rebuild fails, model repair with evidence and fix instructions (REODE repair agent)
Under developmentREODE repair agent
Observation · findingIf the rebuild fails, model repair with evidence and fix instructions
- handoffVerification signals→ Scorecard: build · test · deleted tests · surefire exclusions (Artifacts)
ArtifactsArtifacts
ArtifactScorecard: build · test · deleted tests · surefire exclusions
- sent backRemaining failures→ Remaining failures go back to evidence collection (Development changes)
Work sessionDevelopment changes
ActionRemaining failures go back to evidence collection
- Context
- The repair agent tried to fix about 40 setMsg() not found errors one at a time without looking at @Data or the Lombok version in pom.xml. Input that was already broken was not told apart from errors the migration introduced.
- Outcome
- The scorecard reads build and test results together with the number of deleted tests and surefire exclusions, and skips the coverage item when the baseline is unknown. Passing by deleting tests stays a failure.
- Limit
- Evidence collection samples up to three sources, so it is not an understanding of the whole codebase. There is no record that the policy’s worktree, independent review or develop merge queue actually applied to this case, and the coding agent and model for this case are not confirmed. There are no final customer test or coverage results.
Sources and remaining limits
- The baseline task and the explore-before-fixing task moved from in progress to done, and implementation commits exist. No fresh GitHub check results were pulled.
- This repository’s policy sets a feature → develop → main merge queue, but the same procedure is not applied to other projects.
- The opt-in validation agents are a mechanism in the implementation, not evidence that they were used on every delivery. Figures such as delivery size or ratios are not included because their original evidence could not be confirmed.
- When the rebuild fails, model repair still receives the original build error, not the rebuild’s new one.