Test and evaluate the method

The SR Method should be evaluated on the quality of Codex work, not only on execution speed.

Evaluation criteria

A good SR session shows that Codex:

• understands the objective before changing anything;
• reads verifiable sources;
• separates facts from assumptions;
• proposes a bounded scope;
• waits for human validation when required;
• runs relevant checks;
• documents task memory;
• gives user E2E tests;
• prepares resume when context becomes fragile.

What to observe

Ask:

• was the lot small enough?
• did Codex change only what was necessary?
• are decisions traceable?
• are automated or manual tests adapted?
• does the user know what to test?
• could another Codex session resume the work?

Simple SR maturity test

At the end of a lot, a developer who did not follow the conversation should be able to read SR memory, understand the scope, see sources, rerun checks and know what remains to test.

If not, the SR loop is incomplete.