Black Belt badge

Status: drafted · Time: 5 min · Audience: platform-builder Outcome: Claim the Black Belt — the platform-builder community’s admission ticket and the close of the belt curriculum.

You have walked Parts A, B, and C. You have claimed Quest B-1 (a shared skill adopted by two PODs outside your team) and Quest B-2 (a Blade contribution or a full-stack feature released with production proof). You have shipped Boss Fight B-B (a one-month POD embed with a signed-off metric lift and a contributed case study). You are ready to claim the Black Belt.

What the Black Belt means

The promise the belt has carried since the Prologue:

“I am a force multiplier for Razorpay.”

Three pieces of evidence prove it: a published shared skill (cross-POD adoption), a cross-layer contribution (Blade or full-stack ownership), and a measured uplift on a POD outside your own (the boss fight). The chapters teach the moves; the quests prove you can make them; the boss fight proves the moves propagate.

The Black Belt is not a graduation. It is an admission ticket to the platform-builder community, the cohort of builders the program leans on for the harder shapes of work: complex shared skills, MCPs, custom agents, plugin lifecycle decisions, RFCs against the program’s AI surface, and (when invited) membership of the Staff+ Council.

A reader can hold this belt and continue to ship in their POD. A reader can also hold this belt and pivot toward platform-builder work as their primary focus. Both are valid. The belt does not prescribe; it qualifies.

The claim ceremony

Five steps. None of them are heavy; the heavy lifting is the work that came before.

Step 1 — Confirm the chain

Walk your tracker row and confirm:

⚪ White Belt earned (date logged).
🟡 Yellow Belt earned (date logged).
🟢 Green Belt earned (date logged).
Black Belt nomination registered (manager or Green Belt teammate, recorded with the cohort lead).
Quest B-1 claimed: merged shared-skill PR, install confirmations from ≥2 outside-team PODs, reviewer attestation.
Quest B-2 claimed: merged Blade contribution OR full-stack PR/revision set with a completed production release receipt, reviewer attestation.
Boss Fight B-B claimed: case-study link, POD lead’s metric sign-off, all-hands share confirmation, two reviewer attestations (one out-of-team, one Black-Belt-or-above).

If any link is missing, fix the link before claiming. The claim is built on the chain, not on the candidate’s say-so.

Step 2 — Write the closing reflection

A short paragraph (~150-300 words) covering:

what you built that other teams now run on;
the moment(s) you understood that platform-builder work is different from individual-contributor work;
one thing about the Black Belt curriculum (any module, any quest, the boss fight) that worked or did not for you;
what you intend to do in the next twelve months: Council shape work, mentoring, or returning to your POD with the new toolkit.

The reflection is what cohort leads read most carefully. It is the candidate’s chance to name the internalisation: what the badge means to them, in their context, beyond compliance with the rubric.

Step 3 — Submit the claim

In the program’s main forum, with a single post that contains:

the chain confirmation (Step 1) with links;
the closing reflection (Step 2);
a one-line “I claim Black Belt” statement.

The cohort lead acknowledges within a working week. If the chain is incomplete, the cohort lead names what is missing; if complete, the claim moves to Step 4.

Step 4 — Review

Per Appendix L. For Black Belt: two reviewers, one out-of-team and one Black-Belt-or-above. The reviewers verify the chain (the same checks Step 1 walked, but independently); they read the boss-fight case study; they read the closing reflection. They sign the claim.

The review is thorough, not adversarial. Reviewers’ job is to ensure the chain is real and the artefacts are honest; if the chain is real and the artefacts are honest, the claim approves.

Step 5 — Recognition

An entry in the program’s celebrations channel with the candidate’s name, the date, and a link to the boss-fight case study (with the case study contributed back to the playbook archive per Boss Fight B-B’s rubric).
A row update in the certification tracker.
The Black Belt badge artefact added to the candidate’s profile (the program’s badge system).

The recognition is light on ceremony. The boss-fight all-hands share already happened; the badge claim is the official close-out of the belt, not a second presentation.

What changes after the claim

A Black Belt is reachable for:

Authoring RFCs that affect the program’s AI surface (per B.14).
API Council reviews with an AI-specific lens (per B.15).
Plugin and skill governance decisions: approval, deprecation, security review (per B.16).
Office hours and embedded sprints as a host or embedding builder (per B.12 and B.13).
Mentoring Black Belt candidates through their quests and boss fight.
Sponsoring other builders’ RFCs, pre-embed conversations, and case-study reviews.

The expectation is light but real: a Black Belt is a member of the platform-builder community, which means showing up to the cultural and governance moves the community runs. A Black Belt who claims the badge and disengages from the community is technically valid; an active Black Belt is what the badge actually represents.

What does NOT change

Your role does not change. Black Belt is a curriculum credential; it does not promote you, change your team, or grant authority.
Your responsibilities to your POD do not change. The boss fight was outside your POD; your normal work is inside your POD. The badge does not exempt you from POD work.
Your reporting line does not change. Black Belt is parallel to the management track, not a substitute for it.

What comes next: the Staff+ Council

The Staff+ Council is the program’s invitation-only community for builders who shape AI policy across the org over multi-year horizons. It is not a next belt to earn through quests; it is a standing forum for builders the program leans on for direction. Membership comes via invitation from the existing Council; the criteria are public but the decision is curated.

The patterns that lead to Council invitation:

consistent contribution to the platform-builder community (RFCs sponsored, embeds run, case studies contributed);
mentoring multiple Black Belt candidates through their boss fights;
authoring new chapters or substantive updates to this playbook;
representing Razorpay externally on AI engineering (talks, blog posts, OSS contributions).

The Council recognises the moves before it formalises them. A closed-belt builder who is sponsoring RFCs, reviewing peers’ boss fights, and mentoring Black Belt candidates is already operating at the level the Council looks for.

Where to next

If you have just claimed Black Belt:

Stay engaged. The community runs office hours; show up. Embedded sprints get requested; volunteer when the timing fits. New plugins enter approval; review them.
Mentor. A Yellow or Green Belt builder in your network is closer to their next belt than you think. The fastest way to compound the program’s leverage is to coach the next cohort.
Author. A chapter you wish this playbook had — write it. The repo accepts contributions; a Black Belt’s first contribution is often where the playbook grows next.

If you have not yet claimed:

Walk the chain. Step 1’s checklist names the missing pieces. Most candidates are missing one or two, not all of them.
Talk to the cohort lead. Pre-claim conversations surface the right way to close the gap; do not wait for the formal review to learn what is missing.

What you can say after Black Belt

“I am a force multiplier for Razorpay. I have built leverage other teams run on, owned cross-layer work, and shipped a measured uplift on a POD outside my own. The Black Belt is what I built, not what I was given.”

The Black Belt artefact

The badge image lives in the program’s badge system. The shape: a black square with the Razorpay mark and the word BLACK in the program’s typography, plus the date the candidate claimed. The artefact lands in the candidate’s profile, the celebrations-channel post, and (if the candidate wishes) their LinkedIn or external profile.

The artefact is a token. The work it represents is the boss-fight case study, the published shared skill, the cross-layer contribution, and the closing reflection.

Previous: ← Boss Fight B-B · Next: Master Index · Black Belt README

Further reading

Appendix L — Certification — the reviewer protocol.
Black Belt — Part C: Shape the Org — the chapters this badge closes.
Staff+ Council — the next horizon.