1. Product evidence
- Is there a live app or working surface?
- Are real workflows visible?
- Are admin or operational structures visible?
- Are screenshots sanitized before public use?
Reviewer checklist
Use this before trusting the case study
2. Technical evidence
- Is there a connected GitHub repository?
- Is there a hosted deployment?
- Is the system database-backed?
- Are architecture claims specific and bounded?
3. Governance evidence
- Are roles and permissions represented?
- Are organizations, programs or workflows structured?
- Are audit or timeline concepts visible?
- Are decision and escalation ideas documented?
4. Claim discipline
- Does the case avoid overclaiming production use?
- Does it separate evidence from ambition?
- Does it state what is not yet proven?
- Does it route reviewers to proof pages?
Simple score
Evidence maturity score
0-1 areas strong: early concept proof.
2 areas strong: credible portfolio artifact.
3 areas strong: strong technical/product proof.
4 areas strong: highly reviewable case study with strong trust discipline.