Outcome and constraints
The intended audience, result and success checks are clear; unsupported assumptions are named.
Belts · evidence · Randori
Bring a real artifact, explain your choices and practice adapting when the situation changes.
Use the packet with a person who independently agrees to review your work. It asks for the outcome, the stack you actually used, an artifact, observed checks, a changed constraint and honest limits. It works for a software prototype, a design, a research summary or another field.
Download the blank review packet · Open the packet in your browser
On a phone, open or download the file and edit a copy in your notes or document app. You choose where to keep and share it. The Dojo does not save, receive or send this packet. Browser downloads and printing also work without JavaScript.
Practice, not an award: This packet does not assign a reviewer, score an assessment, issue a belt or certify a professional deliverable. Specialist belts and a formal independent assessment process are still being developed.
These are proposed cross-field practice prompts, not a replacement for an existing rank rubric or a passing threshold. Use standards and checks appropriate to the actual field.
The intended audience, result and success checks are clear; unsupported assumptions are named.
The learner identifies the harness, model, instructions, tools and permitted actions actually used, with versions when available.
The learner explains their own decisions, what each agent did and why the approach fits the task.
Inputs, checks and actual results can be inspected; failed or untested cases are recorded rather than hidden.
The learner responds to a new constraint without copying a memorized recipe, explains the change and checks the revised result.
Privacy, permissions and unresolved risks are identified, along with any independent or qualified review needed.
A practice sales table has two unique complete lines: 2 items at $4 and 3 at $5. A duplicate is counted once and a missing quantity is left for review. The learner reports $23 and shows the arithmetic: 2 × $4 + 3 × $5. The reviewer independently checks those source rows.
A changed constraint asks for a short text-message report that still names the duplicate and missing quantity. The reviewer records whether the learner adapted without inventing the missing value. This is an illustration, not an observed learner review.
The five colored stages on the belts page are proposed field-practice stages, not issued credentials. Developer, Master Developer and Sensei are broader Dojo ranks; a field practice stage does not automatically confer a rank.
For an actual Developer or Master Developer certificate, use the existing Product Package rubric or Master Developer assessment as applicable. A Sensei, or a mentor for Master Developer, reviews; a separate Maintainer decides under the certificate process. Sensei selection follows the existing process. This practice packet does not change those rules or promise a review.
For regulated or safety-critical work, a practice review is separate from independent validation and any approval required from a qualified professional.
Review notes, scores and learner work are private by default. Ask before sharing learner material with an AI service; a human reviewer reads the evidence and writes feedback. See the Sensei privacy guide and review guide.
These recipes name evidence a peer, Sensei or professional checks. Use the packet to prepare it. Fixtures only show the template.