PatchGarden π±: I Built an AI Maintenance Engineer That Doesn't Trust Its Own Patches
ΠΠΏΠΈΡΠ°Π½ΠΈΠ΅ ΠΈ ΠΏΡΠΈΠΌΠ΅Π½Π΅Π½ΠΈΠ΅
PatchGarden Π°Π²ΡΠΎΠΌΠ°ΡΠΈΠ·ΠΈΡΡΠ΅Ρ ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Π½ΠΈΠ΅, ΠΏΠ»Π°Π½ΠΈΡΠΎΠ²Π°Π½ΠΈΠ΅, Π³Π΅Π½Π΅ΡΠ°ΡΠΈΡ ΠΏΠ°ΡΡΠ΅ΠΉ, ΠΏΡΠΎΠ²Π΅ΡΠΊΡ ΠΈ ΠΎΠ±Π·ΠΎΡ, ΡΠΎΡ ΡΠ°Π½ΡΡ ΠΊΠΎΠ½ΡΡΠΎΠ»Ρ ΡΠ°Π·ΡΠ°Π±ΠΎΡΡΠΈΠΊΠ° ΠΈ ΡΠΎΠ·Π΄Π°Π²Π°Ρ Π°ΡΠ΄ΠΈΡΡΠ΅ΠΌΡΠ΅ Π·Π°ΠΏΠΈΡΠΈ ΡΠ΅ΠΌΠΎΠ½ΡΠ°.
ΠΠ°Π΄Π°ΡΠ°
Open-source maintainers struggle with failing tests, neglected issues, and maintenance work that never ends, while AI-generated patches may introduce regressions and lack trustworthiness.
Π Π΅Π·ΡΠ»ΡΡΠ°Ρ
PatchGarden reduces manual maintenance effort by automating investigation and patch generation while ensuring verification and developer control, producing auditable repair records.
Π Π°Π±ΠΎΡΠΈΠΉ ΠΏΡΠΎΡΠ΅ΡΡ
- Investigate the failure and gather diagnostic evidence
- Plan a structured repair with hypothesis and verification criteria
- Patch by generating a minimal, reviewable candidate change in an isolated workspace
- Verify by running relevant tests and comparing results to baseline
- Review the diff and evidence for human approval or rejection
ΠΠΎΠΊΠ°Π·Π°ΡΠ΅Π»ΡΡΡΠ²Π°
PatchGarden is designed to help developers investigate repository failures, generate minimal repair proposals, verify changes, and preserve an auditable history of the process.
The architecture separates reasoning from execution: 1. Open-weight AI for investigation 2. A controlled execution layer 3. Independent verification
PatchGarden relies on Temporal durable workflow orchestration paired with persistent SQLite domain state and immutable JSONL audit logs
- ΠΠ°ΡΠ° Π·Π°ΠΏΠΈΡΠΈ: 2026-10-26T06:11:25.841Z