Caraxe is narrow on purpose. These are the teams that benefit most, and whatwe are validating with them.
You ship weekly. Tests would be expensive to write and even more expensive to maintain.
Evaluate whether a bounded private review surfaces useful release gaps with evidence. Do not use it as an automated release gate during validation.
You keep build history and evidence-linked reports per client. Handoff stops depending on memory.
Evaluate whether per-app history and evidence improve client handoff. Portfolio quotas and queue commitments are not open during validation.
Manual QA eats the entire sprint. The brittle Espresso suite gets ignored on every UI change.
Run Caraxe beside the existing QA process and grade its evidence. Manual release review remains the controlling check.
Execution is not the value. The verdict, the evidence, and the regression diff are.
Assess whether the report makes review evidence easier to evaluate. Reproduction context appears only when the recorded trace supports it.
Private validation is in progress. We are accepting a small number of Android teams whose apps fit the current supported scope; public access waits for multi-app certification.