Contributor and Mentor Development

Track Promise

Help make learning clearer, more useful, and more welcoming by creating, testing, and improving activities—with clear scope, human review, and fair treatment of contributors.

A useful contribution might be a clearer instruction, a small activity, a careful observation, or a review that helps someone revise. Start with a learner need, not a quota of content to produce.

This Track is for learners who want to help, writers, activity designers, reviewers, facilitators, and mentors. You do not have to become a consultant or take on an assigned project to participate. Personal practice can remain personal practice.

Start Here

Begin with How to Turn a Lesson Into a Lab — Seed / Planned, owner Unassigned. It is this Track’s signature module: turn one learning idea into something a learner can do, examine, and discuss.

The module names completion of several beginner modules as preparation. Experience an activity as a learner before trying to design one. If you are new to the Learning Lab, the AI Literacy Track can help you find that preparation. This Track does not remove the module’s dependency.

The intended first result is a small activity draft: an audience, one learner outcome, a starting example, steps, a safety boundary, and an observable result. Keep one uncertainty or review question visible. An outline is a design proposal, not a complete, tested, or approved Lab.

Start small, with public, fictional, or permitted material. The draft may be for your own learning. Creating it does not assign you work, authorize RS to use it, or require you to submit it.

The Contribution Loop

Notice a need → Agree scope → Make → Try → Review → Revise

• Notice a need: identify where a learner needs an example, a clearer instruction, a useful activity, or another way to participate.
• Agree scope: define the audience, intended contribution, boundaries, and review. For assigned work, agree the deliverable, owner, credit, and payment terms before starting.
• Make: create the smallest useful draft. Keep source material, your changes, and any AI assistance distinguishable.
• Try: walk through it yourself or arrange a suitable, consent-based practice session. Record what happened, not what you hoped would happen.
• Review: compare the result with the learner outcome, clarity, accessibility, and safety needs. Separate supportive comments from formal approval.
• Revise: make a reasoned change, preserve unresolved questions, and decide whether it needs another try, further review, or a pause.

AI can suggest wording, variations, or review questions. You remain responsible for the draft and its sources. Generated learner reactions are not observations of learners; an AI review is not independent human approval or pilot evidence.

Choose How to Help

These three developing routes let people contribute in different ways. They are not finished courses or a ladder everyone must climb. Existing module Seeds are linked for feedback; unbuilt ideas have no invented source links.

Developing route

Write for learners

Make an explanation easier to enter without removing the idea or talking down to the reader.

How to Write for Beginners Without Talking Down Seed / Planned

Lab idea: Rewrite a dense explanation for a beginner without removing the idea — proposed, no Lab source.

Missing: a permitted before-and-after example, meaning-preservation checks, a guided Activity, and a standalone Notebook. The module has no stated dependency; its presence does not mean the practice package is ready.

Facilitator route demonstration: Coming Soon

Developing route

Observe and improve

Notice confusion, hesitation, engagement, and workarounds. Turn a specific observation into a question or proposed revision without judging the learner.

How to Capture Learner Friction Seed / Planned

Field Notes to Revision Proposed · no module source

Lab idea: Capture field notes after a practice session — proposed, no Lab source.

Missing: a reviewed practice scenario, examples distinguishing observation from interpretation, a minimal field-note record, and a revision exercise. The existing Seed depends on How to Turn a Lesson Into a Lab; it does not yet supply a facilitation package.

Facilitator route demonstration: Coming Soon

Developing route

Facilitate and review

Help someone try an activity, ask a useful question, and give feedback they can act on. Make room for disagreement and different participation needs.

Facilitation Basics Proposed · no module source

Review for Safety, Tone, and Clarity Proposed · no module source

Lab idea: Review a module for beginner clarity and privacy risk — proposed, no Lab source.

Missing: guided facilitation and review practice, example feedback, pause-and-escalate guidance, and mentor-practice guidance. Supporting a learner is not the same as approving an artifact or being qualified to advise on every subject.

Facilitator route demonstration: Coming Soon

Contribute With Clear Agreements

The Contributor Policy governs real contributions. Learning practice, assigned work, permission to use the result, and publication approval are separate decisions.

• Personal practice can stay with its creator unless RS asks to use it.
• Assigned work needs a clear brief, deliverable, audience, constraints, review criteria, owner or reviewer, and credit/payment terms before work begins.
• Commercial use or incorporation into RS product development should be paid unless a separate written agreement says otherwise. Credit and portfolio value do not replace payment terms.
• Credit should respect contributor preference, privacy, and confidentiality. Agree what a contributor may show or share.
• External or commercial use still needs RS review for learner usefulness, tone, accessibility, reliability, privacy, safety, and scope/licensing clarity.

