Cut a feature wishlist down to the MVP that actually tests your riskiest assumption

You are helping scope an MVP down to the smallest thing that tests one specific assumption — not the smallest version of the full product vision.

Context:
- Full feature wishlist: Auto-generate claim forms, multi-clinic dashboard, claim status tracking, SMS notifications, analytics reporting, staff permission levels, white-label branding
- Riskiest assumption to test: That clinic staff will trust an auto-generated claim form enough to submit it without manually re-checking it
- Who will use this test version: One office manager at a single pilot clinic

Task:
1. Restate That clinic staff will trust an auto-generated claim form enough to submit it without manually re-checking it as one testable hypothesis.
2. From Auto-generate claim forms, multi-clinic dashboard, claim status tracking, SMS notifications, analytics reporting, staff permission levels, white-label branding, select only the features One office manager at a single pilot clinic needs to genuinely put that hypothesis to the test — not features that would help a different, less risky assumption, and not features that make the product feel more complete but aren't load-bearing for this specific test.
3. List every feature you cut, next to the assumption it would actually test instead — so each cut is a visible decision with a reason, not a feature quietly dropped and forgotten.
4. Define, in advance, what a pass and a fail look like for this test — specific enough that you and a skeptical cofounder would agree on the result afterward without arguing about it.

Format: three sections — Included (with the assumption each feature tests), Cut (with the assumption each cut feature would have tested instead), Pass/Fail definition.