AI collaboration and continuous improvement
Turn repeated findings into tests, shared owners, scaffolds, and shrinking debt.
On this page
Canonical source
This public guide is distilled from docs/AI-COLLABORATION.md and docs/CONTINUOUS-IMPROVEMENT.md. Keep implementation detail in those repository documents.
Evidence before edits
The repository workflow orients in current state, establishes a reproduction or measurement, changes the owning boundary, verifies in expanding rings, performs adversarial review, and hands off literal evidence.
Make the next change safer
A recurring review comment should become a shared primitive, regression test, generated contract, scaffold rule, or architecture ratchet. Pattern baselines may shrink, while new exceptions require explicit rationale.
Was this page helpful?
Feedback is stored only in this browser in the starter implementation.