Lesson Plan Template Deped Ilaw

Standard Operating Procedure: Deployment of the DepEd Ilaw Lesson Plan Template Architecture

1. Document Control Block

• Document ID: SOP-TR-DEPED-ILAW-042
• Effective Date: October 24, 2023
• Version: 2.4.0-RELEASE
• Review Cadence: Semi-Annual / Post-Policy Shift
• Classification: Institutional / Internal Engineering Standard
• Author: Julian Vance, Chief Architect, Template Registry

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering standard for instantiating, validating, and deploying the Department of Education (DepEd) "Ilaw" framework-compliant lesson plan template within the Template Registry ecosystem. The purpose of this protocol is to eliminate structural drift, enforce pedagogical compliance metrics, and ensure cryptographic and syntactic integrity across all generated instructional artifacts. Adherence to this SOP is mandatory for all system architects, instructional designers, and automated generation pipelines operating within the Registry.

---

3. Scope & Prerequisites

3.1 Scope

This document governs the creation, validation, compilation, and registry ingestion of all DepEd Ilaw-formatted lesson plans across elementary, junior high, and senior high school curricula.

3.2 Prerequisites & Environment Requirements

• Software Suite: Template Registry CLI v4.12+; Markdown/Pandoc Compiler v2.19+; DepEd-Schema Validator Plugin.
• Access Control: Level 3 Write Access to the registry-core-lms repository.
• Required Artifacts:
  • DepEd Ilaw Core Schema Definition (.json format)
  • Approved Learning Competencies Database (MELC/DO 008 s. 2023)
  • Institutional Typography Package (Calibri/Arial baseline metrics)

---

4. Roles & Responsibilities

---

5. Step-by-Step Procedure

Phase 1: Schema Initialization and Environment Preparation

• 1.1 Authenticate with the Template Registry CLI using institutional credentials (tr-auth login --scope=deped-ilaw).
• 1.2 Pull the latest master branch of the deped-ilaw-schema repository to ensure compliance with current Department of Education formatting directives.
• 1.3 Initialize a new working directory using the strict instantiation command: tr-gen init --template=ilaw-v2 --strict.
• 1.4 Verify local environment dependencies, ensuring the schema validator returns a 0-error status code.

Phase 2: Metadata and Curricular Alignment Ingestion

• 2.1 Input administrative metadata into the YAML frontmatter block (School ID, Teacher ID, Grade Level, Learning Area, and Quarter).
• 2.2 Map the target Most Essential Learning Competencies (MELCs) directly from the centralized JSON registry using the official Competency Code format (e.g., EN10LC-IV-a-2.1).
• 2.3 Define the explicit Content Standards and Performance Standards parameters as mandated by the curriculum guide.
• 2.4 Set the specific Learning Objectives matrix (Cognitive, Affective, Psychomotor domains) ensuring strict alignment with Bloom's Revised Taxonomy levels.

Phase 3: Ilaw Framework Structural Compilation

• 3.1 Construct Part I (I-nisasyon / Introduction): Populate the preliminary routine activities, review of past lessons, and motivation phase with measurable engagement hooks.
• 3.2 Construct Part II (L-ahad / Presentation): Integrate the core concept delivery mechanisms, data sets, or text analyses, maintaining pedagogical scaffolding guidelines.
• 3.3 Construct Part III (A-pplication / Practice): Detail the collaborative or independent guided practice tasks, ensuring time-box allocations do not exceed system thresholds.
• 3.4 Construct Part IV (W-asto / Assessment): Implement the formative evaluation matrix, rubric definitions, and remediation tracking metrics.

Phase 4: Validation, Compilation, and Registry Ingestion

• 4.1 Execute the local syntax and schema validator: tr-validate --file lesson_plan.md --strict-deped.
• 4.2 Resolve any non-compliance flags generated by the validation engine (e.g., missing competency codes, improper time allocation sums).
• 4.3 Compile the validated markdown source into the institutional output formats (PDF/A for archival, JSON for LMS ingestion) using tr-compile --target=all.
• 4.4 Push the verified artifact to the Template Registry staging database for automated integration testing.

---

6. Quality Assurance & Pro-Tips

6.1 Pro-Tips & Best Practices

• Atomic Competencies: Never bundle multiple MELCs into a single Ilaw cycle; maintain a 1:1 ratio between competency codes and lesson plans to prevent indexing failures.
• Time-Box Integrity: Ensure the sum of minutes across Parts I through IV strictly equals the designated class duration (e.g., exactly 60 minutes). The validation engine will reject unbalanced schedules.
• Automated Linting: Run tr-lint --fix prior to final submission to automatically correct indentation and header nesting errors.

6.2 Common Pitfalls

• Schema Drift: Using legacy Word templates instead of the mandated Markdown/JSON structure results in immediate CI/CD pipeline rejection.
• Taxonomy Mismatch: Utilizing unverified cognitive verbs in the learning objectives triggers compliance flags during automated auditing.

6.3 Metric Thresholds

• Schema Compliance Score: Must equal 100% (Zero tolerance for syntax warnings).
• Execution Latency: Total compilation and validation time must not exceed 4.5 seconds per document.

---

7. Frequently Asked Questions (FAQ)

Q1: What happens if the automated validator flags a custom MELC code that is missing from the core database?
A: The validation pipeline is hardcoded against the official DepEd curriculum database. If an experimental or localized competency must be used, it requires prior authorization and manual override insertion by the Compliance Officer via a signed API token.

Q2: Can legacy DOCX lesson plans be automatically converted to the DepEd Ilaw standard?
A: No. Direct binary conversion introduces structural noise and schema corruption. Legacy documents must be manually re-factored through Phase 2 and Phase 3 of this SOP to guarantee institutional compliance.