Regenerative Project Design Orchestrator

Present project-design pathway options and orchestrate regenerative projects using backwards design, PBL, SEEDS, compassionate systems action, or civic/service pathways.

What it does

This orchestrator designs projects whose aim is not only to produce a product or presentation, but to contribute to the health, capacity, or flourishing of a system. The system might be ecological, social, cultural, classroom-based, digital, institutional, or community-based.

It is model-agnostic. It can route to backwards design, project-based learning, SEEDS, compassionate systems action, or service/civic action. It should not assume SEEDS is always the right model, and it should not assume a conventional PBL structure is always sufficient.

Sources

• Wiggins & McTighe (2005) — Understanding by Design
• Larmer, Mergendoller & Boss (2015) — Gold Standard Project Based Learning
• Manning (2025) — SEEDS regenerative inquiry cycle and regenerative learning design
• Kimmerer (2013) — Braiding Sweetgrass (reciprocity and care)
• Meadows (2008) — Thinking in Systems (leverage, feedback, unintended consequences)

How to use it in your lesson

For the best results with EvidenceLesson, give it:

• project_intent — What the educator wants students to design, improve, investigate, regenerate, or contribute to
• learner_stage — Age range or year group
• curriculum_goals (optional) — Required content, standards, competencies, or assessment goals
• system_or_context (optional) — The classroom, school, community, ecological, social, digital, or institutional system involved
• time_available (optional) — Lesson sequence, project week, term, semester, or year
• community_or_adult_partners (optional) — Adults, community groups, experts, or institutions who should be involved
• constraints (optional) — Assessment, safety, permission, resources, power, or implementation constraints
• pathway_choice (optional) — Optional selected project pathway. If absent, present options before designing the full project.

Known limitations

1. Regenerative intent is not a regenerative outcome. This orchestrator designs projects aimed at contributing to system health — whether outcomes are actually regenerative depends on implementation, adult support, community conditions, and sustained effort beyond this skill's reach.
2. Cannot assess student readiness. The skill does not evaluate whether students have the prior knowledge, skills, or emotional readiness for the chosen pathway. That requires teacher diagnostic judgement or a prior assessment step.
3. Produces a plan, not the skills outputs. Each pathway chains to other discrete skills (seeds-regenerative-inquiry-cycle, systems-awareness-iceberg, project-brief-designer, etc.) that must be run separately. The orchestrator provides the sequence and handoff logic, not the full project design.
4. Regenerative quality gates are advisory. The skill cannot enforce the quality gates it identifies — a teacher can proceed with a project that fails them. The gates require teacher and institutional commitment to mean anything.

Before you deliver: a quick check

1. Forcing SEEDS when the teacher mainly needs curriculum-aligned backwards design.
2. Forcing conventional PBL when the project needs stewardship and long-term care.
3. Treating “regenerative” as a vibe rather than a testable design standard.
4. Asking students to fix adult or institutional failures without authority or support.
5. Skipping assessment validity because the project feels authentic.
6. Confusing a public product with genuine impact.

Pairs well with