Skip to main content

Implementation Protocol Example - Introduction to Permaculture

Implementation Protocol Example: Introduction to Permaculture​

This document is a domain-specific implementation example that translates the repository's canonical evidence-based instructional protocol to a concrete subject area.

Canonical references:

  • docs/quality/instructional-design-protocol.md
  • docs/quality/evidence-vetting-checklist.md
  • docs/quality/peer-review-sop.md

Use this as a worked pattern for designing objective, skills-focused courses in other domains.

Positioning​

  • This is an implementation example, not a replacement for the canonical protocol.
  • Claims in domain modules still require source verification and peer review.
  • Human domain experts should validate technical/ecological accuracy before release.

Phase 1: Foundational Design and Needs Analysis​

1. Define target skills and goals​

Primary course outcome:

  • Learner can develop a complete Permaculture Design Plan (PDP) for a defined site.

Applied objectives should prioritize:

  • Water flow and catchment reasoning
  • Zone and sector placement decisions
  • Plant guild assembly and ecosystem fit

2. Select pedagogical framework​

  • Andragogy: authentic design projects and immediate real-world relevance.
  • Connectivism: regional collaboration forums for climate/soil/contextual peer feedback.

Phase 2: Content Development and Rigor​

3. Content sourcing and vetting protocol​

  • Cross-reference ecological/agricultural claims with credible primary or high-quality secondary sources.
  • Avoid anecdotal or overclaimed language.
  • Apply strict causality discipline and uncertainty labeling.

4. Peer review and bias mitigation​

  • Route technical modules (for example, soil microbiology, water systems) through external domain review.
  • Capture reviewer critiques, dissent, and resolution decisions.

5. Structure content for cognitive load​

  • Break large topics into micro-lessons (3-5 min each, one concept each).
  • Example decomposition for earthworks:
    • Reading contour maps
    • Swale design basics
    • Keyline and water movement principles

Phase 3: Presentation and Multimedia Optimization​

6. Multimedia coherence​

  • Remove decorative but irrelevant visuals.
  • Keep visuals directly tied to the design decision being taught.

7. Interactive video requirements​

  • Add in-line checks for key technical distinctions.
  • Use progression gates for critical misconceptions.

8. Accessibility integration​

  • Provide robust alt text for technical diagrams.
  • Ensure captions and transcripts for all instructional video.
  • Validate color/contrast and legibility for map-heavy content.

Phase 4: Learning Architecture and Retention​

9. Retrieval practice design​

  • Start each module with mixed retrieval prompts covering earlier concepts.
  • Include scenario-based recall (not only definitions).

10. Spacing and interleaving schedule​

  • Introduce interleaving across ethics, earthworks, guilds, and systems decisions.
  • For novices, begin with lower context-switch patterns (for example, AABBCC), then increase interleaving complexity (ABCABC).

Phase 5: Assessment and Evaluation​

11. Performance-based assessment​

Summative task:

  • Complete and justify a Permaculture Design Plan using site constraints and resource assumptions.

12. Rubrics and bias controls​

  • Use criterion-based rubrics with explicit technical and reasoning dimensions.
  • Grade blind where feasible.
  • Use secondary review for borderline/high-judgment submissions.

Phase 6: Deployment and Environment Configuration​

14. Personalized pathways and mastery gates​

  • Restrict access to advanced design modules until foundational competence thresholds are met.

15. Collaboration and peer assessment​

  • Require peer review of preliminary designs using standardized rubrics.
  • Include constructive feedback expectations and netiquette guidance.

16. Iterative review and analytics​

  • Track learner progression through milestones and retrieval performance.
  • Use analytics to identify support needs and revise module sequence/content.

Required Readiness Checks Before Publishing a Domain Variant​

  • Domain claim verification complete.
  • External peer review complete for technical modules.
  • Assessment rubric and blind-grading workflow defined.
  • Accessibility checks complete (WCAG 2.2).
  • Safety and ethics review complete where emotionally intense practices are included.