How the review system works
Follow one change from an idea to verified work, then into operational learning.
Seven articles for engineering leads: briefs, agent review, CI, independent verification and measurement.
TL;DR
- Define what a change must preserve before assigning it. Carry that contract through review, CI and independent checks after merge.
- Follow one ledger-reading improvement through all seven parts, or choose the question you need from the reading list.
- Keep component performance separate from user benefit. Continuing operational assessment, performance review and architecture review are planned additions.
Read the series
Follow the seven parts in order, or open the question you are working on.
- Read part 1
Review starts in the brief
How an idea becomes a stream and a brief, then moves through implementation, review and independent verification.
- Read part 2
Writing briefs agents can execute
Find the affected consumers, preserve their behavior and write acceptance checks that can reject a plausible wrong result.
- Read part 3
Four questions for the review agent
What correctness and security review ask, and how the planned performance and architecture reviews would extend them.
- Read part 4
What CI can prove
How CI checks behavior, how muhar tests the tests, and where quality history, ratchets and publication checks fit.
- Read part 5
Merged is not verified
What a separate verifier checks on merged main, how evidence is recorded and what dependencies require.
- Read part 6
Learning after delivery
Keep user journeys and the review method under examination. Learn from other systems, test refinements and return justified improvements as bounded work.
- Read part 7
Measuring agent delivery
Choose useful measures for waiting, review quality, accepted-result cost and the effect on users.
The review system at a glance
*Performance and architecture reviews are planned.