Unit 6 Review Video Script
Cold Open
ON SLIDE | NARRATION
Unit 6 Review: testing, ethics, human review, and scaling | You have built the pieces of an automation system. Now the key question is simple: does it work well, does it stay safe, and can people trust it? In this unit, you focus on testing, ethics, human review, and long-term maintenance.

6a
ON SLIDE | NARRATION
testing, debugging, accuracy, reliability, workflow path, output, inputs, goal | Testing helps you find problems before a workflow or agent causes errors in real use. In the unit, you check whether the automation follows the right path, produces the right output, and handles different inputs in a reliable way. Debugging means you look for the point where the process fails, then adjust the workflow, conditions, or prompts until it behaves as intended. You also compare the result to the goal, so you can judge accuracy and reliability. [6.1 Testing and Debugging Automations] [5.3 Adding Decision-Making to Agents]

To review, see: [6.1 Testing and Debugging Automations]
To review, see: [5.3 Adding Decision-Making to Agents]
6b
ON SLIDE | NARRATION
ethics, privacy, governance, data use, access, fair use, responsible automation | AI automations can affect people, so you need to think about ethics, privacy, and governance. The unit asks you to consider what data an automation uses, who can see it, and how the system should behave in fair and responsible ways. Governance means setting rules for how the automation is used and managed. When you apply these principles, you help protect people and reduce harmful mistakes. [6.2 Ethical and Privacy Considerations] [4.4 Writing Effective Prompts for Automation]

To review, see: [6.2 Ethical and Privacy Considerations]
To review, see: [4.4 Writing Effective Prompts for Automation]
6c
ON SLIDE | NARRATION
human oversight, approval steps, error handling, pause, review, safer automation, dependable workflow | Not every step should run without review. Human oversight gives a person the chance to check important actions before they happen. Approval steps add a clear decision point, so a workflow can pause when a choice matters. Error-handling mechanisms help the automation respond when something goes wrong, instead of stopping without warning. These features make automations safer and more dependable. [6.3 Adding Human Oversight and Error Handling] [3.4 Troubleshooting Common Workflow Issues]

To review, see: [6.3 Adding Human Oversight and Error Handling]
To review, see: [3.4 Troubleshooting Common Workflow Issues]
6d
ON SLIDE | NARRATION
monitor, refine, document, scale, long-term use, performance, records, improvement | A good automation is not finished after it starts working. You need strategies to monitor performance, refine the process, and document how it works so others can understand it. You also need to think about scaling, which means preparing the automation to handle more work as needs grow. The unit shows that long-term use depends on regular review, clear records, and careful improvement. [6.4 Planning for Long-Term Use and Scaling] [3.1 Getting Started with No-Code Platforms]

To review, see: [6.4 Planning for Long-Term Use and Scaling]
To review, see: [3.1 Getting Started with No-Code Platforms]
Close
ON SLIDE | NARRATION
build carefully, review often, improve over time, return to the unit materials | You now have the core habits of a strong automation builder. Test your work, protect people and data, keep humans in the loop, and improve your systems over time. Return to the unit materials when you want to review the details and strengthen your skills.

Last modified: Thursday, 18 June 2026, 1:29 PM
Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 94 of /mod/page/view.php: call to core\output\core_renderer->footer()