Skip to content

White Belt badge template

Status: drafted · Time: 10 min · Audience: new-builder Outcome: Provide the builder-facing template for claiming White Belt with evidence links and reviewer attestation.

Use this after Boss Fight W-B merges. The badge is not a reading chapter. It is the builder-facing evidence packet for certification.

Copy the template into the program tracker or the approved evidence location.


Builder handle:
Team:
Role:
Belt claimed: White
Date claimed:

Quest W-0 - Turn GREEN
Evidence link:
Verification date:
Plugin version:
Result: GREEN
Quest W-1 - HelloRazorpay commit
PR URL:
PR state:
Date closed or reviewed:
Boss Fight W-B - One real typo, merged
PR URL:
Merge link:
Reviewer:
Date merged:

Reviewer handle:
Reviewer role:
Review date:
I confirm that the evidence above satisfies White Belt:
- setup verification is GREEN;
- sandbox PR evidence exists;
- one genuine typo or equivalent micro-fix was merged;
- no evidence includes sensitive material.

Write 3-5 sentences in your own words:

Before White Belt, I...
The hardest part was...
The thing that now feels less scary is...
The next small thing I want to try is...

This paragraph is not for ranking. It helps the program improve the next cohort.


Date awarded:
Recertification due:
Refresh note:

Set recertification due to one year from the awarded date. See Appendix L - Certification for the program rule.


Recommended Yellow Belt start:
Why:

Most White Belt graduates should start with the Yellow Belt boss-fight example when the module set is still being filled in, then return to the Yellow modules as they land.


  • W-0 evidence exists and is GREEN.
  • W-1 PR URL exists.
  • W-B PR is merged.
  • Reviewer attestation exists.
  • Recertification due date is set.
  • No sensitive details are present in the badge packet.

When all six are checked, the White Belt claim is ready for the tracker.


Previous: Boss Fight W-B - Next: Yellow Belt