Not persuasion. Not a verdict. A calibration layer.
A serious review should allow rejection while also distinguishing structural refutation from evidence gaps, phase confusion, documentation issues and access limits.
Classify the objection before converting it into a verdict.
Structural refutation
Would the objection invalidate the bounded Phase 2 solo-formation claim, asset substance, or review-worthiness?
Evidence gap
Is material absent, or simply reserved for controlled review because it is provenance-, IP-, privacy- or security-sensitive?
Phase confusion
Is Phase 1 execution, Phase 2 solo formation or Phase 3 advancement being collapsed into one claim?
Category mismatch
Is a multi-domain formation/review case being judged only as a normal SaaS startup, a single patent file or one product page?
Documentation hygiene
Version drift, stale counts and old wording matter, but only become structural when they touch a load-bearing claim.
Review-capacity limit
A public-only single-pass review should produce a scope-limited conclusion rather than an unrestricted portfolio verdict.
Valid negative outcomes.
Defeat conditions remain explicit.
The purpose of review calibration is not to make MZN unfalsifiable. It is to distinguish a real defeat condition from a gap, a scope limit, a versioning problem or a phase error.
Solo formation fails
Records show material human team/contractor/collaborator formation of eligible Phase 2 assets inside the bounded period.
Asset depth fails
Qualified review shows key assets reduce to unsupported naming, triviality or materially false technical claims.
Evidence fails after access
Controlled records, technical review or legal/IP review contradict the relevant load-bearing claims.