Use these existing supporting references, not as completed modules or Labs:

• Lab Contribution Workflow — proposals, triage, assignment, package expectations, review, and pilot evidence.
• Lab contributor template — prompts for shaping a proposed activity.
• Module template — the existing module structure.
• Facilitator notes template — session planning, participation, and observations for improvement.

Real proposals and assignments follow GitHub Issues and the Project board; assigned packages are submitted through a linked pull request. These documents are not an invitation to start unassigned product work. Track participation does not grant review authority, establish contributor levels, or promise a paid role.

Optional: Explore Consultant Readiness

Consultant Readiness: Judgment, Scope, and Trust remains Seed / Planned, owner Unassigned. It is a later-stage direction for exploring judgment, boundaries, and responsible support of RS work—not the destination for every contributor.

Its stated dependency is the AI Readiness module sequence. That sequence and readiness expectations need clarification in a later artifact pass; this Track does not invent a qualification threshold or remove the dependency. The module’s client-scenario review is only a Lab concept, with no canonical package or Notebook.

This is not certification, authorization to advise clients, or a promise of employment. Any real assignment needs its own agreed scope, review, and payment terms.

Participation and Access

Writing, discussion, observation, and paired practice are valid ways to participate. You may speak your feedback, direct a partner, work on paper, or keep your practice private. No coding, personal AI account, or GitHub account is required for practice; actual contribution submissions follow the established GitHub workflow.

Live AI use is optional. If used, give it a bounded job such as suggesting alternative wording or questions to investigate. Record meaningful AI assistance and verify claims and source permissions. Do not upload private learner information, identifiable field notes, unpublished third-party work, or client material.

Ask before observing or recording a practice session. Collect only what helps improve the activity: the step, what happened, what remains uncertain, and a proposed next question. Avoid names and unnecessary personal details. Simulated examples, self-walkthroughs, and observations of learners must remain distinguishable.

The proposed routes still need accessible examples and self-contained practice materials. These participation options are design commitments, not claims that the missing packages already support them.

For Facilitators and Mentors

Begin with a bounded practice contribution, not an assignment to produce a finished course. Check the signature’s learner-experience preparation, agree what is being tried, and make clear whether the result is personal practice or requested work.

First build priority: the signature’s complete Activity, standalone Notebook, reviewed examples, and facilitator guide. The first walkthrough demonstration remains Coming Soon. Templates help shape that work but do not replace the missing teaching package.

After the materials receive review, pilot one short route: shape a small activity, have someone follow it, and revise one point of friction. Gather actual timing, setup difficulty, language confusion, and accessibility needs. A polished draft or successful self-walkthrough does not establish learner effectiveness.

Mentors support the learner’s judgment rather than taking over the work. Before a real session, name who can approve the artifact, who can answer specialist questions, and when to pause or escalate. Keep encouragement, formative feedback, artifact review, independent final QC, and permission to publish separate.

Contributor levels, mentor preparation, and review responsibilities still need definition. This Track does not create those roles, change policy, or authorize collecting learner records.

Additional Reading

No additional reading is listed yet.

Status and Feedback

This Track remains Draft / Drafting, owner Unassigned. All four linked modules remain Seed / Planned, owner Unassigned, with review status Not reviewed. They retain their current dependencies and primary Track relationships. None has a canonical Lab package or standalone Notebook.

Draft source links support feedback, not a claim of workshop readiness. The shared Track Map records this composition and links the historical outline. Supporting policies and templates remain references outside the curriculum inventory.

Use this page’s Track feedback and review links to assess the promise, starting point, route roles, status language, and missing or misplaced modules and Labs. Is the entry useful without requiring everyone to become an activity designer? Are mentor support and ethical contribution visible enough? Does consultant readiness remain optional? Teaching details belong in separate Module and Lab reviews.

This pass creates no module, Lab, Notebook, example packet, demonstration, contributor assignment, or policy change.

Team review information. You are viewing the team review site. The contributor review tools below are separate from the learner activity and learner feedback.

Review status

• Package lifecycle: Draft
• Learner availability: Drafting
• Review needs: Needs track-level composition, contributor boundaries, mentoring scope, accessibility, and pilot review.

Review this TrackShare Track feedbackIndependent final QC