webrune-tim / webrune-tim/The-Autonomy-Protocol

Core curriculum guides and lesson plans

Open
#39 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

curriculum help wanted site-content
Dominant language
JavaScript
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Objective

Rewrite synthetic lesson content and curriculum guides into actionable, practitioner-level instructional materials.

Key Focus Areas

  • Module Summaries: Clear explanations of purpose, real-world utility, and personal stakes for each unit.
  • Lesson Steps: Concrete, step-by-step procedures that teach executive functioning habits (time management, task prioritization, emotional regulation under pressure).
  • Actionable Exercises: Tangible student deliverables rather than passive reflection exercises.

Tone & Voice

  • Instructive, objective, and realistic about human friction and resistance to discipline.
  • Frame learning as a tool for personal liberty and independence rather than bureaucratic compliance.

Acceptance Criteria

  • All curriculum files (.md / .mdsvex) reviewed and rewritten.
  • Jargon-heavy or speculative educational theories removed in favor of practical application.
  • Clear learning outcomes defined for every module.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inventorying all curriculum files with .md or .mdsvex extensions, then review each module summary, lesson sequence, and exercise against the objective and tone requirements. Done means every curriculum file has practical learning outcomes, actionable student deliverables, step-by-step executive-function instruction, and no jargon-heavy or speculative theory.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
content, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.